Export (0) Print
Expand All
Expand Minimize

A Transport database operation has encountered a fatal error

 

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

17003

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

A Transport database operation has encountered a fatal error. The database may be corrupted. The Microsoft Exchange Transport service is shutting down. Manual database recovery or repair may be required.

This Error event indicates that 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\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, 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:

  1. Verify that the Microsoft Exchange Transport service is stopped.
  2. 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.
  3. 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:

  1. Verify that the Microsoft Exchange Transport service is stopped.
  2. 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.
  3. 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 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