Corruption was detected during soft recovery in the log file
Topic Last Modified: 2007-11-16
The Microsoft Exchange Server 2007 Management Pack for Operations Manager 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 alert, if you are using Microsoft Operations Manager 2005, do one or more of the following:
From the Operator Console, select this alert, and then click the Properties tab. Review the description of the alert that includes the variables specific to your environment.
From the Operator Console, click the Events tab, and then double-click the event in the list for which you want to review the event description. Review the events that have been logged that meet the criteria of this Operations Manager alert.
To learn more about this alert, if you are using System Center Operations Manager 2007, 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 events that have been logged that meet the criteria of this Operations Manager alert.
Details
Product Name |
Exchange |
Product Version |
8.0 (Exchange Server 2007) |
Event ID |
465 |
Event Source |
ESE |
Alert Type |
Warning |
MOM Rule Path |
Microsoft Exchange Server/Exchange 2007/Common Components/Extensible Storage Engine |
MOM Rule Name |
Corruption was detected during soft recovery in the log file. The log file is damaged and is unusable. This may be caused by faulty hardware. You may be able to repair this file. |
Explanation
This Error event indicates that corruption was detected in the log file during soft recovery. This log file is damaged and unusable. Soft recovery is an automatic transaction log file replay process that occurs when a database is remounted after an unexpected stop. The soft recovery process only replays logs from the transaction log file path specified for the storage group that contains the affected databases. Affected databases are described as having been shut down in a dirty state. Soft recovery uses the checkpoint file to determine which transaction log file to start with when it sequentially replays transactions into databases. This process makes the databases up to date with all recorded transactions.
User Action
To resolve this error, do one or more of the following:
Unless the log file specified is the current log file in use, restore the log file from a backup copy.
Use the Exchange Server Database Utilities (Eseutil.exe) tool with the /R and /A switches to recover a database with missing log files. For more information, see Eseutil /R Recovery Mode.
If you are having difficulty resolving the issue, contact Microsoft Product Support. For information about contacting support, visit the Contact Us page of the Microsoft Help and Support Web site.
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.