asked on

Exchange 2013 services do not automatically start on server reboot.

Hi,

We are running Exchange 2013 on Windows Server 2012 R2 Standard. When we restart this server, the following Exchange services do not automatically start, even though the services are set to "Automatic":
MSExchangeADTopology
MSExchangeAntispamUpdate
MSExchangeDagMgmt
MSExchangeDelivery
MSExchangeDiagnostics
MSExchangeEdgeSync
MSExchangeFastSearch
MSExchangeFrontEndTransport
MSExchangeHM
MSExchangeIS
MSExchangeMailboxAssistants
MSExchangeMailboxReplication
MSExchangeRepl
MSExchangeRPC
MSExchangeServiceHost
MSExchangeSubmission
MSExchangeThrottling
MSExchangeTransport
MSExchangeTransportLogSearch
MSExchangeUM
MSExchangeUMCR

If I log in and start these services manually, they start up right away with no issues and everything works great. I don't see any errors in the event logs about services being unable to start, and I've checked the dependencies for the services against another Exchange 2013 running 2012 R2 Standard and don't see any issues there. Has anyone else run into this before with 2013 on 2012 R2? Any ideas on how to resolve this?

Thanks

Jian An Lim

I have seen this before on virtual environment especially CPU and memory was too low.
what was your specs?

Also, this issues was known if it is running on DC which hopefully you are not.

Lafzo

The main reason services wont start automatically is if their dependencies are not met.
Also the event viewer will not display this as an error, it will display as a warning.
Filter your event viewer for warnings and then read / identify which dependency is not being met

Simon Butler (Sembee)

All of those services are dependant on the first one - AD Topology. If that fails to start then the rest do as well.

Primary reason for that is the server is coming up too quickly and the network isn't ready. This will not be an Exchange issue, but elsewhere. Could be an issue with the network switch it is connected to for example.

Simon.

OAC Technology

ASKER

This IS running on a domain controller. I'm not seeing any warnings in the event viewer regarding the service startup, either. Sembee, I think you're probably right. Is there a way to have these services wait for network connectivity? Would setting them as delayed start have any effect?

Thank you

ASKER CERTIFIED SOLUTION

Simon Butler (Sembee)

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Jian An Lim

Hi Datadudes,

cool. If it is a domain controller on exchange, then it is known to have such issues. (happen in SBS world all the time)

I will follow this article, and pick one method.
https://support.microsoft.com/en-au/kb/940845

p/s: Simon comment is valided, but the above method should get you going

OAC Technology

ASKER

That was the issue, there was an old primary DNS entry from when the server was being migrated. I made sure that the server had only itself listed in DNS and everything is working great now.

Thanks!