Incorrect vRealize Automation Component Service Registrations

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.

Solution

Re-register component services that appear to have problems.

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.

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

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

Click Services.

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

If a faulty service is the iaas-service, go to the next step.

Otherwise, 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

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

Do not unregister the service.

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

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.