MSExchangeTransport 15005

 

Letztes Änderungsdatum des Themas: 2011-03-19

Dieser Artikel bietet eine Erläuterung und mögliche Lösungen für ein bestimmtes Exchange-Ereignis. Wenn Sie hier das Gesuchte nicht finden können, durchsuchen Sie die Exchange 2010-Hilfe.

Details

Product Name

Exchange

Product Version

14.0

Event ID

15005

Event Source

MSExchangeTransport

Category

ResourceManager

Symbolic Name

ResourceUtilizationDown

Message Text

The resource pressure decreased from %1 to %2.%3

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 Grundlegendes zur Rückstaufunktion.

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:

  • Ü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.
  • 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 Grundlegendes zur Rückstaufunktion.
  • 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.
    • Smtpreceive
    • Smtpsend
    • DSN
    • Components
    • Remote Delivery
    • Categorizer
  • Lösen Sie Ihr Problem über die Optionen zur Selbsthilfe, die Optionen für technischen Support und andere Ressourcen. Sie können auf diese Ressourcen über das Exchange Server Solutions Center (möglicherweise in englischer Sprache) zugreifen. Klicken Sie auf dieser Seite im Navigationsbereich auf Optionen zur Selbsthilfe, um die Optionen zur Selbsthilfe zu verwenden. Zu den Optionen zur Selbsthilfe gehört das Durchsuchen der Microsoft Knowledge Base, das Stellen einer Frage in den Exchange Server-Foren und andere Methoden. Alternativ können Sie im Navigationsbereich auf Optionen für technischen Support klicken, um Kontakt mit einem Microsoft-Supportspezialisten aufzunehmen. Da es in Ihrer Organisation ein bestimmtes Verfahren für den direkten Kontakt mit dem Microsoft-Produktsupport geben kann, sollten Sie zuerst die Richtlinien Ihrer Organisation prüfen.

For more information about the transport pipeline in Exchange 2010, see Grundlegendes zur Transportpipeline and also the Exchange Server Team blog article,

Exchange 2010 Transport Architecture Diagrams Available for Download.

Der Inhalt jedes Blogs und die dazugehörige URL kann ohne vorherige Ankündigung geändert werden. Der Inhalt jedes Blogs wird "WIE BESEHEN" ohne Gewährleistungen bereitgestellt und überträgt keine Rechte. Die Verwendung der enthaltenen Skriptbeispiele unterliegt den in den Nutzungsbestimmungen angegebenen Bedingungen.