tdubb123
Expert
Expert

geting error when registering vrealize application services to vra

I keep gettting this error when registering vrealize application services (darwin) to the vra.

can anyone help on this? Capture.JPG

0 Kudos
7 Replies
rcporto
Leadership
Leadership

Try the same command with the "tenant" option, take a look at documenation: Register Application Services to vRealize Automation

1

In the roo shell prompt, register Application Services to the vRealize Automation server.

register-vcac-server --componentRegistryUrl vCACServerURL --ssoAdministratorUsername UserName --ssoAdministratorPassword Password

The componentRegistryUrl is the URL for the vRealize Automation self-service catalog.

A sample URL for the componentRegistryUrl is https://vcac-oci-071.eng.test.com.

The registration might take approximately 30 seconds before the status message, vCAC server registered successfully, appears.

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
0 Kudos
tdubb123
Expert
Expert

I am using application director 6.2 and it does not like the --tenant=vsphere.local

option

0 Kudos
rcporto
Leadership
Leadership

Yes, this options seems like is required on 6.1 and previous.

And remember mark the question as correct or helpful.

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
0 Kudos
tdubb123
Expert
Expert

any tips on getting this registered on 6.2?

thanks

0 Kudos
rcporto
Leadership
Leadership

Just run the command without -tenant option, like this:

register-vcac-server --componentRegistryUrl https://vra.localdomain --ssoAdministratorUsername administrator@vsphere.local --ssoAdministratorPassword Password123@

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
0 Kudos
tdubb123
Expert
Expert

now I am getting this error

Screen Shot 2015-06-19 at 1.16.54 PM.png

0 Kudos
culps
Contributor
Contributor

I had the same error today. As I was testing a lab build I knew was working in previous tests I was a little surprised to see this.

I guessed my vrealize application server hadn't come back from the snapshot cleanly and a reboot of the appliance solved this problem.

Not the ideal fix but it completed the registration after the reboot.

0 Kudos