Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
<service> (<PID>) Unable to read the header of logfile <file>. Error <error code>.
|English: Request a translation of the event description in plain English.|
In my case, the header of a logfile was corrupted when a disk went offline following an offline defrag of the Exchange 2000 database. I ran eseutil /mh on the applicable databases and found that they were in a clean state. I relocated the E0?.log files to another folder, mounted the databases and the problem was solved.
Look at MSEX2K3DB and "EventID 412 form source ESENT" for details on this error.
|Private comment: Subscribers only. See example of private comment|
|Links: EventID 412 from source ESENT, MSEX2K3DB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated