Exchange 2013 CU23 update - services now do not start automatically

James Wilson 1 Reputation point
2020-07-29T09:22:48.283+00:00

We have 4 Exchange 2013 servers, and i recently went began the process of upgrading each of them to CU23. The first server was running CAS and Mailbox roles, and updated perfectly fine. The second server was running just the CAS role and that again updated file. The third server is running just the Mailbox role, this completed the update without any issue, but now when the server is rebooted the Exchange services don't start automatically.

The services are still set to automatic, and if i go in and start them manually they start ok. I've tried setting them to Automatic Delayed Start but that doesn't make any difference.

Has anyone had this happen before?

Thanks
James

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,350 questions

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Andy David - MVP 141.6K Reputation points MVP
    2020-07-29T11:10:55.087+00:00

    Check the server component state and make sure they are all set to active.
    https://techcommunity.microsoft.com/t5/exchange-team-blog/server-component-states-in-exchange-2013/ba-p/591342

    I assume you took the server out of maintenance mode after upgrading and Exchange is not installed on a Domain Controller, yes?

    0 comments
  2. Lucas Liu-MSFT 6,161 Reputation points
    2020-07-30T06:12:29.637+00:00

    Hi,
    Except for Exchange service, can Windows services start automatically and normally?

    1. Is this Exchange server installed on the domain controller? If yes, Exchange services may not start correctly when the domain controller is also a global catalog server.
      For more information: Installing Exchange on a domain controller is not recommended
    2. Before starting the Exchange server, you need to make sure that the DC has been fully started, so please make sure that you start the Exchange server five minutes after the start of the DC.
    3. This may also be caused by network and hardware reasons, so please check if your memory is sufficient and DNS settings are correct.
      For more information: Exchange 2013 system requirements
      In addition, you also could check whether there are related error logs in the Event Viewer.
  3. James Wilson 1 Reputation point
    2020-10-02T12:56:00.657+00:00

    Just to follow up on this - i left the server alone for a week or so, and then put into maintenance mode again and rebooted it. This time the services did start as expected.

    0 comments