The time service has not synchronized the system time for %1 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization.
The time service encountered an error while refreshing its configuration in the registry and cannot start. The error was: ...
The time service has been configured to use one or more input providers, however, none of the input providers are still running. ...
The time service has detected that the system time needs to be changed by %1 seconds. The time service will not change the ...
The time service has jumped the local system clock by %1 seconds. This occurs when the time source and local system time ...
The time service has not synchronized the system time for %1 seconds because none of the time service providers provided ...
The time service has stopped advertising as a time source because the local machine is not an Active Directory Domain Controller. ...
The time service is configured to use one or more input providers, however, none of the input providers are available. The ...
The time service is unable to register for network configuration change events. This may occur when TCP/IP is not correctly ...
The time that the current Job is scheduled to start. This time can be represented by the actual date and time, or an interval ...