MSExchangeTransport 16026

  • Article

 

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

Product Name

Exchange

Product Version

14.0

Event ID

16026

Event Source

MSExchangeTransport

Category

Configuration

Symbolic Name

NetworkAdapterIPQueryFailed

Message Text

Microsoft Exchange failed to query a network adapter to obtain the IP addresses assigned to it. Microsoft Exchange will continue to use previously loaded IP address information if available. The Microsoft Exchange Transport service will be stopped if this error occurred during service startup. Exception details: %1

Explanation

This Information event indicates that the Microsoft Exchange Transport service configuration object is unable to communicate with a network adapter on the server. This problem prevents the Hub Transport server or Edge Transport server from communicating with the Active Directory directory service.

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.

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 configuration object cannot receive configuration information from Active Directory, the configuration cannot be updated. Additionally, network problems may prevent mail flow and other server communications.

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.

  • Update network adapter drivers on the server. Alternatively, if the server is running in a virtual environment, install the latest virtualization extensions, such as Hyper V Integration Services or VMWare Tools.

  • Use network troubleshooting tools to verify network connectivity on the server. For example, use the Ping tool to test network connectivity to the server's IP address, to localhost, and to the server's FQDN and host name. For more information, see Microsoft Knowledge Base article 325487, Advanced network adapter troubleshooting for Windows workstations.

  • Verify that the server has an IP address assigned. To do this, run the IPconfig /all command.

  • Restart the server.

  • Verify the IP address information that is assigned to the network adapter. To do this, start the Exchange Management Shell, and then run the following command:

    Get-NetworkConnectionInfo

    In the results, verify that IP Address and AdapterGuid information is returned for each installed network adapter. For example, results that resemble the following may be returned.

    Name : Realtek RTL8139C+ Fast Ethernet NIC #2

    DnsServers : {192.168.20.200}

    IPAddresses : {192.168.20.4, fe80::c5dd:a10c:f7e1:5f5b}

    AdapterGuid : 6ae413f6-f982-4914-9581-a7ed3674755f

    MacAddress : 52:54:00:60:AF:04

    For more information, see Get-NetworkConnectionInfo.

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