| Event Id | 23 |
| Source | Microsoft-Windows-Eventlog |
| Description | The event logging service encountered an error (res=%1) while initializing logging resources for channel %2. |
| Event Information | According to Microsoft : Cause : This event is logged when the event logging service encountered an error while initializing logging resources for channel Diagnose : Event 23 indicates that the Event Log service had a problem opening an event log file. Another event will be found in the log prior to event 23 that can help diagnose the problem. The problem is usually a corrupt log, a bad file path, or a log with an incorrect version. In each case, the Event Log service will attempt to open a different file. Even if the service succeeds, the administrator should repair the problem. To repair the problem, use the following procedure:
To resolve this issue, use the resolution that corresponds to the cause you identified in the Diagnose section. After performing the resolution, see the Verify section to confirm that the feature is operating properly. Cause :
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. Open the renamed log file The log file associated with the channel has version that is too new or too old for the Event Log to use correctly. To fix this problem, open the renamed log file on the system where the file was created. Reconfigure the location to the log file To change the path to a log file, open Event Viewer, right-click on the log to update, and select Properties. Change the value of the Log path field and click Apply. 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. |
| Reference Links | Event ID 23 from Microsoft-Windows-Eventlog |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.