With Client 5.0
Reports submitted with WATS client v5.0 with a StartDateTime more than 5 minutes in the future (after time zones has been taken into consideration) are quarantined (see: Quarantine). The WATS server will attempt to process the report again after several minutes. Reports submitted with a StartDateTime more than one whole day in the future are quarantined, marked as invalid and will not be processed again.
With Client 4.2
Communication between WATS Server and Client v4.2 require the time on both machines to be synchronized. If the time between two hosts differ by more than 5 minutes (after time zones has been taken into consideration), communication will fail. Thus, all servers and clients should get the time from the same source, either directly or indirectly via an internal time server such as a domain controller or NTP server. Virtual machines should synchronize their clocks against this same server, not the host.
How to synchronize time
- VMWare Virtualization
(See: VMware Tools Time Synchronization and Configuration)
- How to configure an authoritative time server in Windows Server
(See: Configuring the Windows Time service to use an external time source)
- Configure a time source for the forest https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-r2-and-2008/cc794823(v=ws.10)
For hosts that are not member of a domain:
- How to synchronize the time with the Windows Time Service in Windows 10 https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-r2-and-2008/cc816656(v=ws.10)
- Set the clock https://support.microsoft.com/en-us/help/4026213/windows-how-to-set-your-time-and-time-zone
We recommend having a domain environment, where the PDC emulator in the forest root domain retrieves the time from an internet time server. In cases where there are more than one forest, each forest should retrieve the time from the same internet time server.