vCAC Upgrade from 6.0.0 to 6.0.1 broke the embedded vCO

[kswamy]

I upgraded vCAC 6.0.0 to 6.0.1 and now the vCO appliance embedded with the vCAC Appliance seems to be broken. I am unable to connect to the default vCO from vCAC. In other words, when I login into vCAC Default Tenant /Advanced Services/Server Configuration and choose "Use the default Orchestrator Server", I get the error "Cannot connect to the Orchestrator server".

When I look at the log file , I see the below error message -

2014-02-28 20:58:16.268-0700 [http-bio-192.168.134.143-8281-exec-10] ERROR {} [VSOFactoryClient] [0002]User 'root@localos' is not authorized!

javax.security.auth.login.LoginException: [0002]User 'root@localos' is not authorized!

When I go to vCAC Appliance Management Interface, I see the vco service is not registered.

vco	o11n.com.vmware.csp.o11n.vco	2014 Feb 25 22:34:09
advanced-designer-service	com.vmware.csp.core.designer.service	2014 Feb 20 21:24:11	REGISTERED

Now the strange part is, I am able to start the vco-configurator service and go to configurator interface. I can also login to vco client and do normal stuff like running workflows, looking at vCenter, vCAC host inventory etc. I also see that the vco endpoint that I have setup within vCAC is working fine. So, everything works just fine except the above error.

[Matrix_1970]

Hi all,

I have the same error, but I have installed vCAC 6.0.1 (no upgrade). Any suggestions?

Thanks

Matrix

[tmactive]

Log into the vcac appliance, and start the orchestrator configurator service and then login to the VCO mgmt and see whats up.

https://vcacappliancefqdn:8283

username vmware

password vmware (unless it got changed)

[nikolovk]

That is really strange behavior. Can you check the network configuration of the embedded vCO server? What is selected as IP address?

[Burke-]

I have not done an upgrade myself and usually am just using pre-built environments that already have vCAC setup for me... but, if I were in this situation, the first place I would look is the vCAC Appliance Management page (port 5480 of the appliance addresss). Login as root, then go to the vCAC Settings tab, then the SSO sub-tab. Once there, re-enter the SSO information. Once re-entered and the SSO status shows "Connected", I would go to the System tab and Reboot the appliance... I'd then head off for a coffee & snack, then come back and check to see whether or not the services and embedded vCO are operating properly.

[Oli_L]

It may be that the upgrade has changed the configuration endpoint. You may need to add /vco (again). This is just a suggestion without knowing too much about your upgrade procedure..

Check this KB article out:

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2072212

Also, I would make sure that services are started and the configuration generally looks good.

Hope this helps somehow - please let us know as it would be good to know the culprit.

Oli

[thibveni]

Hi, did you find a solution ? i exactly have the same issue...

[Tom2k]

Hi @ all,

i have the same Problem after my vcac upgrade from 6.0.1 to 6.0.1.1.

You must start the vco Configuration Sevice manual and configure this on new https://vcacappliancefqdn:8283

Start the vco configurator service over the vcac console:

service vco-configurator start

Regrads Tom