|Component:||Microsoft Exchange Extensible Storage Engine|
|Message:||<process name> (<process id>) <storage group name>The database page read from the file “<file name>” at offset <value> for <number> bytes failed verification because it contains no page data. The read operation will fail with error <error code>. If this condition persists then please restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.|
ESE Event ID 476 indicates that the database page read from Exchange database failed verification because it contains no page data. The read operation will fail with error -1019. This essentially means that the particular database page referenced within the Exchange database file named (such as priv1.edb) is empty when it is expected to be in use. Event ID 476 is always associated with a -1019 error in the Description section of the event.
Generally, resolve a -1019 error the same way you would resolve a -1018 error. Exhaustively check the application log for evidence of any -1018 errors that would be found in the Description section ESE events. The standard resolution of a -1018 error follows below. Use this method to resolve -1019 errors.
Resolution of -1018 Errors
After a system administrator encounters a -1018 error, if the administrator runs diagnostic hardware tests against the server and these tests report no issues, the administrator might conclude that Exchange must be responsible for the issue because the hardware passed the initial analysis. However, in case after case, further investigation by Microsoft or hardware vendors uncovered subtle issues in hardware, firmware, or device drivers that are actually responsible for damaging the database file. Ordinary diagnostic tests might not detect all of the transient faults for several reasons. Issues in firmware or driver software might fall outside the capabilities of diagnostic programs. Diagnostic tests might be unable to adequately simulate long run times or complex loads. Also, the addition of diagnostic monitoring or debug logging might change the system enough to prevent the issue from appearing again.
The first step is to use one of the three methods below to move the existing databases to new hardware:
The second step is to diagnose and correct the original hardware problem by checking the system log, and running extensive tests from the hardware manufacturer on the hardware, firmware, raid controllers, and device drivers. Then you can use Move Mailbox to move the users back, or restore from online back to the repaired machine.
Definitely do not simply repair the existing database or restore from online backup until the hardware errors have been diagnosed and corrected. You must diagnose and correct the hardware errors before repairing, restoring, moving your mailboxes back, or ExMerging your data back or the -1018 errors will come back because the root cause has not been fixed.