Veeam Collector tries to get one of the Host's properties which is missing in vSphere 4.x and fails during topology construction.
Confirm that the required property is not present. To do this, check the VMware MOB (Managed Object Browser) of the host. You can use the following link:
The missing property is called dasHostState. This is what the host MOB looks like if the property is not present:
To workaround the issue, you need create a Registry key to disable collection of dasHostState property. This needs to be done at every collector you use for monitoring vSphere 4.x environment
Path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Virtualization Extensions for VMware\Collector\Collector\GlobalSettings
Parameter name: summary.runtime.dasHostState
Parameter type: DWORD (32-bit)
Parameter value: "0"
"Veeam VMware Collector" service needs to be restarted after adding the key.
Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.