Last updated: Jul 23, 2018 19:58
Whenever the time on Windows machine (HSS or MCM on-premise) is not correct, multiple Perfecto services might not be (properly) operating.
There are several things that can go wrong and cause the time offset / lack of synchronization - below are a few suggestions to help you resolve the issue.
Time Zone must be UTC - Coordinated Universal Time
Windows' Time Service must not be disabled.
If it is not started, try to start it from either Services or CMD ( net start w32time )
- Make sure that the machine has internet connection (proxy configuration might be required)
- Go to Control Panel - Date and Time - Internet Time - Change Settings
- (Optional) Change Internet Time Server - if the current selection is not accessible or more appropriate one can be used.
- Click on Update now - if the time server is correctly set and there is internet connection, the synchronization will pass (the clock was successfully synchronized ...)
Generally Windows relies on Scheduled task (SynchronizeTime) for automatically updating server time.
- Check whether the Task is available & enabled (status Ready)
- Check when was the last time the task has succeeded or what was the error code if it failed
- (optional) Try to run it manually
Sometimes steps I-IV are not enough and the time cannot be properly updated - in such situations try with manual force re-synchronization:
- open CMD as administrator and run:
w32tm /resync /force
In rare occasions the above command might fail :
The computer did not resync because no time data was available
This might be caused by not properly configured Windows Time source. There are few options available:
Configuring the Windows Time service to use an internal hardware clock
Configuring the Windows Time service to use an external time source
Generally the setup which Perfecto offers to on-premise customers uses option 1) however customer's IT might have changed it due to internal requirements.
- If this is the case, then customer's Windows Administrators should be contacted
If the setup was not modified, check which is the current time source:
- in CMD run the following command
w32tm /query /configuration
2. Check the TimeProviders' Type. Value different than NTP(local) might cause issues
3. Change the type to NTP
- Start RegistryEditor (regedit) as administrator
- navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters
- change the value of Type to NTP
- restart Windows' Time service: net stop w32time then net start w32time in CMD
- run force time resync again