Updated 2014-04-14:
Today i received feedback from others who have seen the same problem:
- Darren Goff who reported this was caused by incorrect time in the vCAC Appliance.
- Brice Dereims who reported this happens 90 days after the installation. Admin account locked.
I have not seen this issues myself but it might be workt investigating if/when you see the below described behavior.
Thank you both for contribute to the blog post.
———————————————————
Original post
Yesterday i was back in a vCloud Automation Center (vCAC) 6.0 SP1 (6.0.1) proof of concept (POC) project which has been on-hold for various reasons in two weeks.
When i tried to log on to our Tenant and verify our environment i first received a web page containing only a “Submit” button:
When i clicked the Submit button i received a “HTTP Status 500 – 401 Unauthorized” error:
I was using Firefox when receiving the error so i decided to try Internet Explorer (IE) as well and when using IE i was immediately redirected to the i HTTP Status 500 – 401 Unauthorized web page.
I checked the catalina.out log file located in the directory:
- /storage/log/vmware/vcac/ on the vCAC Appliance
- /storage/log/vmware/sso/ on the vCAC SSO Appliance.
I didn’t manage to find something that pointed me to the root cause of the problem.
I also verified the vCAC Appliance services status via the https://vCAC-Appliance-FQDN:5480 web page and they looked ok:
We are using an external vCenter Orchestrator (vCO) server and that’s why the vcl service shows up blank under the status column.
I remember i saw the error receiving a web page including only the “Submit” button when using vCAC 6.0 a while ago and in that case the problem was solved by restarting the vCAC SSO appliance so i tried that.
That didn’t solve the problem but when restarting the vCAC appliance the problem was fixed and we could log back on to the system again.
Haven’t seen any other problem and everything has been working fine for 2 days now. I know it’s a good idea to open service requests (and i normally do) when receiving a problem but we decided not to.
I will update the blog post if i receive the error again because then we will open a service request with VMware.
2 pings