Channel Initialization
Applies To: Windows Server 2008 R2
Event logs are normally initialized when the Event Log service starts. This initialization can also happen during installation of a component that creates a new log. When the initialization fails, the log is not available to receive events and the diagnostic and troubleshooting capabilities of administrators, support personnel, developers, and automated utilities can be compromised.
The application-defined logs are specific to the event provider that created them and will only affect events published by that provider. The operations that remain for the Event Log service and all other event providers are not affected when there is a problem with one of the event logs being initialized.
Events
| Event ID | Source | Message |
|---|---|---|
Microsoft-Windows-Eventlog |
The service encountered an error %1 while obtaining or processing configuration for channel %2 | |
Microsoft-Windows-Eventlog |
The event logging service encountered an error (res=%1) while initializing logging resources for channel %2. | |
Microsoft-Windows-Eventlog |
The event logging service encountered a corrupt log file for channel %1. The log was renamed with a .corrupt extension. | |
Microsoft-Windows-Eventlog |
The event logging service encountered a log file for channel %1 which is an unsupported version. The log was renamed with a .UnsupportedVer extension. | |
Microsoft-Windows-Eventlog |
The event logging service encountered an error (res=%1) while opening log file for channel %2. Trying again using default log file path %3. | |
Microsoft-Windows-Eventlog |
The event logging service encountered an error (res=%1) while parsing filter for channel %2. Will continue without filter. | |
Microsoft-Windows-Eventlog |
The event logging service encountered an error when attempting to apply one or more policy settings. |