MSExchangeTransport 17021

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

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

Details

Explanation

This Error event indicates that the Microsoft Exchange Transport service was unable to access the Transport database on the Hub Transport server or on the Edge Transport server.

Starting with Microsoft Exchange Server 2007, the Microsoft Exchange Transport service uses an Extensible Storage Engine (ESE) database for mail queue storage. This design change improves read and write performance with respect to messaging queues and also lets the messaging queues be backed up. The Transport database consists of the following files:

• Mail.que: The ESE database

• Tmp.edb: The temporary workspace for processing transactions

• Trn.log: The current transaction log file

• Trntmp.log: The temporary transaction log file

• Trn.chk: The database checkpoint file

• Trnres00001.jrs: The first transaction reserve file

• Trnres00002.jrs: The second transaction reserve file

By default, these files are located in the following directory:

%ProgramFiles%\Microsoft\Exchange Server\V14\TransportRoles\data\Queue

This issue may occur when one or more of the following conditions are true:

• One of the database files is missing. This may occur when a file-level antivirus program has not been configured to exclude the Exchange-related files.

• The Transport database is damaged.

User Action

To troubleshoot this issue, do one or more of the following:

• 有关相关事件，请查看 Exchange 2010 服务器上的应用程序日志和系统日志。例如，在此事件之前和之后发生的事件可能会提供有关导致出现此错误的根本原因的详细信息。

• Review the Operations Console in Operations Manager for detailed information about the cause of this problem. For more information, see the "Introduction" section in this article.

• If a file-level antivirus scanner is running, verify that antivirus exclusions are configured appropriately. For more information, see Exchange 2010 上的文件级防病毒扫描.

• Determine whether any non-Exchange programs are accessing the Transport database files. To do this, follow these steps:

  1. Visit the following Web site to obtain the Handle. exe program:

     https://technet.microsoft.com/en-us/sysinternals/bb896655.aspx

  2. Extract Handle.exe from the downloaded archive, and then copy the file to a location on the affected Transport server.

  3. Run the following command, and replace database.edb by the name of the database file that is listed in the event:

     handle.exe "c:\program files\microsoft\exchange server\v14\transportroles\data\<foldername>\<databasename>"

  4. Determine whether any non-Exchange processes are using the database files.

• Verify that all of the Transport database files exist in the Queue directory. If one or more of the files are not present, follow these steps:

  1. Stop the Microsoft Exchange Transport service.

  2. Remove the transport database. To do this, rename the following folder:

     %ProgramFiles%\Microsoft\Exchange Server\V14\TransportRoles\data\Queue

  3. Start the Microsoft Exchange Transport service to determine whether mail flow is restored.

  4. Try to repair the original Transport database to recover any queued messages.

• Determine whether the transport database is corrupted. To do this, follow these steps:

  1. Stop the Microsoft Exchange Transport service.

  2. Remove the transport database. To do this, rename the following folder:

     %ProgramFiles%\Microsoft\Exchange Server\V14\TransportRoles\data\Queue

  3. Start the Microsoft Exchange Transport service to determine whether mail flow is restored.

  4. Try to repair the original Transport database to recover any queued messages.

• To recover any queued messages from the original Transport database use the Eseutil tool to repair the Mail.que database. For more information, see Working with the Queue Database on Transport Servers. Specifically, move the original Transport database files to a working location, and use the Eseutil tool to perform the following actions against the original Transport database files:

  1. Run the following command to dump the database headers. Then, view the results to determine whether the Mail.que database is in a dirty shutdown state.

     Eseutil /mh mail.que

  2. If the database is in a dirty shutdown state, run the following command to replay any outstanding transaction logs:

     Eseutil /r trn

  3. If MsExchangeTransport Event ID 17011 is logged to indicate that the checkpoint file is damaged, remove the .chk file, and then run the Eseutil /r trn command to replay the transaction log files.

  4. If the Mail.que or transaction log files are damaged or missing, run the following command to perform a checksum test:

     Eseutil /K mail.que

     Then, before you run a hard repair against the database, run the following command to run a read-only version of the hard repair:

     Eseutil /G mail.que

  5. If you have to perform a hard repair of the database, run the following command:

     Eseutil /p mail.que

     Important   The Eseutil /p command is a destructive command. When you run this command, some data loss will occur. We recommend that you only use this command after all other troubleshooting steps have been unsuccessful.

  6. Run the following command to defragment the repaired database:

     Eseutil /d mail.que

  7. Restore the database files to their original location. Use the steps in the Working with the Queue Database on Transport Servers topic to do this. For example, perform the following steps as specified in the linked document:

  • Pause the Microsoft Exchange Transport service.

  • Use the Queue Viewer tool to verify that all Transport queues have emptied, and then export any messages that have not emptied.

  • Stop the Microsoft Exchange Transport service.

  • Replace the new database files with the original files, and then start the Microsoft Exchange Transport service.

• 使用自助支持选项、协助支持选项及其他资源来解决您的问题。您可以从 Exchange Server 解决方案中心访问这些资源。在该页中，单击导航窗格中的“自助支持选项”可使用自助服务选项。自助服务选项包括搜索 Microsoft 知识库、在 Exchange Server 论坛上发布问题及其他方法。或者，您可以在导航窗格中单击“协助支持选项”来联系 Microsoft 支持专业人员。由于您的组织可能已有直接与 Microsoft 产品支持服务联系的特定流程，因此，请您务必先查看您组织的准则。

or more information about the transport pipeline in Exchange 2010, see 了解传输管道 and also the Exchange Server Team blog article,

Exchange 2010 Transport Architecture Diagrams Available for Download.

每个博客的内容及其 URL 如有更改，恕不另行通知。每个博客中的内容均“原样”提供，既不承担任何担保，也未赋予任何权利。对包含的脚本示例或代码的使用受 Microsoft 使用条款中指定的条款的约束。