Database page read failed verification because of no page data. This results in ESE errors -1018 and -1019
Applies to: Operations Manager Management Pack for Exchange 2010
Topic Last Modified: 2012-03-08
The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.
To learn more about this alert, in Operations Manager, do one or more of the following:
From the Operations Console, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.
From the Operations Console, double-click this alert, and then click the Alert Context tab. Review the logged events that meet the criteria of this Operations Manager alert.
Details
Product Name |
Exchange |
Product Version |
14.0 (Exchange 2010) |
Event ID |
476 |
Event Source |
ESE |
Category |
KHI |
Alert Type |
Error |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Common Components/Extensible Storage Engine |
Rule Name |
Database page read failed verification because of no page data. This results in ESE errors -1018 and -1019. |
Explanation
This Error event indicates that the database page read from the Microsoft Exchange Server store database failed verification because it contains no page data. The failed read operation generates error -1019. The particular database page that is referenced within the Exchange store file (for example, priv1.edb) is empty when you expect it to be in use.
Event 476 is always associated with a -1019 error in the event description. 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 is empty. If the value is 0x00000000 in the page number field on a page that is in use, a -1019 error is reported instead of a -1018 error. This is true even though the page might also fail its checksum test. A -1019 error may be occur because the file system is corrupted or because it mapped pages that do not belong into the database file. A -1019 error may also occur 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 faulty hardware.
Note
A -1019 issue may go undetected longer than a -1018 issue. This is because -1019 issues are not detected by online backups.
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 if the problem occurs only under very complex loads.
Consider migrating to different hardware.
Upgrade the disk controller BIOS and the firmware on the computer to the latest vendor revisions.
Repair the database by using the following commands, in this order:
eseutil /P
eseutil /D
isinteg -fix
For more 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
If you are not already doing so, consider running the Exchange tools, which have been created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues and improve mail flow. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.