Partager via


MSExchangeTransport 17013

 

Dernière rubrique modifiée : 2011-03-19

Cet article fournit une explication et d’éventuelles solutions en ce qui concerne un événement Exchange spécifique. Si vous ne trouvez pas ce que vous cherchez ici, essayez Aide d’Exchange 2010.

Details

Product Name

Exchange

Product Version

14.0

Event ID

17013

Event Source

MSExchangeTransport

Category

Storage

Symbolic Name

JetInstanceNameInUse

Message Text

%1: The database could not be opened because there is another process using it. The Microsoft Exchange Transport service is shutting down. The exception is %2.

Explanation

This Error event indicates that the Microsoft Exchange Transport service is unable to access the Transport database file. If the Microsoft Exchange Transport service is unable to open the Transport database or transaction log files, the service stops.

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.

By default, the Exchange 2010 Transport database (Mail.que) is located in the following directory:

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

If the Transport server cannot access the database or transaction log files, the Transport server cannot process messages and may shut down.

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

  • A file-level antivirus program does not have exclusions configured for the Exchange-related files and directories.
  • Another program such as a backup program has locked the database-related files.
  • The Transport database has become damaged.

User Action

To troubleshoot this issue, do one or more of the following:

  • Consultez les journaux système et des applications sur vos serveurs Exchange 2010 pour identifier des événements connexes. Par exemple, des événements qui se produisent juste avant ou après cet événement peuvent fournir des informations supplémentaires sur la cause première de cette erreur.
  • 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 Analyse antivirus au niveau fichier sur 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 any non-Exchange programs are accessing the files. To do this, follow these steps:
    1. Visit the following Web site to obtain the Handle. exe program:
      https://technet.microsoft.com/en-us/sysinternals/bb896655.aspx
    2. Extract Handle.exe from the downloaded archive, and then copy the file to a location on the affected Transport server.
    3. Run the following command, replacing database.edb with the name of the database file that is listed in the event:
      handle.exe "c:\program files\microsoft\exchange server\v14\transportroles\data\<foldername>\<databasename>.edb"
    4. Determine whether any non-Exchange processes are using the database file.
  • 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.
  • Résolvez votre problème en utilisant les options de support autonome et les autres ressources. Vous pouvez accéder à ces ressources à partir du Exchange Server Solutions Center. Depuis cette page, cliquez sur Options de support autonome dans le volet de navigation pour utiliser les options de support autonome. Les options de support autonome incluent la recherche dans la Base de connaissances Microsoft, l’envoi d’une question aux forums Exchange Server, et d’autres méthodes. Dans le volet de navigation, vous pouvez également cliquer sur Options de support assisté pour contacter un professionnel du Support Technique Microsoft. Étant donné que votre organisation peut avoir une procédure spécifique pour contacter directement les Services de Support Technique Microsoft, assurez-vous de connaître d'abord les instructions propres à votre organisation.

For more information about the transport pipeline in Exchange 2010, see Présentation du pipeline de transport and also the Exchange Server Team blog article,

Exchange 2010 Transport Architecture Diagrams Available for Download.

Le contenu de chaque blog et les URL correspondantes peuvent faire l’objet de modifications sans préavis. Le contenu de chaque blog est fourni en l’état sans aucune garantie, et ne confère aucun droit. L’utilisation des exemples de script inclus est soumise aux conditions spécifiées dans les Conditions d’utilisation de Microsoft.