For convenience, Exchange administrators set Exchange services to automatic start. So, they can start all Exchange features and functions without manually restarting the services. However, this automatic starting of Exchange services may not work always. Some Exchange administrators see that the Exchange services are not automatically restarted after a system reboot. It creates a difficult situation for them.

If your Exchange Server 2016 services are also not getting started automatically after you have performed a reboot, try this

Many Exchange experts suggest rebooting of Microsoft Exchange Server as a quick fix under the circumstances like unable to send/receive messages by users, directory service issues, CPU performance issues, etc. Rebooting may solve these problems. In fact, it is recommended to reboot the Exchange Server twice a month for better functioning of the Exchange Server.

But, once you have rebooted the Exchange Server and finds that all Exchange Services did not get started automatically, then there is a problem. The services which generally refused to get started automatically (shows Stopped as the status) after rebooting are:

 rebooted the Exchange Server

One can try the below-given method to manually restart the Exchange Services, which did not get started automatically after the reboot.

Restarting the Exchange services manually

To restart the Exchange services manually, you must access the system on which the Exchange Server 2016 is installed. Then follow the given steps:

  1. Press Windows+R, type services.msc, and click OK.
  2. Run services.msc

  3. In the opened Services page, select a Microsoft Exchange Service, which shows Stopped as the status, right-click on it and then click the Restart option from the menu.
  4. Microsoft Exchange Service

This will take some time to start each Microsoft Exchange Service, but the problem can be resolved by performing this.

What if the Exchange database is not accessible?

You can try the above method to restart the Exchange services, but it might happen that users can still not access the Exchange mailboxes to send or receive emails. This condition gives a strong sign of corruption in the Exchange database. There are manual solutions like the in-built Eseutil application for fixing the corruption in the EDB file, but all are time-taking, unreliable, unsafe, and lengthy.

For smooth and safe recovery of the corrupted Exchange database file, we recommend trying the best Exchange Server recovery software in the market, Kernel for Exchange Server. It can automatically recover and restore mailboxes database in Exchange. Some important features of the advanced Kernel for Exchange Server tool are:

  • Recovery of all sort of EDB data, including mailboxes, archive mailboxes, and public folders
  • Compatible with all Exchange Server versions (including 2016 & 2019)
  • Includes advanced filters and options for mailbox item selection based on user needs
  • Various saving destinations like Outlook, Office 365, live Exchange, Outlook profiles, etc.
  • Easy drag/drop, copy/paste, export options to move data between the source & destination
  • Support for Office 365 cloud (all plans)
  • Demo version for a free trial (with some saving limitations)

This advanced software incorporates a simple and interactive Graphic User Interface for the users’ convenience.

Download Free

Summary

Though set for automatic start, sometimes Exchange services fail to restart automatically after a system reboot. After rebooting, Exchange administrators will have to restart them manually. Apart from this, Exchange Server is vulnerable to many other issues like corruption. In severe corruption cases, the EDB file may show multiple types of errors, and the ESEUTIL tool may further delete the data rather than recovering it. Kernel for Exchange Server Recovery will recover the entire mailbox and save them to a Live Exchange again.