MSExchangeTransport 16027

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 Information event indicates that the Microsoft Exchange Transport service configuration has not received updates from the Active Directory directory service.

Microsoft Exchange Server 2010 uses an ESE database to store queued messages and configuration information, such as IP allow lists, IP block lists, and sender repudiation information. Configuration information for the Microsoft Exchange Transport service is stored in Active Directory on the Configuration/Services/Microsoft Exchange/First Organization/Administrative Groups/Exchange Administrative Group/Servers/<Servername> object.

Note   Some configuration values do not map directly to properties on the server object in Active Directory. For example, many boolean attributes such as PoisonMessageDetectionEnabled, ExternalDelayDsnEnabled are combined into a single msExchTransportFlags property on the server object.

When settings are changed on the Transport server object, Active Directory notifies the Transport server to update the Transport server configuration cache. When the Transport server receives this type of notification, it reloads the configuration from Active Directory into the cache, and then uses the new information for subsequent message transfer operations.

If the Transport server cannot receive configuration information from Active Directory, the particular component that a configuration change affects will not be updated. This event may be logged if there is a configuration problem between the Hub Transport server and Active Directory.

This event may be logged on an Edge Transport server when the following conditions are true:

• The Microsoft Exchange ADAM service on an Edge Transport server has stopped.

• The configuration stored in Active Directory or in ADAM is corrupted.

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.

• If this error occurred on a Hub Transport server, try one or both of the following methods:

  • Verify connectivity between the Hub Transport server and Active Directory domain controllers in the same site. To do this, use the Ping.exe tool to test connectivity by IP address and by FQDN. Use the PathPing command-line tool to help detect packet loss over multiple-hops. For more information, see Microsoft Knowledge Base article 325487, Advanced network adapter troubleshooting for Windows workstations.

  • Run the Dcdiag command line tool to test domain controller health. To do this, run dcdiag /s:<Domain Controller Name> at a command prompt on the Exchange server. Use the output of Dcdiag to discover the cause of any failures or warnings that it reports.

• If the error occurred on an Edge Transport server, verify that the Microsoft Exchange ADAM service is started on the Edge Transport server. Examine the EdgeTransport.exe.config file to determine whether any Transport settings have been changed. For more information, see Understanding the EdgeTransport.exe.Config File.

• 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 architecture in Exchange 2010, see Understanding Transport Pipeline and also 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.