There are many reasons why this particular service won’t start, but a really popular reason involves clocks on the client and server. Even if the time in your taskbar and the time on your AD Server are the same, they may not be the same somewhere else on the machine, or so I’ve learned. Here’s how to find out, and how to find out what else it may be:
The service we are talking about is the Microsoft Exchange Information Store service, store.exe, or MSExchangeIS. The default location for the executable for Exchange 2010 is here:
“C:\Program Files\Microsoft\Exchange Server\V14\bin\store.exe”
If you try and start the services, you’ll typically get this error:
This is actually great advice! You’ll need to check the event viewer to see what’s wrong. Head to Server Manager > Diagnostics > Event Viewer (On a Server 2008 R2 Server). In the Summary on the front page, scroll down to MSExchangeIS and look for the EventID error, double click to see more details. Here’s what I see when I get this error:
Unable to initialize the Information Store service because the clocks on the client and server are skewed. This may be caused by a time change either on the client or on the server, and may require a restart of that computer. Verify that your domain is correctly configured and is currently online.
Neat, Dan. How do I fix it?
You’ll need to reset the clock based on your AD Server and then restart services so Exchange notices the changes. Here’s how:
Net time \\ADServerName /Set
ADServerName is the name of your AD Server. You’ll be prompted to make the change, and sometimes, just like you see in the screenshot below, the times will be set. If you are pointing to the right domain controller, do it:
Once done, you’ll need to restart the Microsoft Exchange Active Directory Topology. This service has lots of dependencies, or many services are dependent on it, so they will be listed and will restart as well, including the pesky MSExchangeIS Service. Once everything restarts, you’ll be all set.
As I said in the beginning, there are lots of reasons why services fail. Check your Event Viewer and see what’s going on with the service. Microsoft does many things difficult, but the Event Viewer can be your friend sometimes. Learn to use it to your advantage!
As always, these posts only get better if I have feedback. Let me know how it goes.