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 provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will try again in %1 ...
The time provider NtpServer encountered an error while digitally signing the NTP response for peer %1. NtpServer cannot provide ...
The time provider NtpServer encountered an error while digitally signing the NTP response for symmetric peer %1. NtpServer ...
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 ...