- Windows Setup Log Files and Event Logs
- WindowsВ Setup Event Logs
- To view the WindowsВ Setup event logs
- To Export the log to a file
- How to: View, save, and configure build log files
- To view the build log file for a C++ project
- To create a build log file for a managed-code project
- To change the amount of information included in the build log
- Where Are The Windows Logs Stored?
- Accessing The Event Viewer
- Using The Event Viewer
- Log Categories
- Get Started Today!
- Knowledge Base
- 8859: Exporting and Viewing Windows Event Logs
- use Google Translate
- Operating Systems:
- Introduction
- Solution
- How-To Export Windows Event Logs
- Purpose
- Solution
- Method 1: Export EVTX with Display Information (MetaData)
- Method 2: Export as CSV
- Method 3: Collect entire log folder from Windows.
- Which Logs to Export
Windows Setup Log Files and Event Logs
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 | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Verbosity level | Description |
|---|---|
| Quiet | Displays a summary of the build only. |
| Minimal | Displays a summary of the build and errors, warnings, and messages that are categorized as highly important. |
| Normal | Displays a summary of the build; errors, warnings, and messages that are categorized as highly important; and the main steps of the build. You’ll use this level of detail most frequently. |
| Detailed | Displays a summary of the build; errors, warnings, and messages that are categorized as highly important; all of the steps of the build; and messages that are categorized as of normal importance. |
| Diagnostic | Displays all data that’s available for the build. You can use this level of detail to help debug issues with custom build scripts and other build issues. |
You must rebuild the project for your changes to take effect in the Output window (all projects) and the
Where Are The Windows Logs Stored?
In this article, we discuss Windows logging, using the event viewer, and the windows log storage locations.
Windows VPS server options include a robust logging and management system for logs. These logs record events as they happen on your server via a user process, or a running process. This information is very helpful in troubleshooting services and other issues, or to investigate a security problem.В
Windows references logs as events, while Plesk and most other systems call them logs. For standardization, they call them logs in this article. Follow below to see how you can use the event viewer to review your logs and investigate issues.В
Accessing The Event Viewer
The first step in accessing the Event Viewer is to connect to your server. Gaining access to the server is accomplished through the Console button in Manage, or through a manual RDP connection.
Once you have connected to your Windows server, you will need to log in to your administrator account. Once logged in, click the Start menu, then Event Viewer.
Using The Event Viewer
The event viewer is a system application included on all versions of Windows servers. This program allows you to view logs recorded to it by applications and the system. The event viewer has four main views you will see when you first launch the application:
- Custom Views
- Windows Logs
- Application and Services logs
- Subscriptions
For this article, we will focus mainly on the Windows Logs. The project you are hosting may have you reference the application logs for programs you use, which may be outside the scope of this article.В
All logs are assigned an event level. This event level denotes the severity or seriousness of any issues noted in the logs. The default view of the list below is by acuity.
- Audit Success — (Security category only)
- Audit Failure — (Security category only)
- Critical
- Error
- Warning
- Information
- Verbose
Log Categories
You will also notice that Windows logs are broken down into categories. These classifications are listed below, along with some quick info about each section.В В
Application — Logs related to drivers and other system components
Security — Logs pertaining to successful and failed logins, and other authentication requestsВ
Setup — Logs associated with Windows install and updates
System — Logs linked to uptime, service status changes, and other messages generated by the operating system
Forward Events — Logs from a remote server, forwarded to this server
Clicking on any of the categories above will load all of the saved logs for that category. The logs will, by default, be arranged in chronological order. You can also modify how the logs are arranged by clicking on any of the column headers.В
Clicking on any specific record will bring up some general information about the log, like the time of the log entry, the log entry level, it’s ID and source, as well as a variety of other information that can be used to identify an issue.В
Clicking on details will provide you with the raw log data, which can present a more considerable amount of detail that can be used to investigate and solve problems.В
Lastly, the default location of these logs can be found in the following folder on the server:В
Get Started Today!
Are you have issues tracking down where problems are occurring on your windows server? Need help deciphering the information in a log file, or trying to locate ways to improve the responsiveness of your server?
Our Level 3 Windows administrators are tough, smart, and experienced techs who can help with any issue. Reach out today if you are running out of options and need to hear from a professional regarding any of our Windows servers or platforms using either our Managed Cloud or Private Cloud Powered by VMware and NetApp!
If you are on a Fully Managed VPS server, Cloud Dedicated, Private Parent server, or a Dedicated server owner and want to make a change, give us a call at 800.580.4985, or open aВ chatВ orВ ticketВ with us to find out how!
Knowledge Base
8859: Exporting and Viewing Windows Event Logs
use Google Translate
Operating Systems:
Last update: Mon, 2014-08-25 15:27
How to export and view event logs in Windows
Introduction
For troubleshooting purposes, it may be necessary to export Windows Event Logs.
Solution
Exporting Windows Event Logs
- Invoke Windows Event Viewer:
- Windows XP/2003/2000: Hit Start-Run and type in eventvwr.msc:
Windows Vista/7/2008/2008R2: Hit Start and type in eventvwr.msc:
Windows 8/8.1, Windows Server 2012/2012R2:
— press Winkey + W;
— type «ev»;
— select «View event logs».
Select the type of logs you need to export:
- Windows 7/8/8.1, Windows Vista, Windows Server 2008/2008R2/2012/2012R2: Action ->Save All Events As.
- Windows XP/2000/2003: Action ->Save Log File As.(!) It is recommended to save the System and the Application event logs, and name them accordingly.
| KB ID: | 1873 |
| Product: | Veeam Backup & Replication |
| Version: | All |
| Published: | 2014-04-21 |
| Last Modified: | 2021-01-01 |
| Languages: | IT | ES |
Purpose
When submitting a support case for technical assistance, it is sometimes necessary to upload relevant Windows event logs in addition to the Veeam logs. Event logs exported using default settings can be missing important information. This article describes three different methods of exporting Windows event logs and which logs tend to be most useful for certain types of support cases.
Solution
Below are the three common methods a Veeam Support Engineer may request you gather event logs for them. If they have specified a specific method, please use the requested method.
Click here to see what logs should be collected for common issues.
Method 1: Export EVTX with Display Information (MetaData)
An .evtx file alone does not contain the text of most events, so uploading an .evtx file without the associated Display Information can delay resolution of your support case. Even with the display information, an .evtx contains only the UTC time of the events and not the source time zone (Event viewer adjusts the displayed time to your local time zone).
Steps to Export .evtx with Display Information
- Open Event Viewer (eventvwr.msc).
- Locate the log to be exported in the left-hand column.
- Right-click the name of the log and select Save All Events As…
- Enter a file name that includes the log type and the server it was exported from.
For example, when exporting the Application event log from server named HV01, enter Application_HV01. - In Save as type , select Event Files .
- Include display information.
Be sure to include the LocaleMetaData folder when packaging logs for upload.
Please package all files into a single .zip archive. For information on uploading files to Support, see: Steps to Compile Logs
To export and then archive an event log from the command line, see: Archive an Event Log
Method 2: Export as CSV
- Open Event Viewer (eventvwr.msc).
- Locate the log to be exported in the left-hand column.
- Right-click the name of the log and select Save All Events As…
- Enter a file name that includes the log type and the server it was exported from.
For example, when exporting the Application event log from server named HV01, enter Application_HV01.
In Save as type , select CSV (Comma Separated) .
Please package all files into a single .zip archive. For information on uploading files to Support, see: Steps to Compile Logs
To export and then archive an event log from the command line, see: Archive an Event Log
Method 3: Collect entire log folder from Windows.
- Navigate to C:\Windows\System32\winevt\Logs
- Archive (ZIP\7z\RAR) the entire contents of the Logs folder.
Please package all files into a single .zip archive. For information on uploading files to Support, see: Steps to Compile Logs
To export and then archive an event log from the command line, see: Archive an Event Log
Which Logs to Export
Veeam Support will request logs as needed, but you can speed up resolution of a new case by checking to see if it falls into one of the categories below and uploading appropriate event logs during case creation.
- For Hyper-V Snapshot (Shadow Copy) Failures
- Export the following event logs from the standalone Hyper-V host or from all cluster nodes:
- Windows Logs > System
- Windows Logs > Application
- Applications and Services Logs>Microsoft>Hyper-V-VMMS>Admin
- If Application-Aware Image Processing is enabled in the Backup or Replication job settings, test whether the failure occurs with that setting disabled.
- If the problem occurs only when Application-Aware is enabled, export the Hyper-V-Integration log from the Hyper-V host managing the VM, then see Guest Processing Issues below.
Note:For Hyper-V 2016 or newer this step can be skipped, as this section was removed in Server 2016.- Applications and Services Logs>Microsoft>Hyper-V-Integration>Admin
- Export the following event logs from the standalone Hyper-V host or from all cluster nodes:
- For Guest Processing Issues
Note: For “Guest Processing Skipped” seeKB1855.- Common examples include failure to truncate Exchange or SQL transaction logs, “VSSControl” error codes, and unexpected behavior occuring with the VM guest OS during backup.
- Export these logs from the affected VM guest OS:
- Windows Logs > System
- Windows Logs > Application
- You will typically also want to collect the Veeam VSS logs from the VM – see KB1789.
- For Problems with Backup Infrastructure Servers
- In all scenarios below, export the following from the appropriate server. When in doubt, export from the Veeam Backup server:
- Windows Logs > System
- Windows Logs > Application
- If the error message is:
- «task failed unexpectedly” — Export events from the Veeam Backup server.
- referring to backup files on a Windows server — Export events from the repository server.
- referring to backup files on a CIFS/SMB share — Export events from the gateway server, or from the Veeam Backup server and all proxies if no gateway was specified in the repository settings.
- In all scenarios below, export the following from the appropriate server. When in doubt, export from the Veeam Backup server:
