Exchange 2010: Unable to initialize the Information Store

Problem:  Rebooted my Exchange 2010 server and when it came back up the information store wouldn’t mount.   Looked in the application log and found the following 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 in the client or the server,  and may require a reboot of that computer.   Verify that your domain is properly configured and  is currently online.

Solution:
Found some instructions on the technet website that fixed my problem.

  1. Open a cmd prompt from the Exchange Server as administrator (right mouse click on the command prompt shortcut and select Run as Administrator)
  2. Run this command Net time \\ADServerName /Set
  3. Restart the Microsoft Exchange Active Directory Topology Service

*Important!! You have to restart the Microsoft Exchange Active Directory Topology Service or this fix will not work..  I tried just starting the Information Store service after running the command it it still failed..

Further reference:  Technet

28 thoughts on “Exchange 2010: Unable to initialize the Information Store

  1. This happened just after I had update the time on my NTP server. First the send connectors between my Ex2k7 and Ex2k10 servers reported authentication errors which was resolved by restarting the servers but after that the information store on the Ex2k7 wouldn’t come up. Serves me right for not looking at the event logs sooner. Mad props!!!

  2. thank you very much. I could upload it from your explanation uploading Microsoft Exchange Active Directory Topology Service

  3. This has worked for us. Even though time was not skewed and w32tm /query /status showed that it was synchronizing from a valid source, the IS service would not start and errors would be logged complaining of the clock being skewed. After running the command above and restarting the AD Topology service we were finally able to bring the IS service back up.

    Thanks a lot!!!

  4. Glad it worked for you. That’s an interesting variation to my problem. Thanks for sharing.

  5. This saved me as well, I don’t know why we keep having this same problem whenever the DC’s reboot (usually when we push an update), but I did write a simple batch file for the IS service to restart. In recovery I set it to run the following batch command:

    Net time \\ADServerName /Set
    net stop MSExchangeADTopology && net start MSExchangeADTopology

    Seems to correct itself then.

    THANKS Larry!

  6. Thank you very much. Happened right after the reboot after Installation of Exchange 2010 SP3 Rollup 5. Time was exactly the same as on the PDC. Your solution solved it.

  7. Glad it worked and thanks for the batch command. An nice addition to the solution as well.

  8. Add me to the list of “me too’s” that this fixed worked on. My time skew was all of 3 seconds after a reboot of Exchange 2010 :/

  9. Superb. And thanks for pointing out the need to restart the topology service 🙂

  10. The fix had to be applied after each reboot. Checked and noticed the time was off on the VMware Host server. Once the time was fixed on the VMware host the problem went away.

  11. Excellent! This should never happen but it did… I am very thankful it is fixed but any ideas on WHY? it happened? The Time change was 3 days ago… But the problem started today.. Very frustrating! Anyway I know the OP wrote this like 3 years ago but thank you!!!!

Leave a comment

Your email address will not be published.