MSExchangeTransport 12025

Letztes Änderungsdatum des Themas: 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 Warning event indicates that the Microsoft Exchange Transport service is resetting transport-related performance counters.

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 those 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 automatically creates these queues on an as-needed basis for temporary message storage.

When the Microsoft Exchange Transport service stops, Reliability and Performance Monitor may still track transport-related processes. Therefore, when the service starts, it disconnects the performance counters from old transport-related processes to start monitoring the newly-started processes. For more information about the transport architecture in Exchange 2010, see Transport Architecture.

User Action

No user action is required. However, you may want to investigate the issue further to determine whether restarting the Microsoft Exchange Transport service was intentional. To do this, do one or more of the following:

• Überprüfen Sie das Anwendungsprotokoll und das Systemprotokoll auf den Exchange 2010-Servern auf verwandte Ereignisse. Ereignisse, die unmittelbar vor oder nach diesem Ereignis auftreten, können z. B. weitere Informationen zur eigentlichen Ursache dieses Fehlers zur Verfügung stellen.
• 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 component startup sequence during the startup process of the Microsoft Exchange Transport service. To increase diagnostics logging for the Transport component, follow these steps:
  1. In Registry Editor, locate the following registry subkey:
     HKEY_LOCAL_MACHINE\SYSTEM\Current Control set\Services\MSExchangeTransport\diagnostics
  2. Set the following REG_DWORD values to 7:
  • Smtpreceive
  • Smtpsend
  • DSN
  • Components
  • Remote Delivery
  • Categorizer
• Examine the Application log to determine whether any other logged events indicate that message processing has experienced a problem.

For More Information

Wenn dies nicht bereits der Fall ist, sollten Sie die Exchange-Tools ausführen, die für die Analyse und Problembehandlung der Exchange-Umgebung erstellt wurden. Mit diesen Tools kann sichergestellt werden, dass Ihre Konfiguration die bewährten Methoden von Microsoft einhält. Sie tragen zudem zur Identifikation und zur Lösung von Leistungsproblemen bei, und können die Nachrichtenübermittlung verbessern. Sie können diese Tools über den Knoten Toolbox in der Exchange-Verwaltungskonsole ausführen. Weitere Informationen zu diesen Tools finden Sie unter Verwalten von Tools in der Toolbox.