Event IDs 1103 and 4506 may also be observed.
The root cause is currently investigated by Microsoft. This article will be updated after the research is completed.
To work around the issue, do the following:
Move the affected Collector to another time zone (it has to be different from GMT+1).
Restart nworks Virtual Infrastructure Collector service.
Move the Collector back to the preferred time zone.
If you have any questions or problems, please contact Veeam Support at http://www.veeam.com/support
Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.