%1 (%2) %3 Unable to read page %5 of database %4. Error %6.

Product: Exchange
Event ID: 419
Source: ESE
Version: 6.5.7596.0
Message: %1 (%2) %3 Unable to read page %5 of database %4. Error %6.

This Error event indicates that Microsoft® Exchange Server cannot read a page of a database as specified in the description of this event. Specifically, this event can be logged during a recovery operation if a page of a database cannot be read. If a page of a database cannot be read, the recovery or restore process fails.

To understand the cause of this event, it is helpful to understand how transaction log replay works in coordination with the pages of an Exchange Server database. When a recovery operation runs, Exchange Server first makes sure that the logical page number written on the page is correct. Then, Exchange Server makes sure that the page checksum is good. Changes for a page are associated with a sequence number in the log file.

Exchange Server includes the functionality to detect file-level damage to pages in its databases. The error associated with this event is specified in the description of the event.

The following are the most common errors that are associated with file-level damage to an Exchange Server database:

  • -1018 JET_errReadVerifyFailure

  • -1019 JET_errPageNotInitialized

  • -1022 JET_errDiskIO

Error -1018 is the most frequently seen error. This indicates that an Exchange Server database has suffered damage at the file system level. Almost always, you will find the root cause for a -1018 error in one of the underlying systems that Exchange Server depends on, not in Exchange Server code itself. There are very few exceptions to this rule. The exceptions to date have been with regard to Exchange Server reporting a -1018 condition, not because Exchange Server itself causes a -1018 error.

Most -1019 and -1022 errors are also caused by a fault in an underlying system. However, you cannot rule out the chance that -1019 and -1022 errors might occur because of an issue unrelated to the file system.

For more information about -1018, -1019 and -1022 errors, see following Microsoft Knowledge Base articles:

User Action

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

  • Try to restore the Exchange Server database from backup. For information about how to recover Exchange Server databases, see the Exchange 2003 Disaster Recovery Operations Guide. For more information about recovering Exchange Server databases, see Microsoft Knowledge Base article 313184, How to recover the information store on Exchange 2000 Server or Exchange Server 2003 in a single site.

  • Try to repair the database using the Exchange Server Eseutil and Isinteg utilities. For information about repairing Exchange Server databases, see “Repairing Exchange Databases” in the Exchange 2003 Disaster Recovery Operations Guide.

  • Run the Exchange Server Disaster Recovery Analyzer Tool on the servers in your Exchange Server 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 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.


Leave a Reply