Hello,
This is killing me, i have been working on the installation for the past two days following virtualjad POC guide and every step either doesn't work or something goes wrong, and at the end i reach to a dead end and i appreciate your help.
Installed everything, configured the tenants but when i login and navigate to the infrastructure tab i get the following error :
A required service cannot be reached at the expected address.
Please contact your System Administrator for assistance.
Reference error REPO404
and nothing inside work, all the tabs inside report the same.
after looking around and logging into the vcac appliance:5480 i find the Iaas-service failed
i'm installing vCAC 6.0.1
Is your vCAC Service Account added to the local admins group on all the IaaS servers? Can all the IaaS servers reach AD?
This error occurs due to following confrontational issues
1- Service account does have proper privileges on the IAAS server.
2- Communication between IAAS and vCAC server is not properly opened as per the Ports guideline.
3- IAAS server does not have sufficient compute resources available for IAAS ( Actual Service name vCloud Automation Center) to perform.
Try this out for more details on the IAAS Failure on vCAC Appliance
Open the URL : https://<VCAC APPLIANCE URL>/component-registry/services/status/current
look IAAS service and check for error message.
I would suggest to Reboot VCAC Appliance and along with it restart all vCAC services including DEMs.
Hope this will help you.
Br,
MG
One more reason that this can occur, if you are using certificates issued by AD CA that can not be reached by your vCAC Servers. I have seen this at one customer, and documented it in the following post: vCAC 6 Service Unreachable Reference error REPO404. As this particular error can be caused by different causes, check out your error logs, especially the Application event log on your IaaS Web and IaaS Manager.
Thanks,
Eiad Al-Aqqad
B: http://www.VirtualizationTeam.com
T: https://twitter.com/virtualizationt
The IAAS server's event logs are the right place to look for help, in my case i had enabled proxy in the IAAS server and all the requests where redirected to the proxy.