Upgrade to vRA 7.x fails on the IaaS nodes with error "event.broker.error.provider.not.found"

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• Upgrade to vRealize Automation 7.x fails on the IaaS nodes.
   
• In the C:\Program Files (x86)\VMware\vCAC\Management Agent\Logs\All.log file on the IaaS web node(s), you see the entries similar to:
  
  C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe>vcac-config.ex
  e RegisterCatalogTypes -v
  Catalog registration starting.
  
  System.AggregateException: One or more errors occurred. ---> VMware.Cafe.JsonRes
  ponseException: event.broker.error.provider.not.found

Environment

VMware vRealize Automation 7.1.x
VMware vRealize Automation 7.2.x
VMware vRealize Automation 6.x
VMware vRealize Automation Desktop 6.2.x
VMware vRealize Automation 7.x
VMware vRealize Automation 7.3.x
VMware vRealize Automation 6.2.x
VMware vRealize Automation 6.2
VMware vRealize Automation Desktop 6.2
VMware vRealize Automation 7.4.x
VMware vRealize Automation 7.0.x

Cause

This is occurs due to mismatch of the IaaS solution user within the environment pre-upgrade.

Resolution

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

To work around this issue:

1. Validate that the IaaS nodes are functioning properly prior to upgrade.
2. Take snapshot of your vRA environment.
3. Re-register the solution user by executing these commands on the primary web node:
   1. Vcac-Config.exe GetServerCertificates -url https://<vRA VA FQDN or VIP Address for load balanced environments> --FileName .\Vcac-Config-[yyyymmdd].data -v
      Note: Vcac-Config-[yyyymmdd].data is a configuration file generated in step 1 and is consumed in step 2 and step 3. You have your own data file name such as, Vcac-Config-20150217.data. Replace <vRA VA FQDN or VIP Address for load balanced environments> with the FQDN or VIP address for the vRA appliance.
   2. Vcac-Config.exe RegisterSolutionUser -url https://<vRA VA FQDN or VIP Address for load balanced environments> --Tenant vsphere.local -cu [email protected] -cp <password> --FileName .\Vcac-Config-[yyyymmdd].data -v
      
      Note: Replace <password> with the password for [email protected] in your vRA environment.
       
   3. Vcac-Config.exe MoveRegistrationDataToDB -d <Name of IaaS DB in SQL> -s <IaaS DB server address> -f .\Vcac-Config-[yyyymmdd].data -v
      
      Note: If you are unsure of the -d and -s values, navigate to C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Web\web.config and search for repository. After the <connectionString> section, look for the Data Source= line and add this value in the -s value. Look for Initial Catalog= line and add this value in the -d value.
4. Review the environment to ensure there are no other errors or indications that affects the environment.
   1. Check all services are REGISTERED in the vRA VAMI.
   2. Check all VAMI tabs under vRA Settings to confirm there are no errors.
   3. Make sure there are no errors in the IaaS node's Windows Events logs.
   4. Open the UI and confirm you can access all tabs without error
5. Proceed with the upgrade.