%1 (%2) %3 The database page read from the file “%4” at offset %5 (database page %8) for %6 bytes failed verification. Bit %7 was corrupted and has been corrected. This problem is likely due to faulty hardware and may continue. Transient failures such as these can be a precursor to a catastrophic failure in the storage subsystem containing this file. Please contact your hardware vendor for further assistance diagnosing the problem.

Details
Product: Exchange
Event ID: 399
Source: ESE
Version: 6.5.7596.0
Message: %1 (%2) %3 The database page read from the file “%4” at offset %5 (database page %8) for %6 bytes failed verification. Bit %7 was corrupted and has been corrected. This problem is likely due to faulty hardware and may continue. Transient failures such as these can be a precursor to a catastrophic failure in the storage subsystem containing this file. Please contact your hardware vendor for further assistance diagnosing the problem.
   
Explanation

Microsoft® Exchange Server 2003 Service Pack 1 (SP1) introduced a new error-correcting code (ECC) algorithm to help resolve -1018 errors that may occur in an Exchange Server database. ESE event 399 indicates that a single-bit error has been detected, and that this error has been successfully corrected in memory. In this scenario, the page where this error occurred may have been corrected on the physical hard disk. The single-bit error is not corrected on the physical hard disk unless the page has been written to. Therefore, if the database page is only read, the single-bit error is corrected in memory, but the single-bit error is not corrected on the physical hard disk.

For information about the error-correcting code (ECC) algorithm introduced in Exchange Server 2003 Service Pack 1 (SP1), see 867626, New error correcting code is included in Exchange Server 2003 SP1.

   
User Action

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

  • Examine the Application log for related ESE events such as ESE event 474. For information about ESE event 474, search the Events and Errors Message Center Web site.

  • Run the Exchange Server Disaster Recovery Analyzer Tool on the servers in your Exchange environment. The Exchange Server Disaster Recovery Analyzer Tool examines an Exchange Server deployment when an Exchange Server database does not mount. Based on the problem found, the tool automatically generates step-by-step instructions to bring the database online. The Exchange Server Disaster Recovery Analyzer can be used with Exchange 2000 Server and Exchange Server 2003. For information about how to download and run this and other Microsoft Exchange Server Analyzer tools, see the Microsoft Exchange Server Analyzer Tools Web page.

  • Contact your hardware vendor for more help diagnosing the problem. For example, hardware vendors may be able to help you identify any firmware or device driver issues that may be causing the problem.

For detailed information about understanding and analyzing -1018, -1019, or -1022 Exchange Server database errors, see Microsoft Knowledge Base article 314917, Understanding and analyzing -1018, -1019, and -1022 Exchange database errors.

For information about how the Microsoft Information Technology group (Microsoft IT) recovers from -1018 errors, see Exchange Server Error –1018: How Microsoft IT Recovers Damaged Exchange Databases.

Related:

Leave a Reply