Operational Defect Database
BugZero found this defect 4535 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb1462
An error message "Collecting thread has failed to initialize (Time difference between Veeam Monitor server and ESX host is too large. Make sure that NTP is enabled on ESX host and try again.) and will be stopped" in Veeam Monitor
Last update date:
1/18/2023
Affected products:
Veeam ONE
Affected releases:
8.0
Fixed releases:
No fixed releases provided.
Description:
Challenge
The error "Connection problems" appears with vCenter server or ESX(i) host in Veeam ONE Monitor client infrastructure view. vCenter server or the ESX(i) host becomes grayed out:
Cause
By default, Monitor requires server time to be less than a 5 minute difference between the Veeam Monitor Server and the VC or host that is having this issue. You will also see the following error in the logs: "Collecting thread has failed to initialize (Time difference between Veeam Monitor server and ESX host is too large. Make sure that NTP is enabled on ESX host and try again.) and will be stopped"
Solution
Make sure to have the time difference between Veeam Monitor and the host or VC having the issue no more than 5 minutes. This is achieved through NTP or other time protocols in one's environment. since v6.0 it is possible to modify the maximum allowed time difference by manually creating or modifying if exists the MaxTimeDiff value under HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam ONE Monitor\Service on Veeam One server and setting it to preferred in seconds > restarting Veeam One Monitor Server service.
More Information
If you have any questions, contact Veeam Support.
