Windows® Setup creates log files for all actions that occur during installation. If you are experiencing problems installing Windows, consult the log files to troubleshoot the installation.
WindowsВ Setup log files are available in the following directories:
Log file location
Description
Log location before Setup can access the drive.
Log location when Setup rolls back in the event of a fatal error.
Log location of Setup actions after disk configuration.
Used to log Plug and Play device installations.
Location of memory dump from bug checks.
Location of log minidumps from bug checks.
Location of Sysprep logs.
WindowsВ Setup Event Logs
WindowsВ Setup includes the ability to review the WindowsВ Setup performance events in the Windows Event Log viewer. This enables you to more easily review the actions that occurred during WindowsВ Setup and to review the performance statistics for different parts of WindowsВ Setup. You can filter the log so as to view only relevant items that you are interested in. The WindowsВ Setup performance events are saved into a log file that is named Setup.etl, which is available in the %WINDIR%\Panther directory of all installations. To view the logs, you must use the Event Viewer included with the Windows media that corresponds to the version of the customized image that you are building.
To view the logs on a computer that does not include the corresponding kit, you must run a script from the root of the media that installs the Event Trace for Windows (ETW) provider. From the command line, type:
where D is the drive letter of the Windows DVD media.
To view the WindowsВ Setup event logs
Start the Event Viewer, expand the Windows Logs node, and then click System.
In the Actions pane, click Open Saved Log and then locate the Setup.etl file. By default, this file is available in the %WINDIR%\Panther directory.
The log file contents appear in the Event Viewer.
To Export the log to a file
From the command line, use the Wevtutil or Tracerpt commands to save the log to an .xml or text file. For information about how to use these tools, see the command-line Help. The following commands show examples of how to use the tools:
Where to store an application log file on Windows
Where would be the best «standard» place to put an application’s debug log file in a Windows user environment?
In this particular case, it is an application that is run once and could go wrong. It will be run by system administrator types who may need to inspect the log after the application is run. Everytime the application is run, a new log file is created.
Options that have been floated so far include:
The program directory
The user’s desktop
The user’s local Application Data directory.
I have my favourite, but I wondered what the SO consensus was.
Note: this is similar to this question, but we’re dealing with an application that’s only likely to be run once by one user.
7 Answers 7
The Application Data directory would seem to be the perfect place, but it’s an area that is nearly invisible. You need to give your users an easy way to get to it.
Have your installation script create a Log folder in the Application Data area for your program, and include a link to the folder in your Start menu.
In the organization I work for we use the (%TEMP% or %TMP%)\CompanyOrProductName\Logs directory Using %APPDATA% may be problematic with roaming profiles if the logs are numerous or huge : it slows their login process .
1.The program directory
The «standard» place for the log would be the AppData directory. However, really its up to you where you want to store them. As they are administrator (power users) then there should be no problems storing the logs in the same directory as the application being run. Even in the MyDocuments of the user would be a good shout.
If you EXPECT something to go wrong put it in the user’s local Application Data directory.
If you don’t and just want to log anyways I might think about really using the temp directory. The reasoning for this is simple. If the application is only run once you will leave trash in the Application Data directory otherwise that nobody will ever need again. In the temp you have at least the CHANCE that it’s going to be cleaned up later.
BTW: IMHO the best would be not not create the log AS A FILE at all (log to memory) until something goes wrong. Then you can still offer a dialog where the user selects where to save the log.
Where is windows log
This forum is closed. Thank you for your contributions.
Answered by:
Question
I have a job running on a sharepoint server every hour. If I write to the event logs/ Console.Write, can you tell me, where will the logs get stored on the sharepoint server.
Answers
How about looking at this MSDN article which explains the Custom Logging mechanism in detail:
Hope this helps.
Thanks & Regards, Kamlesh | Blog | Twitter | Posting is provided «AS IS» with no warranties, and confers no rights.
All replies
Log in to your server.
Go To Start—>Administrative Tools—>Eventviewer
Then right click on the event categories on left and select properties. This will show you the path.
For me it is %SystemRoot%\System32\Winevt\Logs
I hope this will help you out.
Thank you so much. But, I believed, that for sharepoint server, u mention the logs, in the central admin site, and thats where the logs get stored.
Correct me if I am wrong.
How about looking at this MSDN article which explains the Custom Logging mechanism in detail:
Hope this helps.
Thanks & Regards, Kamlesh | Blog | Twitter | Posting is provided «AS IS» with no warranties, and confers no rights.
I have opened the event viewer and in the diagnostics performance It has shown some files which are causing too much lag while the system is shutting down and also while booting up. I wonder where those files are..
can u please tell me to how to get to that file location?
for example, wuauserv file is creating a delay of 4sec to shutdown.
Where is windows log
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Asked by:
Question
===== NOT SOLUTION =====
The solution that follows in this inset tricked me into thinking I’d made a discovery that solved my (and many other’s) problem. But it is apparently only the solution when Memory Diagnostic is run by the system in ‘Task Scheduler’, not when ‘Memory Diagnostic’ is run on demand (i.e., as an application). DAMN!
I’m leaving this non-solution here as documentation of at least one thing that works (though it doesn’t work in a practical sense).
The results of Memory Diagnostic are hidden in ‘Task Scheduler’ (. really)
1, Open ‘Task Scheduler’ using ‘Run as administrator’, then look in the right panel and click ‘Enable All Tasks History’ — otherwise, when you get to the _/History\_, you will discover that it says: _/History (Disabled)\_. 2, Now, run ‘Memory Diagnostic’ in the usual way (which closes Windows, runs the test, then restarts Windows). 3, When Windows is back up, look in ‘Task Scheduler’, ‘Task Scheduler (Local)’, ‘Task Scheduler Library’, ‘Microsoft’, ‘Windows’, ‘MemoryDiagnostic’. 4, Double-click Name ‘ProcessMemoryDiagnosticEvents’ . which opens the ‘ProcessMemoryDiagnostiEvents Properties (Local Computer)’ dialog. 5, Click the _/History\_ tab. 6, Search for, and select the most recent ‘Task Category’: ‘Action completed’. 7, Under the _/General\_ tab in the panel directly below, read the result of the test — I assume that ‘with return code 0’ means no memory faults were found.
Honestly! Microsoft! This is cruel and unusual punishment.
===== ORIGINAL POST ===== (Note: I found ‘answers.microsoft.com’ topics relating to this. They are all closed and locked with no resolution.)
As you probably know, Windows has a Memory Diagnostic that reboots, then runs prior to Windows startup.
I ran Memory Diagnostic, Basic, 1 pass . simple, just so I could quickly see what it does. It said I would see the results on next log on. I was not shown results.
I searched all of drive C: for *memory*.log — not found. I searched all of drive C: for *memory*.evtx — results:
Acer made the computer. I chatted with Acer support. They don’t know where the log is stored. They also said that the test is supposed to show the log to me when it finishes, prior to Windows startup . that didn’t happen, either.
Where does Windows put the results of the Memory Diagnostic?
