Database page read failed verification because of no page data


Topic Last Modified: 2007-11-16

The Microsoft Exchange Server 2007 Management Pack for Microsoft Operations Manager (MOM) monitors the Windows Application log on computers that are running Exchange Server 2007 and generates this alert when the event or events specified in the following Details table are logged.

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

  • Review the description of the event that includes the variables specific to your environment. From the MOM Operator Console, select this alert, and then click the Properties tab.

  • Review all events that have been logged that meet the criteria of this MOM alert. From the MOM Operator Console, click the Events tab, and then double-click the event in the list for which you want to review the event description.


Product Name


Product Version

8.0 (Exchange Server 2007)

Event ID


Event Source


Alert Type

Critical Error

MOM Rule Path

Microsoft Exchange Server/Exchange 2007/Common Components/Extensible Storage Engine

MOM Rule Name

Database page read failed verification because of no page data. This results in ESE errors -1018 and -1019. Move existing databases to new hardware.


This Error event indicates that the database page read from Exchange store database failed verification because it contains no page data. The read operation will fail with error -1019. The particular database page referenced within the Exchange store file (such as priv1.edb) is empty when it is expected to be in use.

Event 476 is always associated with a -1019 error in the Description section of the event. Error -1019 = 0xfffffc05 = Jet_errPageNotInitialized = Blank database page. Error -1019 is reported when a page that is expected to be in use is not initialized or empty. If the page number field on a page in use is 0x00000000, a -1019 error is reported instead of a -1018 error, even though the page might also fail its checksum test. A -1019 error may be caused because the file system was corrupted or it mapped pages into the database file that do not belong in the file. A -1019 error may also be caused by Exchange if logical pointers or links between pages are inaccurate.

ESE event 476 may also be related to -1018 errors that may be included in the event descriptions of other ESE events in the Application log. Error -1018 = 0xfffffc06 = Jet_errReadVerifyFailure = Checksum error on a database page. The root cause of -1018 errors is frequently because of faulty hardware.


A -1019 issue may go undetected longer than a -1018 issue because -1019 issues are not detected by online backup.

User Action

To resolve this Error event, 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 by using the eseutil /p command, run eseutil /d, and then run isinteg -fix.

For detailed information about how to troubleshoot -1018 and -1019 errors, see Microsoft Knowledge Base article 314917, Understanding and analyzing -1018, -1019, and -1022 Exchange database errors

For More Information

To search the Microsoft Knowledge Base articles based on criteria that generated this alert, visit the Search the Support Knowledge Base (KB) Web site.

To review Exchange 2007 event message articles that may not be represented by Exchange 2007 MOM alerts, see the Events and Errors Message Center.

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.