Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 509 Source: ESE
Information Store (<PID>) First Storage Group: A request to write to the file "<file>" at offset <offset> (<offset>) for <value> (<value>) bytes succeeded but took an abnormally long time (<value> seconds) to be serviced by the OS. In addition <value> 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 <value> 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.|
In my case, file system defragmentation was in progress when the events were logged. For information about file system defrag on Exchange databases from the Exchange Development team, see the link to "The Microsoft Exchange Team Blog".
As per Microsoft: "This problem may be caused by faulty hardware. This problem may also be caused if the server or disk subsystem is not correctly configured". See MSEX2KDB for additional information about this event.
From a newsgroup post: "It sounds like there is a hardware problem that is showing up during either the Backup or IS maintenance, which both run at night. As a start one recommendation is to make sure that IS maintenance and the Backup are not running at the same time as they will conflict.
In addition, another recommendation is to make sure that your storage solution is optimized. Read ME317173 and ME326294 for details on this issue". See the link to "Google thread - Event ID 509" for the original thread.
|Private comment: Subscribers only. See example of private comment|
|Links: ME317173, ME326294, Google thread - Event ID 509, The Microsoft Exchange Team Blog, MSEX2KDB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated