Exchange: Event ID 508 "Information Store A request to write took an abnormally long time"

Summary:

Event ID: 503 Application ESE. Information Store (8260) EX3-SG4: A request to write to the file "P:\EX3-SG4-MB1\EX3-SG4-MB1.edb" at offset 336986112 (0x0000000014160000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (66 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. For more information, click http://www.microsoft.com/contentredirect.asp

Cause #1

This is likely due to excessive disk checking on a hard drive.

Resolution: Examine your hardware vendor's Event log to check for excessive disk checking and replace disk according to vendor's specification.


Cause #2

In some instances this is due to eseutil running during backup process to verify integrity of the backup. I've seen this on an Exchange server that was running Veritas to snapshot the Exchange database and this would occur when Veritas would perform eseutil to verify the integity of the database which is a very disk I\O intensive.

Resolution: Run performance baseline to check out disk I\O





James Chong (MVP)
MCITP | EMA; MCSE | M+, S+
Security+, Project+, ITIL
msexchangetips.blogspot.com