This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Dear Support MS.
I have a system Exchange 2013 SP1 CU23. I have just update windows server.
My server Exchange ERROR - Micorsoft Exchange Active directory topology can not start Event id 4027
So all servcies Exchange ca not start so my services downtime.
Help me guide to resolve
Thanks so much
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 68%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECJ%3C/text%3E%3C/svg%3E)
I ran across this thread just recently while having a similar issue of the "Microsoft Exchange Active Directory Topology" service failing to start and wanted to put in our experience. Due to this thread, I remembered a slight change we made to our AD Sites and defined subnets. In this case, we neglected to add the subnet the exchange server was in and associate this to the default site with assigned appropriate Domain Controllers. Once that subnet was created and associated to the correct site/DCs, the service started.
It seems the Exchange AD Topology service - tries talking to Active Directory but fails, or cannot locate any available domain controller. Like the message indicates, make sure there are no firewalls blocking communication between Exchange and domain controllers, and that your AD site configuration, domain controller positioning and the site Exchange host belongs to match up. Simple test to see if it works is restart Exchange AD Topology service and look for event 2080 in the application log, logged by MSExchange ADAccess, mentioning what DCs' it could locate, or use nltest /dsgetdc:<your DNS domain> to use commandline tools.
Hi @Anonymous
I can ping and nslookup my domain controller
I run commend nltest /dsgetdc:mydomaincontroller is good
My firewall is disabled
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 26%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETH%3C/text%3E%3C/svg%3E)
When installing Exchange 2019, we found the AD Topology Service had stopped running when setup.exe was attempting to complete step "Mailbox role: Transport Service". It stalled at 97%, due to being unable to communicate with the AD Topology Service (according to ExchangeSetup.log). The error that was reported was Event 1002, MSExchangeSetup, "Exchange Server component Mailbox role: Transport service failed .... Unable to set shared config DC", but that failed due to this error: "Topology Provider coundn't find the Microsoft Exchange Active Directory Topology service on end point 'TopologyClientTcpEndpoint (localhost)'".
Ultimately the solution was adding the domain name to the NIC's IP4 properties, advanced DNS tab, "DNS suffix for this connection:". We found it by comparing ifconfig /all output between hosts where setup.exe succeeded and failed.
Additionally, all our DCs were reachable on the network from the failing servers, according to "netdom /query dc", but Event Viewer event 2080 reported the AD Topology Service found no Out-of-site DCs. After adding the domain suffix, the Out-of-site DCs were discovered. Lastly, running setup.exe the last time, having it proceed where it left off after detecting "Incomplete setup", the Mailbox role: Transport Service step again stopped at 97%, but manually starting the AD Topology Service while it was trying allowed it to complete the Transport Service step, and complete the full installation successfully.
Related Application Events:
Error 4027, Process ExSetupUI.exe (PID=10988). WCF request (Set Config DC DOMAIN.COM) to the Microsoft Exchange Active Directory Topology service on server (TopologyClientTcpEndpoint (localhost)) failed. Make sure that the service is running.
After fix: Info 2810, Process Microsoft.Exchange.Directory.TopologyService.exe (PID=6992). Microsoft Exchange Active Directory Topology Service is starting. Step completed - TopologyServiceMain.Main() - ExWatson Register completed.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(243.2, 73%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPS%3C/text%3E%3C/svg%3E)
Solution:
To resolve the error, take the following steps.
Step 1. Right-click the windows icon and then click Run.
Step 2. Type services.msc and then hit enter from the keyboard.
Step 3. Locate and double-click the 'Microsoft Exchange Active Directory Topology'.
Step 4. Click 'Start' to start the servic
Step 5. Problem is Reslove Than login ECP.
Problem Is Screen shots