none
MSExchangeTransport failed to reach status Running on this server RRS feed

  • Question

  • Exchange 2007 on Server 2008 SP2 64 bit. Trying to install exchange 2007 sp1 with the role of hub transport, and the error keeps stopping the installation. I've tried installing IPv6 with a mathcing static to the IPv4 address and tried with the IPv6 uninstalled from registery. Still no luck after elapsed time of 12:09 Status: Starting the Microsoft Edge Transport service. Checked the services and Microsoft Exchange Transport is in "Starting". 5 logs below right after the failure.

    1. Exchange Server component Hub Transport Role failed.

    Error: Error:

    Service 'MSExchangeTransport' failed to reach status 'Running' on this server.

    2. Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=2068). Exchange Active Directory Provider failed to obtain an IP address for DS server abandonedserver.contoso.com, error 11001 (WSAHOST_NOT_FOUND (Host was not found)). This host will not be used as a DS server by Exchange Active Directory Provider

    3. Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=2068). Exchange Active Directory Provider has discovered the following servers with the following characteristics:

    (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)

    In-site:

    exchange03.contoso.com CDG 1 7 7 1 0 0 1 7 1

    fileserver1.contoso.com CDG 1 7 7 1 0 0 1 7 1

    fileserver2.contoso.com CDG 1 7 7 1 0 0 1 7 1

    abandonedserver.contoso.com CD- 1 0 0 0 0 0 0 0 0

    Out-of-site:

    4. Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=2068). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.

    5. Microsoft Exchange couldn't read the configuration from the Active Directory directory service because of error: Failed to load config due to exception: Microsoft.Exchange.Data.Directory.NoSuitableServerFoundException: The Exchange Topology service on server localhost did not return a suitable domain controller.

    at Microsoft.Exchange.Data.Directory.DSAccessTopologyProvider.GetConfigDCInfo(Boolean throwOnFailure)

    at Microsoft.Exchange.Data.Directory.TopologyProvider.PopulateConfigNamingContexts()

    at Microsoft.Exchange.Data.Directory.TopologyProvider.GetConfigurationNamingContext()

    at Microsoft.Exchange.Data.Directory.ADSession.GetConnection(String preferredServer, Boolean isWriteOperation, Boolean isNotifyOperation, ADObjectId& rootId)

    at Microsoft.Exchange.Data.Directory.ADSession.GetReadConnection(String preferredServer, ADObjectId& rootId)

    at Microsoft.Exchange.Data.Directory.ADSession.Find(ADObjectId rootId, String optionalBaseDN, ADObjectId readId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCreator, CreateObjectsDelegate arrayCreator)

    at Microsoft.Exchange.Data.Directory.ADSession.Find(ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCtor, CreateObjectsDelegate arrayCtor)

    at Microsoft.Exchange.Data.Directory.ADSession.Find[TResult](ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties)

    at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.Find[TResult](ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults)

    at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.FindServerByFqdn(String serverFqdn)

    at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.FindLocalServer()

    at Microsoft.Exchange.Transport.LocalServerConfiguration.<>c__DisplayClass2.<TryLoadLocalServer>b__0()

    at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount)

    at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount).

    Friday, September 2, 2011 4:25 PM

Answers

All replies

  • Google "0x80040a02" and you'll get several hits, including this one:

    http://blogs.msdn.com/b/keithmg/archive/2009/01/06/exchange-topology-discovery-failed-error-0x80040a02-dsc-e-no-suitable-cdc.aspx

     


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    • Marked as answer by Blinks Sunday, September 4, 2011 12:52 PM
    Friday, September 2, 2011 10:43 PM
    Moderator
  • Thanks Ed,

    After adding the Exchange Server Computer account to the Domain Admin group in AD worked.

    Sunday, September 4, 2011 12:54 PM
  • On Sun, 4 Sep 2011 12:54:09 +0000, Blinks wrote:
     
    >After adding the Exchange Server Computer account to the Domain Admin group in AD worked.
     
    Would adding the sever to the "Exchange Servers" security group have
    worked as well? How about rerunning the "setup /preparead" to see it
    might undo some changes that were made to your AD permissons or
    security group membership? While you're at it, a "setup
    /preparedomain" wouldn't hurt either.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Sunday, September 4, 2011 2:56 PM