Export (0) Print
Expand All
Expand Minimize

The database could not be opened because the database file does not match the log files

 

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

Exchange

Product Version

8.0 (Exchange Server 2007)

Event ID

17007

Event Source

MSExchangeTransport

Alert Type

Critical Error

MOM Rule Path

Microsoft Exchange Server/Exchange 2007/Common Components/Hub Transport and Edge Transport/Transport

MOM Rule Name

The database could not be opened because the database file does not match the log files. The Microsoft Exchange Transport service is shutting down.

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\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\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\Bin.

To resolve this error, follow these steps:

  1. Verify that the Microsoft Exchange Transport service is stopped.

  2. 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.

  3. 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 Microsoft Exchange Server 2007 Help topics:

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.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft