The streaming page read from a file failed verification because of a page checksum mismatch
Applies to: Operations Manager Management Pack for Exchange 2010
Topic Last Modified: 2011-09-29
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 |
478 |
Event Source |
ESE |
Category |
KHI |
Alert Type |
Error |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Common Components/Extensible Storage Engine |
Rule Name |
The streaming page read from a file failed verification because of a page checksum mismatch. |
Explanation
This Warning event indicates that the streaming database that is specified in the message is corrupted. The event description provides details about the error that occurred.
Frequently, the following error is associated with this event:
Error -613 = 0xfffffd9b = Jet_errSLVReadVerifyFailure = Checksum error in SLV file during backup. Error -613 resembles error -1018. Exchange logs error -613 for checksum errors on the .stm database file and logs error -1018 for checksum errors on the .edb database file. Checksums for pages in the .stm file are stored in a table in the .edb file. The .edb and .stm files may be out of sync. An older copy of the .stm file may be in use, and the checksum table in the .edb file is therefore out of date. A program may have altered the .stm file without updating the checksums in the .edb file. There could be problems with the hard disk subsystem or controllers of the system.
User Action
To resolve this problem, do one or more of the following:
Determine the root cause of the corruption. To do this, check the System log, run Chkdsk, and perform other diagnostic tasks. If you do not determine and fix the root cause of this warning, the corruption problem may occur again, even if you repair the databases or restore the databases from a backup.
Temporarily disable or remove the antivirus software or the third-party software. This may help identify the root cause of this event.
Restore the Exchange store from the previous online backup.
Move the mailboxes to another server or mailbox store. If the public folder store is affected, replicate the content of the public folders to another server.
As a last resort, if there is no valid online backup, perform a repair by using Eseutil /p, and then run isinteg. If the resolution requires a repair, you cannot repair the .stm file alone. You must repair the .edb file and its associated .stm file. After this procedure is completed, the database may not be stable or reliable. Therefore, you should immediately move the data out of the repaired database to a new database. Alternatively, you can rebuild the affected database.
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.