Product: TIBCO Spotfire®
Windows Time Sync Errors in the Event logs indicates communication issues on the Spotfire Server / Node Manager machines
Spotfire Server and Node Manager machines installed on a Windows server may experience communication issues which can be due to time synchronization errors seen in the event logs.
The following message can be seen the event log:
NtpClient was unable to set a domain peer to use as a time source because of discovery error. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1
Follow the steps given in the resolution section of the referenced Microsoft Wiki article to get around this issue:
**********************************
Address discoverability issues
The Windows Time service cannot discover the configured time source peer. Ensure that the time source peer is online and available. There should be other events in Event Viewer that indicate that there is a problem locating a domain controller. Review those event messages and resolve them as appropriate. When you have resolved them, resynchronize the local Windows Time service with the time source peer. 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 resynchronize the client with the 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 /resync, and then press ENTER. The command output indicates whether the synchronization was successful.
**********************************
https://social.technet.microsoft.com/wiki/contents/articles/1374.event-id-129-microsoft-windows-time-service.aspx
Comments
0 comments
Article is closed for comments.