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.
Information Store (<pid>) Error <error> occurred while opening log file <file>.
|English: Request a translation of the event description in plain English.|
In my case, I made a copy of a log file that had the same naming convention as the log file stated in the event description and renamed that copy so that the file will replace the log that was causing the error. This solved the problem.
- Error: -1811 - This error might occur when an unplanned loss of power (such as a rolling power outage) on a running Windows 2000 DC prevents Active Directory from reading either the NTDS.DIT or log files on next boot. See ME265089 for details.
- Error: -1811 - See ME294367, ME296843, ME314916, ME819553, and ME896143 to fix this problem.
See MSEX2K3DB, ME895856, and the link to "Veritas Support Document ID: 248098" for additional information.
I had this event because I had moved my log files and not told my Antivirus software not to scan the new location. The “E00.log” file got scanned and quarantined. To repair I simply restored the log file from quarantine and restarted the Exchange Information Store which restored everything with no problems.
|Private comment: Subscribers only. See example of private comment|
|Links: ME265089, ME294367, ME296843, ME314916, ME819553, ME895856, ME896143, Veritas Support Document ID: 248098, MSEX2K3DB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated