() A request to read from the file “” at offset for bytes succeeded, but took an abnormally long time ( seconds) to be serviced by the OS. In addition, 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 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Details
Product: Exchange
Event ID: 509
Source: ESE
Version: 6.5.7638.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <%1> (<%2>) <%3> A request to read from the file “<%4>” at offset <%5> for <%6> bytes succeeded, but took an abnormally long time (<%7> seconds) to be serviced by the OS. In addition, <%8> 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 <%9> seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
   
Explanation

A request to read Exchange data from the disk succeeded, but took an abnormally long time to be processed by the operating system. Additionally, other input/output (I/O) requests to this disk have also taken an abnormally long time to be serviced. The text of the event indicates specific information about this Warning event.

This problem may be caused by faulty hardware. This problem may also be caused if the server or disk subsystem is not correctly configured.

   
User Action

For information about the causes of Exchange Server disk I/O, how to calculate your disk I/O requirements and optimize your storage architecture, and how to verify the performance of your storage system, see “Optimizing Storage for Exchange Server 2003” (http://go.microsoft.com/fwlink/?linkid=49324).

For information about troubleshooting Exchange Server 2003 performance, including disk-bound performance issues, see “Troubleshooting Microsoft Exchange Server 2003 Performance” (http://go.microsoft.com/fwlink/?linkId=47588).

Contact your hardware vendor for additional help diagnosing the problem.

Related:

Leave a Reply