VCAC6.0 appliance services in failed state

[sankararumugam]

Looking to see if someone can help, I deployed VCAC 6.0 - vcac appliance, identity appliance, iaas server and seperate DB for iaas. Initially everything except iaas was well (no error, connection failures, etc) and iaas wouldn't install. I read other posts about .net 4.5 & .net 4.5.1 and fixed it, but the iaas service on vcac appliance "failed" to register. Trying to troubleshoot it, I tried change timezone settings, time settings, regenerate self certified SSL cert (all on vcac appliance) and now almost all services are showing as failed. I reverted back all changes, restarted multiple times and did everything I could, but unable to figure out what wrong. Also I see an error on licensing now where it gives 401 unauthorized error all the time and also trying to submit a license key gives the same 401 unauthorized error. Hoping someone can help.

[igorstoyanov]

> I tried change timezone settings, time settings, regenerate self certified SSL cert (all on vcac appliance) and now almost all services are showing as failed. These steps are causing the issues right now. Usually, changes in the VCAC appliance would not help with .Net services registration and the issues is somewhere in the windows part. You could try to recover if first synchronize the VCAC appliance time with the SSO appliance time  and then restart the VCAC appliance (usually after SSL certificate change a full restart is needed). This will not help with the IaaS issue but it could recover the VCAC appliance part.

[igorstoyanov]

BTW, this blog post could be also helpful about SSL reconfiguration: http://www.vmtocloud.com/vcac-6-ssl-configuration-gotcha/

[sankararumugam]

Thanks a bunch Igor.. Yes, changing timezone settings, time settings & regenerate self certified SSL causes almost all services to fail in VCAC appliance. I tried restarting everything and synchronizing time too, nothing worked. I had to re-install the vCAC appliance which solved it.

[chinnaswamy]

This issue occur with unexpected shutdown of Identity and VCAC appliances.

First check SSO status in VCAC appliance.If SSO not connected then check in the identity appliance.

Regenate SSO certificate in Identity Appliance after that SSO will show status as Running.

Connect SSO in VCAC appliance with the credential(administrator@vsphere.local). Finally apply license in VCAC setting.  Then refresh services in home page of VCAC surely it will start all services.

I got resolved with this same issue in my Environment.

[GrantOrchardVMw]

Please *do not* go through cert regeneration after a forced outage. You simply do not need to do this. All the "failed" implies after a forced shutdown is that you do not have your startup order correct.

If you change certificates, then you will need to go through the process of getting the various components to "trust" each other again as the cert will no longer match the known thumbprint.

Grant