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

MSExchangeTransport 12009

  • Статья

 

Последнее изменение раздела: 2012-09-19

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

Details

Product Name

Exchange

Product Version

14.0

Event ID

12009

Event Source

MSExchangeTransport

Category

TransportService

Symbolic Name

ReadConfigReceiveConnectorUnavail

Message Text

Microsoft Exchange couldn't read the Receive connector configuration because the directory is unavailable. The service will be stopped.

Explanation

This Error event indicates the Microsoft Exchange Transport service can't load the routing tables because the Служба каталогов Active Directory directory service is unavailable.

User Action

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

  • Проверьте наличие соответствующих событий в журналах приложений и системных журналах серверов 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

  • Verify the group membership for the Exchange Trusted Subsystem object. To do this, follow these steps:

    1. Start the Служба каталогов Active Directory Users and Computers MMC snap-in.

    2. Under the domain name (for example, contoso.com), click the Microsoft Exchange Security Groups container.

    3. In the details pane, right-click the Exchange Windows Permissions group, and then click Properties.

    4. Click the Members tab, and then add the Exchange Trusted Subsystem object if this object is not already present.

    5. Click OK two times.

    6. On the Exchange server, click Start, click Run, type lusrmgr.msc, and then click OK.

    7. In the Local Users and Groups snap-in, click Groups.

    8. In the details pane, right-click Administrators, and then click Properties.

    9. If EXAMPLE\Exchange Trusted Subsystem is not listed in the Members list, add the Exchange Trusted Subsystem object.

    10. Click OK two times, and restart the Exchange server.

    11. Re-run the Exchange Setup program to run the PrepareDomain component. For more information, see Подготовка Active Directory и доменов.

  • Examine the Windows Firewall settings to verify that exemptions are listed for all the Exchange services. To do this, follow these steps:

    1. Start the Windows Firewall Control Panel item.

    2. Click Allow a program through Windows Firewall.

    3. Click the Exchange tab, and then verify that the following exception check boxes are selected:

      • Microsoft Exchange Server

      • MSExchangeIS

      • MSExchangeSA

    4. Click OK, and then restart the Служба каталогов Active Directory topology service.

  • Verify network connectivity with the domain controller. Specifically, verify that you can use the Ping.exe command to reach the global catalog servers that are in the same site as the Exchange server. Use the Ping.exe command to verify connectivity by using the IP addresses and FQDNs of the global catalog servers.

  • If the Exchange Setup/PrepareDomain step generated any errors, re-run the command to prepare the domain for Exchange.

  • Verify that the Exchange server is a member of the Exchange Servers group in Служба каталогов Active Directory.

  • Verify that the Exchange Servers group is listed in the Manage auditing and security log policy setting. If the group is not listed in this policy, add it. To view this policy, follow these steps:

    1. Start the Group Policy Management tool. To do this, click Start, point to Administrative Tools, and then click Group Policy Management.

    2. Expand the forest object, expand the domain object, expand the Domain Controllers object, right-click the Default Domain Controllers Policy object, and then click Edit.

    3. Expand Computer Configuration, expand Policies, expand Windows Settings, expand Security Settings, expand Local Policies, and then click User Rights Assignment.

    4. In the list of policies, double-click the Manage auditing and security log policy.

    5. If EXAMPLE\Exchange Servers is not listed, add the Exchange Servers group.

    6. Click OK, exit the Group Policy Management Editor, and then run gpupdate /force on the Exchange server.

  • Verify that the Exchange server can register the Service Principal Name (SPN) for the Microsoft Exchange Transport service. To do this, follow these steps:

    1. Start Registry Editor (regedit.exe), and then locate the following registry subkey:

      HKLM\SYSTEM\ControlSet001\Services\Tcpip\Parameters

    2. Right-click the Parameters subkey, and then click Permissions.

    3. Click Add, and then add the computer account for the Exchange server. The correct account is Example\ServerName$.

    4. Click Example\ServerName$, and then click to select the Read check box in the Allow column.

      Note   The Exchange server must be able to read the Parameters subkey. This lets the server locate the FQDN of the server to register the SPN.

    5. Click OK, exit Registry Editor, and then restart the server.

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

F For more information about the transport pipeline in Exchange 2010, see Общие сведения о конвейере транспорта.

To obtain transport architecture diagrams, see the Exchange Server Team blog article, Exchange 2010 Transport Architecture Diagrams Available for Download.

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