Cannot start Exchange Services

Question

_{Friday, November 4, 2016 8:58 PM}

4027
Process umservice.exe (PID=4608). WCF request (Get Servers to the Microsoft Exchange Active Directory Topology service on server (TopologyClientTcpEndpoint (localhost)) failed. Make sure that the service is running. In addition, make sure that the network ports that are used by Microsoft Exchange Active Directory Topology service are not blocked by a firewall. The WCF call was retried 3 time(s). Error Details 
 No Minimal Required Number of Suitable Directory Servers Found in Forest ALLIA.LOCAL Site Default-First-Site-Name and connected Sites.
   at Microsoft.Exchange.Directory.TopologyService.ADTopologyDiscovery.Discover()
   at Microsoft.Exchange.Directory.TopologyService.ADTopologyDiscovery.DoWork(CancellationToken cancellationToken)
   at Microsoft.Exchange.Directory.TopologyService.Common.WorkItem`1.Execute(CancellationToken joinedToken)
   at Microsoft.Exchange.Directory.TopologyService.Common.WorkItem`1.<>c__DisplayClass6.<StartExecuting>b__4()
   at System.Threading.Tasks.Task.Execute()
   at Microsoft.Exchange.Directory.TopologyService.TopologyDiscoveryManager.EndGetTopology(IAsyncResult ar)
   at Microsoft.Exchange.Directory.TopologyService.TopologyService.InternalEndGetServersForRole(IAsyncResult result)
   at Microsoft.Exchange.Directory.TopologyService.TopologyService.<>c__DisplayClassa.<EndGetServersForRole>b__9()
   at Microsoft.Exchange.Directory.TopologyService.TopologyService.ExecuteServiceCall(Action action)

DefaultGlobalCatalog                               : dc-2.ALLIA.local
PreferredDomainControllerForDomain                 : {<ALLIA.LOCAL, dc-2.ALLIA.local>}
DefaultConfigurationDomainController               : dc-2.ALLIA.local
DefaultPreferredDomainControllers                  : {}
UserPreferredGlobalCatalog                         : dc-2.ALLIA.local
UserPreferredConfigurationDomainController         : dc-2.ALLIA.local
UserPreferredDomainControllers                     : {dc-2.ALLIA.local}
DefaultConfigurationDomainControllersForAllForests : {}
DefaultGlobalCatalogsForAllForests                 : {}
RecipientViewRoot                                  :
ViewEntireForest                                   : True
WriteOriginatingChangeTimestamp                    : False
WriteShadowProperties                              : False
Identity                                           :
IsValid                                            : True
ObjectState                                        : New

All replies (9)

_{Saturday, November 5, 2016 4:50 AM}

That message is telling you that you Exchange can't reach domain controllers in the same AD site.

Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Celebrating 20 years of providing Exchange peer support!

_{Saturday, November 5, 2016 8:15 AM}

Hi,

Yes, as Ed said correctly, your exchange server not able to read the domain controller. What you change recently on Exchange server or AD ? 

You may re-join the exchange server after doing a 'reset' the computer object name on ADUC. And restart after successfully rejoined. 

Thanks

Prabodha

_{Saturday, November 5, 2016 8:48 PM}

One of my DOMAIN Controllers died. Bluescreen. All the roles are on another good DC. 

_{Saturday, November 5, 2016 9:05 PM}

Is that other DC a GC? Any ADAccess errors in the Event Logs?

My Blog: http://exchangeitup.blogspot.com My Twitter: http://twitter.com/ExchangeITup

_{Sunday, November 6, 2016 8:02 PM}

Is that other DC a GC? Any ADAccess errors in the Event Logs?

My Blog: http://exchangeitup.blogspot.com My Twitter: http://twitter.com/ExchangeITup

The ads are fine , replication is good. I tried to reset machine and rejoin with no luck!

_{Sunday, November 6, 2016 10:05 PM}

I restored the bad dc from backup. Still same problem

_{Monday, November 7, 2016 4:14 PM}

Can you check on the Exchange server(s) for any ADAccess events; warnings/errors or otherwise?

My Blog: http://exchangeitup.blogspot.com My Twitter: http://twitter.com/ExchangeITup

_{Monday, November 7, 2016 4:50 PM}

It seems Exchange server is not able to reach AD,

1. checked you havent configured any other AD site , like DR AD Site and all

2. Make sure Repadmin /syncall is working fine ,also check the manual replication from dssite.msc

3. Also you can try a reboot of all the Exchange server , if everything looks ok to you

_{Tuesday, November 8, 2016 6:02 AM}

Hi,

Does there any upadtes with this issue?

Please try to manually restart Microsoft Exchange Active Directory Topology service and Microsoft Exchange Unified Messaging service, then check whether it works or not.

Please run run "Get-DomainController" to list working DC, then double check the DC or GC setting for Exchange server:
Get-ExchangeServer | FL Identity,*Static*
Get-ADServerSettings | FL

Please swithc those value by Set-ExchangeServer and Set-ADServerSettings if it remain point to a broken DC.

Best Regards,

Allen Wang

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].