Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
Unable to initialize the Microsoft Exchange Information Store service because the clocks on the client and on the server machine are skewed. This may be caused by a time change either in the client or the server machine and may require a reboot of that machine. Other than that verify that your domain is properly configured and is currently online.
|English: Request a translation of the event description in plain English.|
In our case, the domain was online, working, and time on the Exchange box was the same as the time server, reboots did nothing to fix it. I restarted the Exchange Active Directory service (and the 5 others that go with it), then restarted the Information Store and System Attendant.
I found this error while i was trying to update my Exchange 2010 to SP3. Error in Service Pack 3 installation was "..unable to make admin interface connection to server. (hr=0x80040115...". After a look into event viewer, there was "..Source: MSExchangeIS Event ID: 5003 Description: Unable to initialize the Information Store service because the clocks on the client and server are..." listed.
In our domain, I have NTP synchronization on every server to an worldwide NTP server. All my servers had exactly the same time. So I was wondering why I was getting this error.
After a little look, I found the reason. In my VMware VCenter I saw, that the ESXi host which holds the Exchange server had an wrong time (however there is an NTP server configured). I changed the time on the ESXi manually. After an additional reboot of the Exchange server, the Information Store service started normally.
As per TB218848, a time change either on the client computer or server computer could cause this situation. To resolve this error, try one or more of the following:
- Restart the server computer.
- Verify that your domain is properly configured and is currently online.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated