MSExchangeTransport 17010

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

Thank you for clicking the link that brought you to this page. We do not currently have an article to resolve this specific issue. Your attempt to get to this event article helps us prioritize the event articles for which we will be providing detailed explanations and user actions.

Although there is as yet no supplementary content specifically written to help resolve this Exchange 2010 event, here are some recommended next steps to learn more about this alert:

• Review the Application log and System log on your Exchange 2010 servers for related events. For example, events that occur immediately before and after this event may provide more information about the root cause of this error.

• Research your issue by using self-support options. From the navigation pane of the Exchange Server Solutions Center page, click Self Support Options to use the following and other self-help options:

  • Search the Microsoft Knowledge Base. For example, search the Knowledge Base for the Event Source and event ID you are getting, as well as any other key words in the text of the event message.

  • Search the Exchange 2010 Forum. You can also post a question there.

  • Search the Exchange Server Community Web site.

• Research your issue by using other resources. From the navigation pane at the Exchange Server Solutions Center page, click Key Resources to learn about other resources.

• Resolve your issue by using assisted support options. From the Exchange Server Solutions Center page, click Assisted Support Options to contact a Microsoft support professional. Because your organization may have a specific procedure for directly contacting Microsoft Technical Support, be sure to reviewing your organization's guidelines first. If you do contact support, have the event ID information available. Also, if possible, be prepared to send your application and system logs to the support professional.

Details

Explanation

This Information event indicates that the Microsoft Exchange Transport service has finished parsing the transport database, mail.que.

Microsoft Exchange Server 2010 uses an ESE database to store messages for routing throughout an Exchange organization. On servers that run the Edge Transport role, the database queues those messages that are received from or are directed to the Internet. On servers that run the Hub Transport role, the database queues messages that are transferred throughout the Exchange organization. Exchange 2010 includes the following transport queues:

• Submission queue

• Mailbox delivery queue

• Remote delivery queue

• Poison message queue

• Unreachable queue

The Microsoft Exchange Transport service creates these queues for temporary message storage as the service transfers messages through the transport pipeline. Queue settings are stored in the EdgeTransport.exe.config file. This file is an XML application configuration file that is associated with the EdgeTransport.exe file. For more information, see the "Options for Configuring the Queue Database" section in 了解传输队列.

If the transport queue contains a lot of messages, or if the queue continues to grow, this could indicate a problem in the transport pipeline.

For more information about the transport architecture in Exchange 2010, see Transport Architecture.

For more information about the transport pipeline in Exchange 2010, see 了解传输管道 and also see the Exchange Server Team Blog article Exchange 2010 Transport Architecture Diagrams Available for Download.

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

User Action

No user action is required. However, we recommend that you monitor this event to determine whether the number of messages in the queue grows. 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.

• 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, click Expert for each component, then click Configure:

  • Smtpreceive

  • Smtpsend

  • DSN

  • Components

  • Remote Delivery

  • Categorizer

Use the Queue Viewer tool in the Exchange 2010 Toolbox to view the message queues.

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

For More Information

如果您尚未执行此操作，请考虑运行 Exchange 工具，已创建这些工具以帮助您分析 Exchange 环境并对其进行疑难解答。这些工具可帮助确保您的配置与 Microsoft 最佳实践保持一致。它们还可以帮助您识别和解决性能问题，并改进邮件流。若要运行这些工具，请转到 Exchange 管理控制台的“工具箱”节点。若要了解有关这些工具的详细信息，请参阅管理工具箱中的工具。