What Can Happen When Exchange System Times Are Not In Sync

Follow

Summary

This Knowledgebase article provides information about what can happen when any database application's system times are not in sync.

 

More Information

System time differences of one hour or more cause problems starting Exchange, SQL server, and other database systems following a switchover or failover. As a rule of thumb, the maximum "safe" time difference is less than or equal to the minimum time required to complete a switchover.

Below are a few of the tested scenarios:

The Secondary (passive) server is behind the Primary (active) server by 1 hour (Summer Daylight Savings Time change in March).

Results:

The Information Store does not start and logs event IDs 5000 and 5003. The latter informs the user that the client and server times are skewed and that the issue needs to be resolved.

Resolution:

Synchronize the time clock. See KB 1551 (linked below) for information about how to create this task.

The Secondary (passive) server is ahead of the Primary (active) server by 1-hour (e.g. Daylight Savings Time change in October).

Results:

The server may start the Information Store successfully. However, under some circumstances you may see events 7024 and 7000 logged. This is likely to occur if an antivirus product is running.

Resolution:

Synchronize the time clock. See KB 1551 (linked below) for information about how to create this task.

Servers are in different time zones.

Presently not supported. The Secondary should be configured in the same time zone as the Primary.

 

Applies To

All Versions.

 

Related Information

Knowledgebase Article #53 Server Clocks are Not Synchronized

Knowledgebase Article #1551 How to Create a Task to Synchronize the Time of the Passive Server with the Active Server When Neverfail Heartbeat V5.3 and Later is Installed

 

KBID-84

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.