• Article

Corruption was detected during soft recovery in the log file

 

Applies to: Operations Manager Management Pack for Exchange 2010

Topic Last Modified: 2011-08-24

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

465

Event Source

ESE

Category

KHI

Alert Type

Error

Rule Path

Microsoft Exchange Server/Exchange 2010/Common Components/Extensible Storage Engine

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.

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 replay process of the transaction log file that occurs when a database is remounted after an unexpected stop. The soft recovery process replays only logs from the transaction log file path that is 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 problem, 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 that has missing log files. For more information, see Eseutil /R Recovery Mode.

the problem persists, you may require assisted support.

Contact a Microsoft Support professional to resolve this issue. To contact a Microsoft Support professional, visit the Exchange Server Solutions Center. In the navigation pane, click Assisted Support Options and use one of the assisted support options to contact a Microsoft Support professional. Because your organization may have a specific procedure for directly contacting Microsoft Product Support Services, be sure to review your organization's guidelines first.

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.