MSExchangeTransport 15004

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

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

Details

Explanation

This Warning event indicates that the Microsoft Exchange Transport service is experiencing a resource usage issue. This back pressure-related event is logged when the monitored resources have experienced increased pressure.

Note   The frequency at which Exchange monitors resource utilization levels is specified by the ResourceMonitoringInterval parameter in the EdgeTransport.exe.config file. By default, this value is two seconds.

The Back Pressure Monitoring Infrastructure is a system resource monitoring feature on Microsoft Exchange Server 2010 and Microsoft Exchange Server 2007 Transport servers. This system monitors resources used by the Microsoft Exchange Transport service during message processing. The back pressure feature monitors the following system resources:

• Available hard disk space on the drive on which the message queue database is stored

• Available hard disk on the drive on which the message queue transaction logs are stored

• The number of uncommitted message queue database transactions that exist in memory (also known as Version Buckets)

• The memory that is used by the EdgeTransport.exe process

• The memory that is used by all processes

The back pressure feature uses the following three stages of resource usage to determine how much to restrict message processing:

• Normal: In this scenario, the resource is not overused. The Transport server accepts new connections and processes messages as expected.

• Medium: In this scenario, the resource is slightly overused. The Transport server applies back pressure in the following manner. The Transport server processes messages from senders in the authoritative domain. However, the server rejects new connections and messages from other sources.

• High: In this scenario, the resource is severely overused. The Transport server applies full back pressure in the following manner. All message processing stops and the server rejects all new connections and messages.

These actions allow Exchange to slow incoming messages and let it catch up with processing queued messages. During these activities, Exchange 2010 continues to use resource monitoring and corrective actions to gracefully recover from resource usage issues. If these actions do not successfully restore resource usage to typical levels, the Microsoft Exchange Transport service escalates the corrective actions until the resource usage issue is corrected.

This event is logged to indicate the escalation of a resource usage issue. This issue may occur when one or more of the following conditions are true:

• A large number of uncommitted database transactions (version buckets) exists. 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 that is 100 MB large could cause this issue.

For more information, see Общие сведения об обратном давлении.

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.

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

• Examine the System event log to determine whether any hard disk drive or subsystem issues exist that might 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.

• You may want to review the back pressure configuration settings on the server. This information is stored in the EdgeTransport.exe.config file. The file is located in the following folder on the Transport server:

  %ProgramFiles%\Microsoft\Exchange Server\V14\Bin

  Note   We recommend that you do not modify the back pressure settings.

  For more information about the back pressure settings, see the "Back Pressure Configuration Options in the EdgeTransport.exe.config File" section in Общие сведения об обратном давлении.

• 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

• 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 Изменение местоположения базы данных очереди.

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

• Для решения проблемы обратитесь в службу технической поддержки, используйте средства для самостоятельного устранения неполадок или другие ресурсы. Эти дополнительные ресурсы доступны в Техническом центре 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-адрес любого блога могут быть изменены без предварительного уведомления. Содержимое каждого блога предоставляется «как есть», без каких-либо гарантий и передачи каких-либо прав. На предлагаемые примеры сценариев и коды распространяются условия использования продуктов корпорации Майкрософт.