The vRealize Automation appliance management interface can help you resolve registration problems with vRealize Automation component services.

Problem

Under normal operation, all vRealize Automation component services must be unique and in a REGISTERED state. Any other set of conditions might cause vRealize Automation to behave unpredictably.

Cause

The following are examples of problems that might occur with vRealize Automation component services.

  • A service has become inactive.

  • Server settings caused a service to be in a state other than REGISTERED.

  • A dependency on another service caused a service to be in a state other than REGISTERED.

Results

Re-register component services that appear to have problems.

  1. Take a snapshot of the vRealize Automation appliance.

    You might need to revert to the snapshot if you try different service changes, and the appliance ends up in an unpredictable state.

  2. Log in to the vRealize Automation appliance management interface as root.

    https://vrealize-automation-appliance-FQDN:5480

  3. Click Services.

  4. In the list of services, look for a service that is not in the correct state or has other problems.

  5. To have vRealize Automation re-register the service, log in to a console session on the vRealize Automation appliance as root, and restart vRealize Automation by entering the following command.

    service vcac-server restart

    If there are services associated with the embedded vRealize Orchestrator instance, enter the following additional command.

    service vco-restart restart

  6. If a faulty service is the iaas-service, take the following steps to re-register it.

    1. Do not unregister the service.

    2. On the primary IaaS Web Server, log in with an account that has Administrator rights.

    3. Open a command prompt as Administrator.

    4. Run the following command.

      "C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.exe" RegisterSolutionUser -url https://appliance-or-load-balancer-IP-or-FQDN/ -t vsphere.local -cu administrator -cp password -f "C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.data" -v

      The password is the administrator@vsphere.local password.

    5. Run a command to update the registration information in the IaaS database.

      SQL Server with Windows Authentication:

      "C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.exe" MoveRegistrationDataToDb -s IaaS-SQL-server-IP-or-FQDN -d SQL-database-name -f "C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.data" -v

      SQL Server with Native SQL Authentication:

      "C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.exe" MoveRegistrationDataToDb -s SQL-server-IP-or-FQDN -d SQL-database-name -su SQL-user -sp SQL-user-password -f "C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.data" -v

      To find the server or database name, inspect the following file in a text editor, and search for repository. Data Source and Initial Catalog values reveal the server address and database name, respectively.

      C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Web\Web.config

      The SQL user must have DBO privileges on the database.

    6. Register the endpoints by running the following commands:

      "C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.exe" RegisterEndpoint --EndpointAddress https://IaaS-Web-server-or-load-balancer-IP-or-FQDN /vcac --Endpoint ui -v
      "C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.exe" RegisterEndpoint --EndpointAddress https://IaaS-Web-server-or-load-balancer-IP-or-FQDN /WAPI --Endpoint wapi -v 
      "C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.exe" RegisterEndpoint --EndpointAddress https://IaaS-Web-server-or-load-balancer-IP-or-FQDN /repository --Endpoint repo -v    
      "C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.exe" RegisterEndpoint --EndpointAddress https://IaaS-Web-server-or-load-balancer-IP-or-FQDN /WAPI/api/status --Endpoint status -v

    7. Resart IIS.

      iisreset

    8. Log in to the primary IaaS Manager Service host.

    9. Restart the vRealize Automation Windows service.

      VMware vCloud Automation Center Service

  7. To re-register any services associated with an external system, such as an external vRealize Orchestrator instance, log in to the external system and restart the services there.