Поделиться через

MSExchangeTransport 17019

  • Статья

 

Последнее изменение раздела: 2011-03-19

В этой статье приводится объяснение и возможные варианты устранения неполадок, связанных с определенными событиями Exchange. Если вам не удалось найти ответ на свой вопрос, используйте поиск по Справке Exchange 2010.

Details

Product Name

Exchange

Product Version

14.0

Event ID

17019

Event Source

MSExchangeTransport

Category

Storage

Symbolic Name

JetIOError

Message Text

%1: A database operation has encountered an I/O error. The Microsoft Exchange Transport service is shutting down. Exception details: %2

Explanation

This Error event indicates that the Microsoft Exchange Transport service was unable 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 allows for the messaging queues to 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

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

  • Another program, such as a file-level antivirus program or backup program. has locked the file or files.

  • A storage issue exists on the drive that hosts the Transport database files.

  • The Microsoft Exchange Transport server is trying to process many very large messages.

  • The Transport database is damaged.

User Action

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

  • Проверьте наличие соответствующих событий в журналах приложений и системных журналах серверов Exchange 2010. Например, события, которые происходят непосредственно до и после этого события, могут предоставить дополнительные сведения об основной причине ошибки.

  • 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 Поиск вирусов на файловом уровне в Exchange 2010.

  • Determine whether any non-Exchange programs are accessing the Transport database 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, but replace database.edb by 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>"

    4. Determine whether any non-Exchange processes are using the database files.

  • 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 System event log to determine whether any hard disk drive or subsystem issues exist that may 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 Изменение местоположения базы данных очереди.

  • 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 Общие сведения об ограничениях размера сообщения.

  • 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 any Outlook clients that are earlier than Microsoft Outlook 2003 are accessing the system. Outlook clients that are earlier than Outlook 2003 do not recognize message size restrictions that are configured in Exchange. Therefore, these clients may send messages that exceed the specified maximum message size.

  • 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.

  • If the issue is resolved, 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, follow these steps:

    • 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.

  • Для решения проблемы обратитесь в службу технической поддержки, используйте средства для самостоятельного устранения неполадок или другие ресурсы. Эти дополнительные ресурсы доступны в Техническом центре Exchange Server. В области навигации на этой странице щелкните Самостоятельная поддержка и выберите один из предлагаемых вариантов. Для самостоятельного устранения неполадок можно выполнить поиск по базе знаний Майкрософт, опубликовать свой вопрос на форуме Exchange Server и воспользоваться другими способами. Можно также обратиться к специалисту службы технической поддержки Майкрософт, щелкнув в области навигации Варианты технической поддержки. Поскольку для прямого обращения в службу технической поддержки Майкрософт в вашей организации может использоваться определенная процедура, необходимо сначала ознакомиться с инструкциями организации.

For more information about the transport pipeline in Exchange 2010, see Общие сведения о конвейере транспорта and also the Exchange Server Team blog article,

Exchange 2010 Transport Architecture Diagrams Available for Download.

Содержимое и URL-адрес любого блога могут быть изменены без предварительного уведомления. Содержимое каждого блога предоставляется «как есть», без каких-либо гарантий и передачи каких-либо прав. На предлагаемые примеры сценариев и коды распространяются условия использования продуктов корпорации Майкрософт.