MSExchangeTransport 17018

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

Explanation

This Error event indicates that the Microsoft Exchange Transport service encountered a resource-related error when it tried to access the Transport database on the Hub Transport server or on the Edge Transport server.

Starting with Microsoft Exchange Server 2007, the Microsoft Exchange Transport service uses an Extensible Storage Engine (ESE) database for mail queue storage. This design change improves read and write performance with respect to messaging queues and also lets the messaging queues be backed up. The Transport database is made up of the following files:

• Mail.que: The ESE database
• Tmp.edb: The temporary workspace for processing transactions
• Trn.log: The current transaction log file
• Trntmp.log: The temporary transaction log file
• Trn.chk: The database checkpoint file
• Trnres00001.jrs: The first transaction reserve file
• Trnres00002.jrs: The second transaction reserve file

By default, these files are located in the following directory:

%ProgramFiles%\Microsoft\Exchange Server\V14\TransportRoles\data\Queue

The Microsoft Exchange Transport service includes a resource monitoring service that is known as the Back Pressure Monitoring Infrastructure. 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 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 let Exchange slow down incoming messages and catch up with processing queued messages. During these activities, Microsoft Exchange Server 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. If the issue is not corrected, the Microsoft Exchange Transport service may shut down.

This issue may occur when one or more of the following conditions are true:

• Many uncommitted database transactions (Version Buckets) exist. This may be caused by virus-related issues, corrupted messages, queue database integrity issues, or hard disk drive-related issues such as performance or storage space issues.
• A large message size limit is configured in Exchange. For example, a message size of 300 MB is configured.
• The server has insufficient available RAM or hard disk space to run the ESE database.

For more information, see the following topics:

• Grundlegendes zur Rückstaufunktion
• Grundlegendes zu Transportwarteschlangen

User Action

To troubleshoot this issue, 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.
• If a file-level antivirus scanner is running, verify that antivirus exclusions are configured appropriately. For more information, see Antivirenscans auf Dateiebene für Exchange 2010.
• 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
• Determine whether the transport database is corrupted. To do this, follow these steps:
  1. Stop the Microsoft Exchange Transport service.
  2. Remove the transport database. To do this, rename the following folder:
     %ProgramFiles%\Microsoft\Exchange Server\V14\TransportRoles\data\Queue
  3. Start the Microsoft Exchange Transport service to determine whether mail flow is restored.
• Examine the System event log to determine whether any hard disk drive or subsystem issues exist that might 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.
• If the drive on which the Transport queue database does not have sufficient space, move the queue database to another drive. For more information, see Ändern des Speicherorts der Warteschlangendatenbank.
• Verify that the server has enough RAM installed for the Exchange roles that are running. For more information, see the following topics:
  • Grundlegendes zu Speicherkonfigurationen und Exchange-Leistung
  • Grundlegendes zur Konfiguration mehrerer Serverrollen bei der Kapazitätsplanung
  • Grundlegendes zur kombinierten Konfiguration der Clientzugriffs- und Hub-Transport-Serverrollen bei der Kapazitätsplanung
• If Exchange is running on a virtual machine, verify that the memory over-commit functionality or the memory over-subscription functionality is turned off for the particular virtual machine. For more information, see the "Exchange Server Memory Requirements and Recommendations" section under "Hardware Virtualization" in Exchange 2010 System Requirements.
• 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.