Exchange 2013 not working after attempting to promote new dc in environment

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.
dannymyungAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

R--RCommented:
Reboot the server once and check.
Make sure primary DNS is SBS in the NIC of exchange.
check if both exchange and sbs are on same site.
Make sure that the Remote Procedure Call (RPC) Locator service is running.

check this from http://technet.microsoft.com and http://social.technet.microsoft.com
http://technet.microsoft.com/en-us/library/ff360293%28v=exchg.140%29.aspx

http://social.technet.microsoft.com/Forums/exchange/en-US/34b1c301-ad12-4655-aeea-772e70c654bc/event-id-2142-2077-2069-msexchangeadtopology-exchange-2013?forum=exchangesvradmin
0
dannymyungAuthor Commented:
Tried rebooting. Also, the Primary DNS is the SBS in NIC of exchange.

RPC Locator was not running -- it is running now.

How can I check if exchange and sbs are on same site? When I went into AD Sites and Services on the SBS there was nothing under Subnets. I added the correct subnet and pointed it to the correct site.

Still unable to start the MS Exchange AD Topology service.
0
dannymyungAuthor Commented:
Ended up resolving myself. Followed instructions below regarding adding a registry key containing the site name and then rebooted and everything came back up. How can I fix it so that I don't have to keep it on this band-aid?

http://messagingschool.wordpress.com/2014/04/18/dsgetsitename-failed-status-1919-0x77f-installing-exchange-2013-sp1/
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
dannymyungAuthor Commented:
Found resolution on technet. Thank you.
0
Samir JiwaniCommented:
Root cause of the failure in a restore virtualized environment for me was the NTDS FSMO roles being on a DC unreachable, along with incorrect subnets setup in Sites & Services.  Once I fixed those, I was up and running.  Hope that helps :)
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.