https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxOTE3IiwiaGFzaCI6IjQ0MGI0NWNkLWJkZGMtNDAzMC05NDFmLWY5MmMzNGUxZjM1ZiJ9
1-800-691-1991 | 9am - 8pm ET
EN

Monitoring of vSphere 4.x fails with Veeam MP v7

Challenge

Though everything is configured correctly and you have successfully added vCenter 4.x or standalone ESX 4.x to Veeam Extensions as a Monitoring target,
no data is shown in SCOM and you can see "Veeam VMware Collector: VMware connection is unavailable" alerts .
 
Additionally, the following errors are logged in the vmspi.log file (you can export logs as described here):
 
1) In case vCenter 4.x is connected:
 
 [0030] VimCL+** [CL100] , target=name_of_VC
 [0030] EXCOL+** [VP120] retrieveHostProperties failed,    at nworksCore.Collectors.VimClient.getObjectProperties(String timer, Object[] objList, String[] properties)
   at nworksCollector.Collectors.EsxPerfCollector.retrieveHostProperties(List`1 topoNodes), target=name_of_VC
 [0019] VPCOL+** [VP038] buildInventory failed [name_of_VC],    at nworksCollector.Collectors.VcPerfCollector.buildInventory(), target=name_of_VC
 [0019] EXCOL+** [VP210] performanceDaemon: connection lost to name_of_VC,    at nworksCollector.Collectors.EsxPerfCollector.performanceDaemon(), target=name_of_VC
 
2) In case standalone ESX 4.x is connected:
 
[0039] VimCL+** [CL100] , target=name_of_ESX
[0039] EXCOL+** [VP120] retrieveHostProperties failed,    at nworksCore.Collectors.VimClient.getObjectProperties(String timer, Object[] objList, String[] properties)
   at nworksCollector.Collectors.EsxPerfCollector.retrieveHostProperties(List`1 topoNodes), target=name_of_ESX
 [0039] EXCOL+** [VP035] buildInventory: Retreive host properties failed,    at nworksCollector.Collectors.EsxPerfCollector.retrieveHostProperties(List`1 topoNodes)
   at nworksCollector.Collectors.EsxPerfCollector.buildInventory(), target=name_of_ESX
 [0039] EXCOL+** [VP038] buildInventory failed @ I,    at nworksCollector.Collectors.EsxPerfCollector.retrieveHostProperties(List`1 topoNodes)
   at nworksCollector.Collectors.EsxPerfCollector.buildInventory(), target=name_of_ESX
 

Cause

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:

https://name_of_ESX/mob/?moid=ha-host&doPath=runtime

The missing property is called dasHostState. This is what the host MOB looks like if the property is not present:

User-added image

Solution

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"

User-added image

"Veeam VMware Collector" service needs to be restarted after adding the key.

More information

Please note, that the dasHostState vSphere HA property is not gathered anymore for any hosts monitored by the Collector, where the mentioned registry key was created.
KB ID:
1917
Product:
Veeam Management Pack for Microsoft System Center
Version:
7.x
Published:
2014-08-08
Last Modified:
2020-08-28
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.