Database page read failed verification because of a -1018 error (page checksum mismatch). This error is often caused by hardware issues
Applies to: Operations Manager Management Pack for Exchange 2010
Topic Last Modified: 2012-02-27
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 |
474 |
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 a -1018 error (page checksum mismatch). This error is often caused by hardware issues. |
Explanation
This Error event indicates that a database page read failed verification because of a page checksum mismatch. The particular database page that is referenced within the Exchange store file (for example, priv1.edb) is corrupted.
When this problem occurs, you may experience one or more of the following symptoms:
Users cannot send or receive e-mail messages.
You cannot start Microsoft Outlook on your client computer.
Online backups fail to finish, and you receive a -1018 checksum error.
Online defragmentation reports a -1018 checksum mismatch error.
This error indicates some level of unreliability in the underlying platform to correctly store or retrieve data from the Microsoft Exchange Server database file. In some cases, the page in the database has not been damaged. In these cases, you receive the following message: “The error may be transient if the problem is in RAM or caused by a firmware malfunction rather than because the actual page in the database has been damaged.”
Alternatively, Error -1811 (hexadecimal 0xFFFFF8ED) corresponds to JET_errFileNotFound and is described as File not found.
User Action
To resolve this error, do one or more of the following:
If the error code listed in the event description is -1018, see ESE 474 -1018: Unrecoverable Error Detected in Database.
Run system diagnostic tests. These tests may not be conclusive if the problem is infrequent and transient, or if it occurs only under very complex loads.
Consider migrating to different hardware.
Upgrade the disk controller BIOS and firmware to the latest vendor revisions.
For more information, see 314917, Understanding and analyzing -1018, -1019, and -1022 Exchange database errors.
Repair the database by using the following commands, in this order:
eseutil /P
eseutil /D
isinteg -fix
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.