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.
|Source: NTDS ISAM|
NTDS (<PID>) NTDSA: A request to write to the file "<file>" at offset <offset> (<offset>) for <size> (<size>) bytes succeeded but took an abnormally long time (<number> seconds) to be serviced by the OS. In addition <number> other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted <number> seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
|English: Request a translation of the event description in plain English.|
This error occurred when a physical drive failed in a SCSI RAID array. The performance of the array decreased significantly until the raid controller finished rebuilding the array using an online spare; therefore, Active Directory had a difficult time writing to the database. Rebuilding the array solved this issue.
|Private comment: Subscribers only. See example of private comment|
|Links: EventID 510 from source ESE|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated