MSExchangeTransport 17014

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 could not start because it is unable to locate a valid copy of the Extensible Storage Engine (ESE) 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 allows for the messaging queues to be backed up. The message queue database and the Content Filtering database use circular logging. Therefore, you cannot use the transaction logs for data recovery. Additionally, the transaction logs are re-created automatically during the startup of the Microsoft Exchange Transport service if they are missing. By default, the Microsoft Exchange Server 2010 Transport database files are located in the following directory:

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

• Because a single ESE database is used to store messaging queues, the Microsoft Exchange Transport service includes a "self healing" feature. The self healing feature is designed to let Exchange recover from most of the issues that could cause the Transport database to fail.

These include the following issues:

• Logical database corruption: When the Microsoft Exchange Transport service detects a "JET permanent exception" error that specifies database corruption, the service performs recovery actions. These actions either delete or move the database queue file, log files, or system directories. After the recovery actions are completed, the service creates a new database instance to continue message processing.
• File(s) not available: When the Microsoft Exchange Transport service detects a "JET permanent exception" error that specifies missing or locked database files, the service performs recovery actions. These actions either delete or move the database queue file, log files, or system directories. After the recovery actions are completed, the service creates a new database instance to continue message processing.
• Insufficient disk space: When the Microsoft Exchange Transport service detects a "JET permanent exception" error that specifies insufficient disk space, the service does not perform any recovery actions. For example, the error might specify that the database cannot be extended or that a log file cannot be created. In this scenario, the service shuts down.
• Database upgrade: When the Microsoft Exchange Transport service experiences a database version error, the service performs recovery actions. These actions either delete or move the database queue file, log files, or system directories. After the recovery actions are completed, the service creates a new database instance to continue message processing.
• Failed server disk replaced: When the Microsoft Exchange Transport service first starts after a failed hard disk has been replaced, the service detects a "JET permanent exception" error that specifies physical database corruption. In this scenario, the service performs recovery actions. These actions either delete or move the database queue file, log files, or system directories. After the recovery actions are completed, the service creates a new database instance to continue message processing.

This event is generally logged together with other MSExchangeTransport events that may indicate the reason for the Transport database failure. 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.
• Versions of Microsoft Outlook that are earlier than Microsoft Outlook 2003 are used. Earlier Outlook clients do not recognize message size limits in Exchange 2010. Therefore, it is more likely that an earlier client could send e-mail messages that exceed the maximum specified message limit.

For more information, see Grundlegendes zur Rückstaufunktion.

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
• Examine the global message size limits in Exchange. To do this, follow these steps:
  1. Start the Exchange Management Console, expand Organization Configuration, and then click Hub Transport.
  2. In the details pane, click the Global Settings tab, click Transport Settings, and then click Properties.
  3. On the General tab, review the transport limits. By default, the maximum message size is 10 MB.
     For more information, see Grundlegendes zu Größenbeschränkungen für Nachrichten.
• To view individual message limits, follow these steps:
  1. In the Exchange Management Console, expand Recipient Configuration, and then click Mailbox.
  2. In the details pane, click a mailbox, and then click Properties.
  3. Click the Mail Flow Settings tab, click Message Size Restrictions, and then click Properties.
• Use the Queue Viewer tool in the Exchange 2010 Toolbox to determine whether any stuck messages exist. Determine whether the messages exceed the maximum message size configured for the organization.
• 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.
• 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.