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.
<process> (ID) Corruption was detected during soft recovery in logfile <log file>. The failing checksum record is located at position <position>. Data not matching the log-file fill pattern first appeared in sector <sector>. This logfile has been damaged and is unusable.
|English: Request a translation of the event description in plain English.|
As per Microsoft: "This issue can occur if the log mentioned in the Event has become corrupted. Exchange cannot repair damage to log files because of factors other than torn writes, which will be fixed automatically by the ESE engine. Hardware failures that randomly damage a log file cannot be overcome because the data that was obliterated cannot be reliably reconstructed. ESE event 465 indicates damage that cannot be repaired". See MSEX2K3DB for more details.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated