Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

"Mismatched component versions" warning is reported within the vRealize Automation Management Interface after a Cumulative Update (76407)

Last Updated: 9/20/2023Categories: InformationalTotal Views: 3804Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

After applying a vRealize Automation cumulative patch you may see similar warnings within the vRealize Automation VAMI Cluster tab:

Node vra-Web-1.rainpole.local has mismatched component versions!
Node vra-Mgr-1.rainpole.local has mismatched component versions!
Node vra-Mgr-2.rainpole.local has mismatched component versions!
Node vra-DEMW-1.rainpole.local has mismatched component versions!
Node vra-DEMW-2.rainpole.local has mismatched component versions!

Cause

This issue occurs due to the dynamic link library (*.dll) files and executable (*.exe) files patched to a newer version as part of the cumulative update.

These warning are expected and do not indicate an issue in the following patch versions:

7.4 HF1 to 7.4 HF13

7.5 HF1 to 7.5 HF8

7.6 HF1

Resolution

A number of triggers for this issue are resolved in vRA 7.5 HF9 and 7.6 HF2 and later versions.

The component version information is read from the windows registry on the iaas servers and then relayed back to the VAMI by the Management agent component.

If the issue persist after applying the relevant patch then please raise a support request for further assistance.

In certain circumstances these registry key entries under HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\VMware, Inc.\ need to be cleaned up manually.

Procedure:
1. Login to the IAAS server with the alert in the VAMI.
2. Open Registry Editor
3. Navigate to  C: \> reg query "HKEY_LOCAL_MACHINE \ SOFTWARE \ WOW6432Node \ VMware, Inc. \ VMware vCloud Automation Center Agents "and removed the records with no type and name attributes.

Note: In General Availability (GA) environments - such warnings are indicative of a version mismatch and should be investigated. In such cases, please contact VMware Support. For more information, see Filing a Support Request in Customer Connect (2006985).

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
Application Remote Collector が再起動後、7.5 から 8.0 に自動的にアップグレードされる (76412)

KB
•
在 vRealize Automation 7.x 中禁用 Internet Information Services (IIS) 应用程序池回收 (76333)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Aria Automation

Related Versions:

VMware vRealize Automation 7.6.x

VMware vRealize Automation 7.5.x

VMware vRealize Automation 7.4.x

Take Our Survey

Support Assistant