Microsoft Exchange 2013 Services will not start

We had a power failure and after the server come back online non of the Exchange services start. I know that most will not start due to the fact that Microsoft Exchange Active Directory Topology does not start. When I try to start it manually it start then stop.
This is the event viewr related to this problem.
Any idea

Process w3wp.exe (PID=3856). WCF request (Get Servers for infedo.local) 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
 System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService. The connection attempt lasted for a time span of 00:00:02.0124225. TCP error code 10061: No connection could be made because the target machine actively refused it  ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
   at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   --- End of inner exception stack trace ---

Server stack trace:
   at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
   at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at System.ServiceModel.ICommunicationObject.Open()
   at Microsoft.Exchange.Net.ServiceProxyPool`1.GetClient()
   at Microsoft.Exchange.Net.ServiceProxyPool`1.TryCallServiceWithRetry(Action`1 action, String debugMessage, WCFConnectionStateTuple proxyToUse, Int32 numberOfRetries, Boolean doNotReturnProxyOnSuccess, Exception& exception)
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Andy SCommented:
Looks like something might be blocking port 890 on that server, there's either another service running which is using that port, or a firewall blocking it.
I'd stop all non-essential services and start exchange first, then start the others one by one..
infedonetworkAuthor Commented:
Looks like somethign is wrong with Active Directory. I can't even acess it.
The server services stay on the starting state but it never start
Brian MurphyIT ArchitectCommented:
That is an refusal.  That happens with
1) Licensing
2) No all prerequisites (Domain, Forest - Functional Level, ADPrep)
3) This happens when the wrong binaries are downloaded from your MS MSDN or whichever page you have.

Did you download from Welcome to the Volume Licensing Service Center

If so, that might be the problem right there. Don't forget service Pack 1, minimum
Active Protection takes the fight to cryptojacking

While there were several headline-grabbing ransomware attacks during in 2017, another big threat started appearing at the same time that didn’t get the same coverage – illicit cryptomining.

Brian MurphyIT ArchitectCommented:
TCP error code 10061?

Doesn't that have something to do with IP V6?  Not network, at localhost level.  This causes issues with GPO policies as well, and Windows Time Service and other, other.

It is not IPV 6 itself but the IP Helper Service
C:\Windows\System32\svchost.exe -k NetSvcs

Provides tunnel connectivity using IPv6 transition technologies (6to4, ISATAP, Port Proxy, and Teredo), and IP-HTTPS. If this service is stopped, the computer will not have the enhanced connectivity benefits that these technologies offer.

I know it doesn't make sense now, but disabling this service has caused a lot of woes.
infedonetworkAuthor Commented:
Those are the 3 services that may be the main or the starting cause.
Server services will never start no matter how much I wait

infedonetworkAuthor Commented:
Ipv6 was set to use ::1 as DNS.
I changed it to obtain automatically but no changes on the services status. It may need a reboot
Brian MurphyIT ArchitectCommented:
Before that hassle.

Scroll Up, set IP Helper to Automatic.

Use Taskman to kill the PIDS of each exchange service trying to start.  Must be clean.

Start IP Helper Service (further up).

If that is disabled, very good chance of being the issue.
Brian MurphyIT ArchitectCommented:
Ipv6 was set to use ::1 as DNS.

Does not work if "IP HELPER" is disabled.

Hence, my original point.

Start IP Helper

Then reboot if you wish or use taskkill from the CMD prompt

Run CMD as Administrator, type tasklist

Then taskkill /IM myexe.exe /F /T

Then start IP Helper
Then start Exchange
infedonetworkAuthor Commented:
Ip Helper is started and I can restart it with no Problem.
Brian MurphyIT ArchitectCommented:
IP Helper
Pic attached
Brian MurphyIT ArchitectCommented:
I notice that Windows Firewall is not started but automatic.

Can you disable that?

Seems like a flat out port block.  Or, if using IP V6 from etc hosts the IP Helper service would cause it.

The other one is licensing, like the CD that was used to install it.

And there are more but those seem like the top.

Is there no error in Windows Event Log - Application

No 4027?
infedonetworkAuthor Commented:
I stop the firewall services but same problem
There is tons of 4027 and 1092 events on the application
The Firewall services is started fine but is disable under control panel so no blocking ports.
This server is running for the last 6 years so not licensing issue
One thing I should mention if it make any difference is that the exchange 2013 is install on the same server as the Domain Controler. I know is not recommend it but like I said it work for 5 years.
Something get messup today after a power failure that cause the server to shutdown the wrong way

infedonetworkAuthor Commented:
Also this tells me that something got corrupt on the AD
infedonetworkAuthor Commented:
I called Microsoft on this and looks like it was a problem finding the site name on the active Directory.
He enter it manually under the registry and after a reboot it all work fine.

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
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

From novice to tech pro — start learning today.