This article offers advice on how to REGISTER a failed iaas-service in vRealize Automation. In several cases, when upgrading vRA from 6.1.x to 6.2.x or replacing certificates, can cause a trust failure and unable pull the new certificates into the IaaS. But make sure the certificates being replaced are valid. Most of the times this also results with “HTTP Error 503. The service is unavailable” and also fails the data collection process. Occasionally we can see 404 and 401 errors as well.
- Test Load Balancer redirects: https://Load_Balancer_FQDN/VMPS2
- Test the active Manager Service directly: https://Iaas_Manager_Service_Server_FQDN/VMPS2
- If the Manager Service is configured correctly, it should rshow an XML page with no certificate warnings.
- If it shows 404 errors, try using the IP address instead of FQDN to check if there is any issues with DNS.
- If you receive 404 errors using FQDN and IP, log in to the Manager Service server directly and try to connect to https://localhost/vmps2
- Check if this works https://localhost/Repository/Data/ManagementModelEntities.svc
- If this succeeds, it’s likely have a DNS problem.
- If this fails then mostly IIS repository website is not operational.
- If it connect to the site successfully but receive an REPO 404 error then it must be the connectivity issue between IaaS web and SQL server. Also make sure NTP is proper.
- Check if Microsoft Distributed Transaction Coordinator Service (MS DTC) is working fine on all IaaS and DB servers.
- For more details follow the KB 2114572
- Rebuild the trust between all components within vRealize Automation 6.x environment.
- It will always suggest to take backup of all vRA appliances and related databases.
- Re-register the first vRealize Automation appliance with SSO.
- Check if the vRA service account has appropriate access to the vRA database.
- In model manager data server, go to "C:Program Files (x86)VMwarevCACServerModel Manager DataCafe"
- Rename the existing file to keep an old copy "vcac-config.data" to "vcac-config.old"
- Vcac-Config.exe GetServerCertificates -url https:// --FileName .vcac-config.data
- Vcac-Config.exe RegisterSolutionUser -url https:// --Tenant -cu -cp --FileName .Vcac-Config.data –v
- Vcac-Config.exe MoveRegistrationDataToDB -d -s -f .Vcac-Config.data –v
- Vcac-Config.exe RegisterEndpoint --EndpointAddress https:///vcac --Endpoint ui -v
- Vcac-Config.exe RegisterEndpoint --EndpointAddress https:///Repository --Endpoint repo -v
- Vcac-Config.exe RegisterEndpoint --EndpointAddress https:///WAPI --Endpoint wapi -v
- Vcac-Config.exe RegisterEndpoint --EndpointAddress https:///WAPI/api/status --Endpoint status –v
- Restart the IIS service in IaaS web servers.
- Restart the vCloud Automation Center Server service in IaaS servers.
- Restart each vRealize Automation appliances.
- For more details follow the KB 2110207
Note: If you are using the vRealize Automation Guest Agents, you may need to import any updated certificates for the IaaS Manager Servers into each of your templates containing the Guest Agent.
To resolve this issue when there is an incorrect or corrupted certificate in the VRMGuestAgent folder on the windows guest OS, delete the .PEM file located at C:VRMGuestAgent directory in your Windows template.
- Stop the VRMGuestAgent service
- Delete the .PEM file located at C:VRMGuestAgent directory
- Uninstall the Guest Agent and run this command: c:VRMGuestAgentwinservice.exe -u
- Install the Guest Agent and run this command: c:VRMGuestAgentwinservice.exe -i -h :443 -p ssl
- Shut down the template or source virtual machine
- For Linux templates make sure the accurate "cert.pem" file is available in /usr/share/gugent/ folder of the Linux VM before the agent runs.
- For more details follow the KB 2068820 and KB 2052085