MSExchangeTransport 17013

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

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

Details

Explanation

This Error event indicates that the Microsoft Exchange Transport service is unable to access the Transport database file. If the Microsoft Exchange Transport service is unable to open the Transport database or transaction log files, the service stops.

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 allows for the messaging queues to be backed up.

By default, the Exchange 2010 Transport database (Mail.que) is located in the following directory:

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

If the Transport server cannot access the database or transaction log files, the Transport server cannot process messages and may shut down.

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

• A file-level antivirus program does not have exclusions configured for the Exchange-related files and directories.

• Another program such as a backup program has locked the database-related files.

• The Transport database has become 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 上的文件级防病毒扫描.

• You may want to increase diagnostics logging to log the components in the transport pipeline. To increase diagnostics logging for the Transport components, follow these steps:

  1. In the Exchange Server 2010 Management Console, expand Server Configuration, and then click Hub Transport.

     Note   For an Edge Transport server, click Edge Transport.

  2. In the Actions pane, click Manage Diagnostic Logging Properties for the appropriate server.

  3. Expand MSExchangeTransport.

  4. Click the following components, and then click Expert, then click Configure for each component:

  • Smtpreceive

  • Smtpsend

  • DSN

  • Components

  • Remote Delivery

  • Categorizer

• Determine whether any non-Exchange programs are accessing the 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, replacing database.edb with 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>.edb"

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

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

• 使用自助支持选项、协助支持选项及其他资源来解决您的问题。您可以从 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 使用条款中指定的条款的约束。