MSExchangeTransport 15005

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

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

Details

Explanation

This Information event indicates that the Microsoft Exchange Transport service is recovering from a resource usage issue. This back pressure-related event is logged when the monitored resources have experienced decreased pressure.

Note   The frequency at which Exchange monitors resource utilization levels is specified by the ResourceMonitoringInterval parameter in the EdgeTransport.exe.config file. By default, this value is two seconds.

The Back Pressure Monitoring Infrastructure is a system resource monitoring feature on Microsoft Exchange Server 2010 and Microsoft Exchange Server 2007 Transport servers. 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 three 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 allow Exchange to slow incoming messages and let it catch up with processing queued messages. During these activities, Exchange 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.

This event is logged to indicate the full or partial recovery from the resource usage issue.

For more information, see 了解反压.

User Action

No user action is required. However, you may want to obtain more information about the cause of the resource usage issue that occurred. To do this, 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.

• Review the Application log to help locate the issue that caused the resource usage issue.

• Examine the System event log to determine whether any hard disk drive or subsystem issues exist which may 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.

• You may want to review the back pressure configuration settings in the EdgeTransport.exe.config file. The file is located in the following folder on the Transport server:

  %ProgramFiles%\Microsoft\Exchange Server\V14\Bin

  Note   We recommend that you do not modify the back pressure settings.

  For more information about the back pressure settings, see the "Back Pressure Configuration Options in the EdgeTransport.exe.config File" section in 了解反压.

• 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 Management Console, expand Server Configuration, and then click Hub Transport.

Note For and 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** for each component, then click **Configure**.

<!-- end list -->

  - **Smtpreceive**

  - **Smtpsend**

  - **DSN**

  - **Components**

  - **Remote Delivery**

  - **Categorizer**

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