Detected data inconsistency
Topic Last Modified: 2007-11-16
The Microsoft Exchange Server 2007 Management Pack for Microsoft Operations Manager (MOM) 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 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 |
448 |
Event Source |
ESE |
Alert Type |
Warning |
MOM Rule Path |
Microsoft Exchange Server/Exchange 2007/Common Components/Extensible Storage Engine |
MOM Rule Name |
Detected data inconsistency. Check the Application log carefully for related events and patterns that may relate to this event. You may have to restore from online backup. |
Explanation
This Warning event indicates that there is a corruption or inconsistency in a table in the ESE database. Check the Application log carefully for related events and patterns that may relate to this event. Check the System log carefully for related events and patterns including any errors related to hardware, drives, controllers, or the file system.
User Action
To resolve this warning, do one or more of the following:
Check the Application log carefully for related events and patterns that may relate to this event. Check the System log carefully for related events and patterns including any errors related to hardware, drives, controllers, or the file system. If there are any such errors, replace the hardware, update the hardware system files, or repair the file system to prevent any future errors. Do this before you continue with the next step.
If the Exchange store database is running, use ExMerge to put your data in .pst files, delete the database, create a blank database, and then use ExMerge to copy your databases to a blank database.
If the database is running, you may also move all the mailboxes to another store, delete the affected database, create a new database, and then move all the mailboxes back.
If the Exchange store database will not mount, the suggested solution is to restore from online backup before the errors appear in the Application log.
If the Exchange store database will not mount and there is no backup, the last resort is to repair the database by running eseutil /p and then repeatedly running isinteg -fix until there are no fixes reported. Then run ExMerge, create a blank store, and run ExMerge to add the data back.
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.