Topic Last Modified: 2010-02-22

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	17007
Event Source	MSExchangeTransport
Alert Type	Error
Rule Path	Microsoft Exchange Server/Exchange 2010/Common Components/Hub Transport and Edge Transport/Transport
Rule Name	The database file doesn't match the log files. The Microsoft Exchange Transport service is shutting down.

Explanation

This Error event indicates there is a version mismatch between an Extensible Storage Engine (ESE) database and its corresponding transaction logs on the Hub Transport server or Edge Transport server. The ESE database that is specified in the error message text could be the message queue database or the Content Filtering database.

The message queue database and the Content Filtering database use circular logging. Therefore, you can't use the transaction logs for data recovery. Additionally, the transaction logs are recreated automatically during the startup of the Microsoft Exchange Transport service if they are missing.

By default, the message queue database and the transaction logs are located at C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\Queue. The location of the message queue database is controlled by the QueueDatabasePath parameter in the EdgeTransport.exe.config application configuration file. The location of the message queue transaction logs is controlled by the QueueDatabaseLoggingPath parameter in the EdgeTransport.exe.config application configuration file.

By default, the Content Filtering database and the transaction logs are located at C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\IpFilter. The location of the Content Filtering database is controlled by the IPFilterDatabasePath parameter in the EdgeTransport.exe.config application configuration file. The location of the Content Filtering database transaction logs is controlled by the IPFilterDatabaseLoggingPath parameter in the EdgeTransport.exe.config application configuration file.

The EdgeTransport.exe.config application configuration file is located in C:\Program Files\Microsoft\Exchange Server\V14\Bin.

User Action

To resolve this error, follow these steps:

Verify that the Microsoft Exchange Transport service is stopped.
Delete or move the transaction log files in the transaction log directory that corresponds to the database that is specified in the error message text. The transactions logs are described in the following list:
- Trn*.log The transaction logs
- Trnres*.jrs The reserved transaction logs that serve as placeholders
- Temp.edb A sample database file that is used to verify the database schema. Although this is not a transaction log file, it is always kept with the transaction logs.
Start the Microsoft Exchange Transport service. If the message queue database transaction logs or the Content Filtering database transaction logs do not exist, new logs are created.

For more information, see the following topics:

Understanding Transport Queues
Change the Location of the Queue Database

For More Information

If you are not already doing so, consider running the Exchange tools 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, improve mail flow, and better manage disaster recovery scenarios. 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.