Event ID - 136

Event Id	136
Source	Microsoft-Windows-Time-Service
Description	NtpClient was unable to set a manual peer to use as a time source because of an unexpected error. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1
Event Information	According to Microsoft : Cause : This event is logged when NtpClient was unable to set a manual peer to use as a time source because of an unexpected error. Resolution : Resolve system issues The Windows Time service is receiving an error that indicates that the time source peer is not valid. However, this error indicates an underlying system issue. Look for other events in Event Viewer that indicate system errors. In addition, check the time source peer Event Viewer for system errors. Perform the following procedure on the computer that is logging the event to be resolved. To perform this procedure, you must have membership in Administrators or you must have been delegated the appropriate authority. To determine the name of the currently configured time source peer: Open a command prompt as an administrator. To open a command prompt as an administrator, click Start. In Start Search, type Command Prompt. At the top of the Start menu, right-click Command Prompt, and then click Run as administrator. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue. At the command prompt, type W32TM /query /status, and then press ENTER. The command displays the status of the Windows Time service synchronization. Check the computer name that is shown as the Source in the command output. This should be the name of a domain controller (or administrator-configured time server). Verify : To perform this procedure, you must have membership in Administrators or you must have been delegated the appropriate authority. To verify that the Windows Time service is synchronizing correctly: Open a command prompt as an administrator. To open a command prompt as an administrator, click Start. In Start Search, type Command Prompt. At the top of the Start menu, right-click Command Prompt, and then click Run as administrator. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue. At the command prompt, type W32TM /resync, and then press ENTER. At the command prompt, type W32TM /query /status, and then press ENTER. This command displays the status of the Windows Time service synchornization. The Last Successful Sync Time line of the output displays the date and time that you ran the W32TM /resync command in the previous step. Also, check the computer name that is shown as the Source. This should be the name of a domain controller (or administrator-configured time server). To confirm that the Windows Time service synchronized successfully with a time source peer, verify that Event ID 37 appears in Event Viewer. If there was a recovery from a previous failure to synchronize with the time source, you also see Event ID 137, which indicates that the Windows Time service is synchronized correctly.
Reference Links	Event ID 136 from Source Microsoft-Windows-Time-Service

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught