The time service detected a time difference of greater than %1 milliseconds for %2 seconds. The time difference might be caused by synchronization with low-accuracy time sources or by suboptimal network conditions. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. When a valid time stamp is received from a time service provider, the time service will correct itself.
The time sample was rejected because: Packet contains unreasonable root delay or root dispersion values. This may be caused ...
The time sample was rejected because: The peer is not synchronized, or it has been too long since the peer's last synchronization. ...
The time sample was rejected because: The peer is not synchronized, or reachability has been lost in one, or both, directions. ...
The time service attempted to create a named event which was already opened. This could be the result of an attempt to compromise ...
The time service detected a time difference of greater than %1 milliseconds for %2 seconds. The time difference might be ...
The time service discovered that the system time zone information was corrupted. Because many system components require valid ...
The time service discovered that the system time zone information was corrupted. The time service tried to reset the system ...
The time service encountered an error while reading its configuration from the registry and cannot start. The error was: ...
The time service encountered an error while reading its configuration from the registry, and will continue running with its ...