A Transport database operation has encountered a fatal error. The Transport service is shutting down.
Applies to: Operations Manager Management Pack for Exchange 2010
Topic Last Modified: 2011-08-02
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 |
17003 |
Event Source |
MSExchangeTransport |
Alert Type |
Error |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Common Components/Hub Transport and Edge Transport/Transport |
Rule Name |
A Transport database operation has encountered a fatal error. The Transport service is shutting down. |
Explanation
This Error event indicates that the specified Extensible Storage Engine (ESE) database is corrupted and is preventing the Microsoft Exchange Transport service from starting.
The ESE databases that may exist on a Hub Transport server or Edge Transport server are the message queue database or the Content Filtering database.
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, do one of the following:
Delete the specified database and the corresponding transaction logs. A new copy of the database and the transaction logs is created automatically. Use this option if you don't care about the contents of the specified database.
Try to repair the database. After the database is repaired, you can try to restart the Microsoft Exchange Transport service
To delete the specified database and corresponding transaction logs, follow these steps:
Verify that the Microsoft Exchange Transport service is stopped.
Delete the specified database files and the corresponding transaction log files. The database files and the transaction log files are described in the following list:
Mail.que or IpFiltering.edb The main database file
Trn.chk The checkpoint file
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 or the Content Filtering database does not exist, a new, empty database is created. If the message queue database transaction logs or the Content Filtering database transaction logs do not exist, new logs are created.
To repair the specified database, follow these steps:
Verify that the Microsoft Exchange Transport service is stopped.
Run the Eseutil /P utility on the specified database. For information about the Eseutil /P procedure, see How to Run Eseutil /P (Repair). The repair can take a long time on a large database.
If the affected database is the message queue database, you can move the database files to another location, and then start the Microsoft Exchange Transport service to create a new message queue database. This lets you perform the database repair without any loss of functionality on the Hub Transport server or Edge Transport server. After the message queue database has been repaired, you can use any other Hub Transport server or Edge Transport server to deliver the messages that are trapped inside the repaired database. For more information, see Working with the Queue Database on Transport Servers.
Start the Microsoft Exchange Transport service. If the Microsoft Exchange Transport Service still does not start because of database corruption errors, you must move or delete the specified database and allow a new copy of the database to be created.
For more information, see the following topics:
For More Information
If you are not already doing so, consider running the Exchange tools, which have been 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 and improve mail flow. 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.