%1 (%2) %3The database page read from the file “%4” at offset %5 for %6 bytes failed verification due to a page number mismatch. The expected page number was %8 and the actual page number 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: 475
Source: ESE
Version: 8.0
Symbolic Name: DATABASE_PAGE_NUMBER_MISMATCH_ID
Message: %1 (%2) %3The database page read from the file “%4” at offset %5 for %6 bytes failed verification due to a page number mismatch. The expected page number was %8 and the actual page number 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 because of a page number mismatch. This means that the particular database page referenced within the Exchange store file (such as priv1.edb) is corrupted. Event 475 is always associated with a -1018 error in the Description section of the event.

The following are several possible symptoms:

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

  • Online defragmentation reports a -1018 checksum mismatch error.

Occurrence of event 475 indicates damage at the page level of the database. Damage at the page level is caused by driver, firmware, or hardware issues 99 percent of the time.

   
User Action

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

  • Run system diagnostic tests. These tests may not be conclusive if the problem is infrequent and transient or only appears under very complex loads.

  • Consider migrating to different hardware.

  • Upgrade disk controller BIOS and firmware to the latest vendor revisions.

  • Repair the database with the eseutil /p command, run eseutil /d, and then run isinteg -fix.

For more information about -1018 errors, see 314917, Understanding and analyzing -1018, -1019, and -1022 Exchange database errors.

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