MSExchangeTransport 17023

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

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

Details

Explanation

This Error event indicates that the Microsoft Exchange Transport service could not mount 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 message queue database and the Content Filtering database use circular logging. Therefore, you can't use the transaction logs for data recovery. Additionally, the transaction logs are re-created automatically during the startup of the Microsoft Exchange Transport service if they are missing. By default, the Microsoft Exchange Server 2010 Transport database files are located in the following directory:

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

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

When a message is received in the Transport pipeline, the page that requires updating is read into memory and the changes are recorded in the ESE cache. The version store component tracks the uncommitted changes. This operation is then recorded in a transaction log file on the hard disk. When the log file becomes full, a new log file is created. Finally, the page is committed to the mail.que file and the checkpoint is advanced to record the committed transaction.

For more information, see 了解传输队列.

User Action

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

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

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

• Start Windows Explorer, and then examine the files in the Queue directory to determine whether the Read-Only attribute is set.

• 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.

• Try to recover any queued messages from the original Transport. For more information, see Working with the Queue Database on Transport Servers.

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

For 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 使用条款中指定的条款的约束。