Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

Migration from vRealize Automation 6.2.x to 7.2 - 7.3 leaves a large number of mismatched and empty resources in Deployments or fails with "504 Gateway time-out" or "413 Request Entity Too Large" errors (51096)

Last Updated: 2/26/2021Categories: TroubleshootingTotal Views: 4966Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

Migration from vRA 6.2.x to vRA 7.2 or 7.3 fails. You see any of these errors:

504 Gateway Time-out.

413 Request Entity Too Large.

Cannot access a disposed object.
Object name: 'System.Net.Http.HttpClient'.

If the migration from 6.2.x to 7.3 is successful, you see any of these results:

Empty deployments.

VMs belonging to more than 1 deployment.

VMs not associated with blueprints.

Cause

This issue occurs because, migration of environments that contain a large number of machines or blueprints can result in a timeout between vRA services resulting in incomplete migration of machines and blueprints.

Resolution

This is a known issue affecting VMware vRealize Automation 7.2 and 7.3.0.

This issue is resolved in VMware vRealize Automation 7.3.1 and VMware vRealize Automation 7.4, available at VMware Downloads.

Workaround

To work around this issue, before migration deploy the attached version specific hotfix on the target vRA 7.2 or 7.3 environment.

Note: If you have already run migration, you will need to revert the target vRA 7.2 / vRA 7.3 environment, deploy the fix and re-run migration.

Procedure:

Take a backup of these existing files:

Connect to the IaaS machine of the target 7.2/7.3 environment that hosts the Model Manager Data component.

Navigate to <vRA Install Folder>\Server\Model Manager Data\Cafe and rename these files:

VMware.Cafe.dll to VMware.Cafe.dll.bak

VMware.Cafe.Client.dll to VMware.Cafe.Client.dll.bak

Vcac-config.exe to Vcac-config.exe.bak

Download and unzip the attached version specific zip file ( 000051096_vRA 7.3 for vRA 7.3 and 000051096_vRA 7.2 for vRA 7.2)

Copy the extracted VMware.Cafe.dll, VMware.Cafe.Client.dll and Vcac-config.exe files to this <vRA Install Folder>\Server\Model Manager Data\Cafe folder.

To resolve the 504 Gateway Time-out error, increase the client and server timeouts of the HAProxy service:

SSH into the vRA virtual appliance.

Open /etc/haproxy/haproxy.cfg file.

Edit and change the following settings:

timeout client 500s to timeout client 3600s

timeout server 500s to timeout server 3600s

Save the file.

Restart the HAProxy service by running the command:
service haproxy restart

Repeat steps a to e for each virtual appliance in the system.

Open the <vRA Install Folder>\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.exe.config file, and add the CafeClientCacheDuration appSetting and set it to 5 hours:

<appSettings>
<add key="EventLogSource" value="vCAC" />
<add key="repositoryAddress" value="" />
<add key="repositoryTimeout" value= "200" />
<add key="repositoryIgnoreServerCertificateWarnings" value="true"/>
<add key="CafeClientCacheDuration" value="05:00:00"/>
</appSettings>

Run migration.

When migration is successfully completed:

Repeat Step 4 to reset the client and server timeout values of the HAProxy service back to 500s. Ensure to restart the HAProxy service when the settings are changed.

Remove the CafeClientCacheDuration setting that was added in Step 5, or set it to 1 hour:

<add key="CafeClientCacheDuration" value="01:00:00"/>

Note: This affects both vRA 7.2 and 7.3.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

000051096_vRA 7.3.zip

000051096_vRA 7.2.zip

Additional Resources

KB
•
vRO 控制中心出现错误“由于未应用配置更改，需要重新启动服务器” (2151288)

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

VMware vRealize Automation 7.2.x

VMware vRealize Automation 6.2.x

Take Our Survey

Support Assistant