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

Updating to vRA 7.3.1/7.4 fails when IaaS installation binaries were not updated to new version (54753)

Last Updated: 7/14/2020Categories: TroubleshootingTotal Views: 4165Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

When you perform an automatic upgrade to vRealize Automation 7.3.1/7.4, the upgrade fails on the primary IaaS website node.

In the Management Agent log file, you see entries similar to:

error MSB4057: The target "UpgradeApprovalsEntitlements" does not exist in the project.

Note: The Management Agent MSI upgrade log could be found in the following location: %Installation_folder%\VMware\vCAC\Management Agent\Logs\All.log

Purpose

This article provides information on what steps to take when there is a failover of the vRA virtual appliances and the replica nodes still have the old IaaS installation files.

Cause

This issue occurs when:

The current Primary appliance is not the first VAMI url listed in the affected Management Agent's configuration (VMware.IaaS.Management.Agent.exe.Config) file, in section <managementEndpoints>.

The Replica virtual appliance(s) failed to upgrade automatically and the automatic IaaS upgrade started.

Resolution

This is a known issue affecting VMware vRealize Automation 7.3.x.

Currently, there is no resolution.

Workaround

To work around this issue, follow either one of the workarounds:

Restore the environment to the backup taken before upgrade.

Change the current Primary appliance to be the same as the first VAMI url listed in the affected Management Agent's configuration (VMware.IaaS.Management.Agent.exe.Config) file, in section <managementEndpoints>.

Retry the upgrade.

Alternatively:

Copy the contents of the IaaS download directory from the Primary appliance  in /opt/vmware/share/htdocs/service/iaas/download.

Overwrite with it the contents of the same folder on all replicas respectively. This way only the IaaS nodes (including the IaaS database, if it is external) should be reverted to pre-upgrade state and its upgrade could be retriggered by running the automatic IaaS upgrade script manually ("/usr/lib/vcac/tools/upgrade/upgrade").

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

Result 1 of 1

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.4.x

VMware vRealize Automation 7.3.x

Take Our Survey

Support Assistant