%1: The database could not be opened because a log file is missing or corrupted. The Microsoft Exchange Transport service is shutting down. Manual database recovery or repair may be required. The exception is %2.

Details
Product: Exchange
Event ID: 17005
Source: MSExchangeTransport
Version: 8.0
Symbolic Name: JetLogFileError
Message: %1: The database could not be opened because a log file is missing or corrupted. The Microsoft Exchange Transport service is shutting down. Manual database recovery or repair may be required. The exception is %2.
   
Explanation

This Error event indicates that one or more of the Extensible Storage Engine (ESE) transaction log files that is used by the specified message queue database or Content Filtering database on the Hub Transport server or Edge Transport server is missing or corrupted.

ESE databases use log files to accept, track, and maintain data. To enhance performance, all message transactions are written first to log files and memory, and then to the database file. Changes to the database are first written to the transaction log and are then committed to the database.

Trn.log is the current active transaction log file. Trntmp.log is the next provisioned transaction log file that is created in advance. If the existing Trn.log transaction log file reaches its maximum size, Trn.log is renamed to Trnnnnn.log, where nnnn is a sequence number. Trntmp.log is then renamed Trn.log and becomes the current active transaction log file.

Circular logging is used for the message queue database. This means that the history of committed transactions that are found in the transaction logs is not maintained. Any transaction logs that are older than the current checkpoint are immediately and automatically deleted. Therefore, the transaction logs cannot be replayed for queue database recovery from backup.

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

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

   
User Action

To resolve this error, follow these steps:

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

  2. Note the name of the database that is specified in the error message text. Verify that the corresponding transaction log location that is specified by the QueueDatabaseLoggingPath parameter or the IPFilterDatabaseLoggingPath parameter in the EdgeTransport.exe.config application configuration file exists, and has the correct permissions assigned to it.

  3. Remove any existing transaction log files that exist in the specified directory. The files are named Trn.log or Trnnnnn.log.

  4. Start the Microsoft Exchange Transport service. New transaction logs will be created automatically.

For more information, see the following topics:

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.

Related:

Leave a Reply