MSExchangeTransport 12009

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

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:

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

• 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 Prepare Active Directory and Domains.

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

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

F For more information about the transport pipeline in Exchange 2010, see Understanding Transport Pipeline.

To obtain transport architecture diagrams, see 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.