MSExchangeTransport 17003

 

上一次修改主题: 2011-03-19

本文对特定 Exchange 事件进行了说明并提供了可能的解决方案。如果您在此处未找到所需内容,请尝试在 Exchange 2010 帮助中进行搜索。

Details

Product Name

Exchange

Product Version

14.0

Event ID

17003

Event Source

MSExchangeTransport

Category

Storage

Symbolic Name

JetCorruptionError

Message Text

%1: An 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. Exception details: %2

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:

  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 topics:

For More Information

如果您尚未执行此操作,请考虑运行 Exchange 工具,已创建这些工具以帮助您分析 Exchange 环境并对其进行疑难解答。这些工具可帮助确保您的配置与 Microsoft 最佳实践保持一致。它们还可以帮助您识别和解决性能问题,并改进邮件流。若要运行这些工具,请转到 Exchange 管理控制台的“工具箱”节点。若要了解有关这些工具的详细信息,请参阅管理工具箱中的工具