MSExchangeTransport 17016

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 cannot mount the Transport database on the Hub Transport server or 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 can't 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 Exchange 2010 Transport database files are located in the following directory:

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

The Microsoft Exchange Transport service includes a "self healing" feature that is designed to enable Exchange to recover from most issues that can 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.

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

When a message is received in the Transport pipeline, the page that requires updating is read into memory, and the changes are recorded in the ESE cache. The version store component tracks the uncommitted changes. This operation is then recorded in a transaction log file on the hard disk, and when the log file becomes full, a new log file is created. Finally, the page is committed to the mail.que file and the checkpoint is advanced to record the committed transaction.

If these files become damaged or if the Microsoft Exchange Transport service cannot access them, the Microsoft Exchange Transport service shuts down.

For more information, see 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.
• Try to repair the original Transport database to recover any queued messages. For more information, see Working with the Queue Database on Transport Servers. Specifically, move the original Transport database files to a working location, and use the Eseutil tool to perform the following actions against the original Transport database files:
  1. Run the following command to dump the database headers. Then, view the results to determine whether the Mail.que database is in a dirty shutdown state.
     Eseutil /mh mail.que
  2. If the database is in a dirty shutdown state, run the following command to replay any outstanding transaction logs:
     Eseutil /r trn
  3. If MsExchangeTransport Event ID 17011 is logged to indicate that the checkpoint file is damaged, remove the .chk file, and then run the Eseutil /r trn command to replay the transaction log files.
  4. Run the following command to defragment the database:
     Eseutil /d mail.que
  5. Restore the database files to their original location. Use the steps in the Working with the Queue Database on Transport Servers topic to do this. For example:
  • Pause the Microsoft Exchange Transport service.
  • Use the Queue Viewer tool to verify that all Transport queues have emptied or export any messages that have not emptied.
  • Stop the Microsoft Exchange Transport service.
  • Replace the new database files with the original files, and then start the Microsoft Exchange Transport service.
• 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.