| Event Id | 510 |
| Source | ESE |
| Description | A request to write to the file %2 at offset %3 for %4 bytes succeeded, but took an abnormally long time (%5 seconds) to be serviced by the OS. In addition, %6 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 %7 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. |
| Event Information | According to Microsoft: Explanation: This Warning event is logged when the Exchange database engine tries to write to the named file and encounters a delayed response from the operating system in performing that write operation. This is a warning, not an error, because the operation eventually finishes, although it is slow. This might indicate a hardware problem, probably with the disk controller, a disk, or other storage component. User Action: Because this event typically indicates a problem with your disk subsystem or other server hardware, you should carefully examine the performance of the hardware in your Exchange server environment. If available, run hardware diagnostics provided by the server manufacturer. If there are specific tests available to test the disk subsystem, run those tests also. Running these hardware tests may help you discover the cause of the performance bottleneck. If the server uses a SAN device, make sure that the SAN has been configured correctly. According to Microsoft: Explanation: A request to write Exchange data to 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 Article "Optimizing Storage for Exchange Server"listed in More information. According to some newsgroup post: This problem may be logged when Disk defragmentation is running at same time as the mailboxes is being backed up.A defrag in progress can lock the .edb database and cause the same errors as a hardware problem. Make sure that no defragmentation of the HDD is in progress. |
| Reference Links | Exchange (ESE) Optimizing Storage for Exchange Server |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.