You may occasionally see errors in your eventlogs regarding the NtpClient or Time-Service. Most of the times these errors or warnings are temporary and are automatically fixed during the next time sync.
Event ID 129 – The entry is not found. (0x800706E1)
I faced event ID 129 today during a logon session on my Surface 4 Pro with Windows 10 installed. The exact error as shown in my event viewer was:
Event ID: 129
Source: Time-Service
NtpClient was unable to set a domain peer to use as a time source because of discovery error. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: The entry is not found. (0x800706E1)
As the error tells you, you should wait 15 minutes for a retry to occur. I’m not that patient, so I forced the sync:
C:\Users\ite>w32tm /resync
Sending resync command to local computer
The following error occurred: Access is denied. (0x80070005)
Oh, shoot, needed Administrator privileges. So again, open CMD but now “Run as Administrator”
C:\WINDOWS\system32>w32tm /resync
Sending resync command to local computer
The command completed successfully.
Better. 🙂
Now, I verified the eventlogs to be sure the error was gone.
Success events appear in the Eventlogs. Like:
Event ID 35 : The time service is now synchronizing the system time with the time source x (ntp.d|[::]:123->[x).
Event ID 37 : The time provider NtpClient is currently receiving valid time data from x (ntp.d|[::]:123->[x).
Event ID 138: NtpClient succeeds in resolving domain peer xafter a previous failure.
Bottom line of this blog post: Some error events in the event log may be caused by a temporary loss of connectivity to your network. For example during the startup of Windows 10, your NICs may not be ready in time to sync to your time server. In case of error 0x800706E1, it’s best to wait a few minutes and try again.
Bottom line of this blog post: Some error events in the event log may be caused by a temporary loss of connectivity to your network. For example during the startup of Windows 10, your NICs may not be ready in time to sync to your time server. In case of error 0x800706E1, it’s best to wait a few minutes and try again.
Bottom line of this blog post: Some error events in the event log may be caused by a temporary loss of connectivity to your network. For example, during the startup of Windows 10, your NICs may not be ready in time to sync to your time server. In case of error 0x800706E1, it’s best to wait a few minutes and try again.