ESX hardware status change however, the change is not reflected in OpsMgr.

KB ID: 1149
Product: Veeam Management Pack for Microsoft System Center
Version: 5.6
Published: 2011-08-05
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

An ESX hardware status change takes place and is registered in VMware vSphere client. It also may be confirmed via the VMware MOB; however, the change is not reflected in OpsMgr.

Cause

The object properties added at the end of the object name are referred to as trailers. The overall health status of the host can be changed correctly in some scenarios, but the hardware item health status will not be updated in OpsMgr. Most often the health state of the affected hardware item may be "Unknown" (grey) in VMware vSphere client.

In nworks 5.6 the following issue with the state table exists: object properties are considered part of the object name and when a property is changed, it appears to nworks as if these are two different objects. Therefore, two state table entries appear - one for each object.

Solution

If the health status of the host is not updated in OpsMgr, first please check that nworks shows the corect status in the log.

If you are able to see the correct status in the log then you may require a patch to resolve your issue. Please submit a support request for the patch  via our support portal and include the applicable logs.

NOTE: The support team will make 100% sure that you are experiencing this specific issue described in this particular article before delivering the patch.

More information

Once you receive the patch, here is how to install it:

  1. Stop "nworks Virtual Infrastructure Collector service" service

  2. Back up "nworksCore.dll" and "nworksVIC.exe" from the Collector installation folder

  3. Replace "nworksCore.dll" and "nworksVIC.exe" with files from the archive

  4. Move "trailers.xml" to "[system_drive]\Program Files\nworks\VIC\Collector\Resources"

  5. Remove old "StateTbl.xml" from "[system_drive]\Program Files\nworks\VIC\Collector\Data"

  6. Start "nworks Virtual Infrastructure Collector service" service

Send Article Feedback
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.