MSExchangeTransport 17013

 

This article provides an explanation and possible resolutions for a specific Exchange event. If you don't find what you’re looking for here, try searching Exchange 2010 Help.

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:

  • Review the Application log and System log on your Exchange 2010 servers for related events. For example, events that occur immediately before and after this event may provide more information about the root cause of this error.

  • 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 File-Level Antivirus Scanning on 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.

  • Resolve your issue by using self-support options, assisted support options, and other resources. You can access these resources from the Exchange Server Solutions Center. From this page, click Self-Support Options in the navigation pane to use self-help options. Self-help options include searching the Microsoft Knowledge Base, posting a question at the Exchange Server forums, and other methods. Alternatively, in the navigation pane, you can click Assisted Support Options to contact a Microsoft support professional. Because your organization may have a specific procedure for directly contacting Microsoft Product Support Services, be sure to review your organization's guidelines first.

For more information about the transport pipeline in Exchange 2010, see Understanding Transport Pipeline and also the Exchange Server Team blog article,

Exchange 2010 Transport Architecture Diagrams Available for Download.

The content of each blog and its URL are subject to change without notice. The content within each blog is provided "AS IS" with no warranties, and confers no rights. Use of included script samples or code is subject to the terms specified in the Microsoft Terms of Use.