Exchange 2013 not working after attempting to promote new dc in environment
Posted on 2014-09-22
I have an Exchange 2013 server that is not working. Over the weekend, we attempted to promote a new DC but that never finished as we were running into issues with it. The existing DC is an SBS2008 box which appears to be working OK at the moment. Since then, the Exchange server has stopped most of it's services and we are getting the following error, among other errors.
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2588) DOMAINNAME.local. Topology discovery failed, error details
The local server is not assigned to any site. This can be caused by incorrect configuration of subnets or sites or by replication latency. AD Topology Information won't be available until this issue is resolved..
What can I do to get this Exchange server talking to the original SBS, since that appears to be the issue? Also, Exchange was removed from the SBS a year ago and migrated to this 2013 server. The primary DNS server on the Exchange is still the SBS.