MSExchangeTransport 17018

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

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

Details

Explanation

This Error event indicates that the Microsoft Exchange Transport service encountered a resource-related error when it tried 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 is made up 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

The Microsoft Exchange Transport service includes a resource monitoring service that is known as the Back Pressure Monitoring Infrastructure. This system monitors resources used by the Microsoft Exchange Transport service during message processing. The back pressure feature monitors the following system resources:

• Available hard disk space on the drive on which the message queue database is stored

• Available hard disk on the drive on which the message queue transaction logs are stored

• The number of uncommitted message queue database transactions that exist in memory (also known as Version Buckets)

• The memory that is used by the EdgeTransport.exe process

• The memory that is used by all processes

The back pressure feature uses the following stages of resource usage to determine how much to restrict message processing:

• Normal: In this scenario, the resource is not overused. The Transport server accepts new connections and processes messages as expected.

• Medium: In this scenario, the resource is slightly overused. The Transport server applies back pressure in the following manner. The Transport server processes messages from senders in the authoritative domain. However, the server rejects new connections and messages from other sources.

• High: In this scenario, the resource is severely overused. The Transport server applies full back pressure in the following manner. All message processing stops and the server rejects all new connections and messages.

These actions let Exchange slow down incoming messages and catch up with processing queued messages. During these activities, Microsoft Exchange Server 2010 continues to use resource monitoring and corrective actions to gracefully recover from resource usage issues. If these actions do not successfully restore resource usage to typical levels, the Microsoft Exchange Transport service escalates the corrective actions until the resource usage issue is corrected. If the issue is not corrected, the Microsoft Exchange Transport service may shut down.

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

• Many uncommitted database transactions (Version Buckets) exist. This may be caused by virus-related issues, corrupted messages, queue database integrity issues, or hard disk drive-related issues such as performance or storage space issues.

• A large message size limit is configured in Exchange. For example, a message size of 300 MB is configured.

• The server has insufficient available RAM or hard disk space to run the ESE database.

For more information, see the following topics:

• 了解反压

• 了解传输队列

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

• Examine the System event log to determine whether any hard disk drive or subsystem issues exist that might cause the storage issue.

• Examine memory-related performance counters or memory-related logged events to determine whether the Microsoft Exchange Transport service experienced an out-of-memory condition.

• If the drive on which the Transport queue database does not have sufficient space, move the queue database to another drive. For more information, see 更改队列数据库的位置.

• Verify that the server has enough RAM installed for the Exchange roles that are running. For more information, see the following topics:

  • 了解内存配置和 Exchange 性能

  • 了解容量规划中的多个服务器角色配置

  • 了解客户端访问和容量规划中的集线器传输组合角色配置

• If Exchange is running on a virtual machine, verify that the memory over-commit functionality or the memory over-subscription functionality is turned off for the particular virtual machine. For more information, see the "Exchange Server Memory Requirements and Recommendations" section under "Hardware Virtualization" in Exchange 2010 System Requirements.

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