vRealize Automation's 7.x VAMI page generates An "Uncaught Exception" error within a client browser when reviewing the Cluster tab

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• Logging into vRealize Automations 7.x (vRA) VAMI and navigating to the Cluster tab generates the following error:

Node FQDN has mismatched component versions!

• When a vRealize Automation 7.x log bundle is generated, the Environment file contains a reported Agent as:

Agent(Unknown)

• Client browser console logging output has similar errors within the Network tab:

:5480/locale/vamilocale_.properties:1 Failed to load resource: the server responded with a status of 404 (Not Found)
:5480/service/administration/view-deploy.xml:1 Failed to load resource: the server responded with a status of 404 (Not Found)
837C770123C6290521C43CA249AAF723.cache.html:852 [ERROR] Uncaught Exception: (TypeError) 
 __gwt$exception: <skipped>: Cannot read property 'b' of null
com.google.gwt.core.client.JavaScriptException: (TypeError) 
 __gwt$exception: <skipped>: Cannot read property 'b' of null

​Note:  The Developer tools within your client browser can be accessed by hitting F12 and navigating to Network.

Environment

VMware vRealize Automation 7.x

Cause

This issue is caused by duplications in registry values for VRMAgentInstanceID on Windows virtual machine hosts hosting vRA IaaS components.

Resolution

VMware is aware of this issue.  See the workaround for further details.

Workaround:
Ensure there are valid backups before moving forward.

1. Log into each Windows component node participating as a Proxy Agent
2. Open regedit.exe
3. Navigate to HKLM\SOFTWARE\WOW6432Node\VMware, Inc.\VMware vCloud Automation Center Agents\
4. Isolate each VrmAgentInstanceId## that does not contain the following keys:

Name
Type
ComponentCondition
Note:  Invalid entries should only contain ComponentCondition values and are the target for deletion.

5. Delete any VrmAgentInstanceId## values that do not have a Name or Type.
6. Attempt to re-test the VAMI error in your client browser.
7. The Cluster tab should now load all Cluster components within the vRA cluster to include any IaaS components.

Additional Information

vRealize Automation Environment User Interfaces
Accessing vRealize Automation 7.x's Virtual Appliance Management Interface (VAMI) Best Practices