Initial data collection stuck at a certain point:
One or more configuration issues may occur:
Veeam ONE Monitor performance graphs show the "No Data Available" message.
VeeamDCS.log file may show the following errors:
Collecting thread will exit due to serious error (The operation has timed out)
Reporting DB event: Failed to collect infrastructure topology for object vCenter . The operation has timed out (VeeamInfCollectionFailedEvent)
Unable to collect events. The operation has timed out
Unable to collect performance. This operation returned because the timeout period expired
There can be a number of reasons for timeout.
Possible solutions are provided below:
Open the Veeam ONE Monitor console and navigate to Options > Server Settings > Hosts. Clear check boxes for all hosts except one. Wait for data to be imported successfully. If this helps, add hosts one by one to finish the initial data import.
Open Registry Editor on the Veeam ONE Server and create key named Service under HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam ONE Monitor. Create the HistQueryTimeoutSec D-WORD (32 bit) and set its value to 3600 in decimal. Next, create the RtQueryTimeoutSec key and set its value to 600 in decimal. If the keys already exist, change their values. Restart Veeam Monitor Server service.
If none of the above solutions help, see this VMware KB article. This issue may result in the described behavior with Veeam. Follow the steps provided in the article to resolve the issue.