%1 (%2) %3The database page read from the file “%4” at offset %5 (database page %10) for %6 bytes failed verification due to a page checksum mismatch. The expected checksum was %8 and the actual checksum was %9. The read operation will fail with error %7. 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.

Details
Product: Exchange
Event ID: 474
Source: ESE
Version: 8.0
Symbolic Name: DATABASE_PAGE_CHECKSUM_MISMATCH_ID
Message: %1 (%2) %3The database page read from the file “%4” at offset %5 (database page %10) for %6 bytes failed verification due to a page checksum mismatch. The expected checksum was %8 and the actual checksum was %9. The read operation will fail with error %7. 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.
   
Explanation

This Error event indicates that a database page read failed verification due to a page checksum mismatch. The particular database page referenced within the Exchange store file (such as priv1.edb) is corrupt.

Possible symptoms are:

  • Users cannot send or receive e-mail messages.

  • You cannot start Microsoft Outlook on your client computer.

  • Online backups fail to complete with a -1018 checksum error.

  • Online defragmentation reports a -1018 checksum mismatch error.

This error indicates some level of unreliability in the underlying platform ability to correctly store or retrieve data from the Exchange database file. In some cases, the page in the database has not been damaged, and the error is: The error may be transient if the problem is in RAM or caused by a firmware malfunction rather than because the actual page in the database has been damaged.

Alternatively, Error -1811 (hexadecimal 0xFFFFF8ED) corresponds to JET_errFileNotFound and is described as File not found.

   
User Action

To resolve this error, do one or more of the following:

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Leave a Reply