A log range read failed verification because of a range checksum mismatch
Topic Last Modified: 2007-11-16
The Microsoft Exchange Server 2007 Management Pack for Microsoft Operations Manager (MOM) monitors the Windows event 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.
Details
Product Name |
Exchange |
Product Version |
8.0 (Exchange Server 2007) |
Event ID |
477 |
Event Source |
ESE |
Alert Type |
Warning |
MOM Rule Path |
Microsoft Exchange Server/Exchange 2007/Common Components/Extensible Storage Engine |
MOM Rule Name |
A log range read failed verification because of a range checksum mismatch. You may not be able to perform backup or restore processes. This may be caused by damaged storage hardware. |
Explanation
This Warning event indicates that a checksum in a transaction log file failed verification. This error is similar to error -1018 in a database file, and indicates the log file has been damaged in the file system.
This issue can occur if the log file mentioned in the event has become corrupted. Exchange cannot repair damage to log files because of factors other than torn writes, which will be fixed automatically by the ESE. Hardware failures that randomly damage a log file cannot be overcome because the data cannot be reliably reconstructed. ESE event 477 indicates damage that cannot be repaired. The following are the most common error codes associated with this event:
Error -501 = 0xfffffe0b = Jet_errLog fileCorrupt = Log file corrupt. An error -1022 is returned from corrupting the header of a log file. Corrupting other areas of the log file returns a -501 Jet_errLog fileCorrupt error. You may not be able to mount an Exchange store database due to the corrupted log file because the database has become inconsistent.
Error -612 = 0xfffffd9c = Jet_errLogReadVerifyFailure = Checksum error in log file during backup. This indicates a corrupt transaction log file. A backup cannot be made of a corrupt log file and the backup will fail. A checksum ESE error indicates a hardware root cause and is caused by hardware, controller, or file system-level problems related to hardware. You may not be able to successfully perform an online backup of an Exchange store database.
Error -573 = 0xfffffdc3 = Jet_errLogCorruptDuringHardRestore = Corruption was detected in a backup set during hard restore. You may not be able to successfully complete an online restore of an Exchange store database due to a corrupted transaction log in the restore set.
For information about ESE error codes other than the ones explained in this topic, see the following Microsoft Knowledge Base articles:
266361, Extensible Storage Engine 98 Error Codes 0 to -1048
266367, Extensible Storage Engine 98 Error Codes -1051 to -999999
This warning may indicate that the log file cannot be repaired.
User Action
To resolve this warning, do one or more of the following:
Run diagnostic tests on your hardware.
Repair or replace your damaged hardware.
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.