Monitoring of vSphere 4.x fails with Veeam MP v7

KB ID: 1917
Product: Veeam Management Pack for Microsoft System Center
Version: 7.x
Published: 2014-08-08
Last Modified: 2020-08-28
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

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.
Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.