MSExchangeTransport 2021

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

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

Details

Explanation

This event indicates that a message delivery failure occurred between the Send connector on a Microsoft Exchange Server 2010 Transport server and another SMTP server. In Exchange 2010, the SMTPSend component is the transport component that sends messages from the Delivery Queue to other destinations. This event is triggered when the SmtpSend component cannot transfer routing destination information (RDST) to the destination SMTP server.

You may experience this issue if the following conditions are true:

• The message requires support for the XRDST extended SMTP verb

• The remote server does not support XRDST

Alternatively, this issue may occur if the following conditions are true:

• The sending server is running Exchange 2010 or Microsoft Exchange Server 2007

• The message destination is a public folder on a receiving server that is running Microsoft Exchange Server 2003.

• The XEXCH50 verb is disabled on the Exchange 2003 SMTP server

When Exchange 2010 or Exchange 2007 send messages to a public folder, they store additional message information in the XEXCH50 blob. In a pure Exchange 2010 or Exchange 2007 organization, the XEXCH50 verb can be disabled. In this scenario, Exchange 2010 and Exchange 2007 use the XRDST verb to store the public folder information. Exchange 2003 does not support XRDST.

Therefore, when the Exchange 2003 SMTP server does not advertise XEXCH50, Exchange 2010 tries to send the information by using XRDST. Because Exchange 2003 does not support this verb, the message cannot be sent.

User Action

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

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

• Log on to the remote SMTP server by using the telnet command to port 25. Use the EHLO command to return a list of extended SMTP verbs that the server supports. Determine whether the XRDST and/or XEXCH50 keywords are advertised.

• If the destination server is running Exchange 2003, restore support for XEXCH50. To do this, run the Microsoft Exchange Best Practices Analyzer on the server. The Best Practices Analyzer returns a list of DLL files that must be registered to support XEXCH50.

• If the destination server is running Exchange 2010 or Exchange 2007, run the Get-ReceiveConnector "ConnectorName" | Format-List command to determine whether the connector supports XRDST.

• Use the Set-ReceiveConnector cmdlet to enable XRDST on the remote SMTP Receive connector. For more information, see Set-ReceiveConnector.

• 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

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

For more information about the transport pipeline in Exchange 2010, see the following topics:

• 了解传输管道

• Exchange 2010 Transport Architecture Diagrams Available for Download

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