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.
Successfully re-opened the local eventlog - NOTE: Some events may have been missed.
|English: Request a translation of the event description in plain English.|
From a newsgroup post: "This means SQL Agent is unable to read local event log, can happen if you clear down the eventlog, however, I believe this can also happen if the readeventlog() call fails because the Buffer it uses to read the eventlog information is not large enough, it then resizes the buffer the next time it makes the call, with the information provided in the previous failure, so it is a fairly benign error and can be safely ignored, unless it is happening constantly I guess. The only downside is any alerts you set up may be delayed."
|Private comment: Subscribers only. See example of private comment|
|Links: EventID 312 from source SQLExecutive|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated