Logs could not be interpreted; review MSExchangeIS event 9513


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 event, do one or more of the following:

  • Review the description of the event that includes the variables specific to your environment. From the Operator Console, select this alert, and then click the Properties tab.

  • Review all events that have been logged that meet the criteria of this Operations Manager alert. 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.


Product Name


Product Version

8.0 (Exchange Server 2007)

Event ID


Event Source


Alert Type

Critical Error

MOM Rule Path

Microsoft Exchange Server/Exchange 2007/Mailbox/Information Store

MOM Rule Name

Logs could not be interpreted; review MSExchangeIS event 9513.


This event indicates that the Exchange Information Store service that is using the Extensible Storage Engine (ESE) was unable to interpret transaction log files caused by corruption. This event might occur in the following situations:

  • When you try to mount a database after a crash (when the database is in a dirty shutdown state).

  • When you try to restore a database from backup.

In both situations, the ESE engine will replay log files into the database. If the ESE engine detects corruption in the log files, the operation to either mount the database or restore the database from backup will not be completed successfully.

User Action

To resolve this issue, do one or more of the following:

  • Look for related ESE events in the Application event log. The related ESE events will give you detailed error information to help you resolve this problem.

  • Try to remount the database or try to restore the database from backup.

  • Attempt to restore the database leading up to the sequence of the corrupted log file (without the corrupted log file and the log files that follow the corrupted log file in sequence). In this case, be aware that you will lose all data that follows in sequence starting with the corrupted log file.

  • If the issue persists, 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 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.