Event ID 31 — Primary Channel Initialization
Applies To: Windows Server 2008 R2
.jpg)
Initialization of the primary channels must succeed for the Event Log service to continue its operation. An error event related to a primary channel initialization causes the Event Log service to terminate. This means that in most cases it is impossible to view the event, because viewing the event requires the Event Log service. When you find events that indicate the primary channel initialization failed, the errors occured in the past and this can indicate a problem that has been corrected or a transient condition that must be investigated.
Event Details
| Product: | Windows Operating System |
| ID: | 31 |
| Source: | Microsoft-Windows-Eventlog |
| Version: | 6.1 |
| Symbolic Name: | PRIMARY_CHANNEL_CONFIGURATION_WARNING |
| Message: | The event logging service encountered an error (res=%1) while opening configuration for primary channel %2. Trying again using default configuration. This problem usually occurs if registry has been corrupted or explicitly misconfigured. |
Resolve
Fix primary channel configuration data
Event 31 indicates that the system was able to recover from initialization failures. Most likely, some of the configuration parameters for the primary channels are incorrect and some information can be derived from the events preceding event 31. The configuration should be fixed, otherwise the warning and the preceding events will appear every time the computer is restarted.
Verify
When primary channels cannot be initialized, the Event Log service does not start. To verify that the Event Log service is running, run the following command from a command prompt:
wevtutil ep
This command will display a list of all the event providers that are registered with the Event Log service. The command succeeds without error (produces a list of publishers) only if the Event Log service is running.