Event ID 25 — Channel Initialization
Applies To: Windows Server 2008 R2
.jpg)
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.
Event Details
| Product: | Windows Operating System |
| ID: | 25 |
| Source: | Microsoft-Windows-Eventlog |
| Version: | 6.1 |
| Symbolic Name: | INIT_CHANNEL_MOVED_CORRUPT_LOG |
| Message: | The event logging service encountered a corrupt log file for channel %1. The log was renamed with a .corrupt extension. |
Resolve
Shutdown the computer properly or repair the hard disk
The most likely reason for a corrupt event log is that the computer was incorrectly shut down. The remedy for this is to always shut down the system correctly and to have backup power to avoid having the power shut off from the computer while the computer is turned on.
Another cause for a corrupt event log file is when a problem occurs with the hard disk drive that contains the event log. To resolve this problem, repair or replace the hard disk drive if required.
Verify
Use the Event Viewer to read the affected log on the local computer after the computer has been restarted, and verify that events 20, 23, 25, 26, or 40 did not appear in the event log after the system was restarted.