When trying to log into the AutoLab vCenter server with the vi-admin account you get an error that says, “The vSphere Client could not connect to vc.lab.local. You do not have permission to login to the server: vc.lab.local”.
Cause – The vi-admin account does not have Administrator permissions in vCenter.
Solution – Log in using the email@example.com account with a password of VMware1.lab. That account info is missing from the AutoLab documentation. Once logged in you can assign the vi-admin account Administrator permissions to vCenter.
After rebooting the vCenter server & logging into the vSphere Web Client I noticed that all objects in the Inventory List had a quantity of 0.
A quick glance at the services showed that the VMware VirtualCenter Server, VMware VirtualCenter Management Webservices, & a few others were stopped. When starting the VMware VirtualCenter Server service I received an error that said, “Windows could not start the VMward VirtualCenter Server on ServerName.”
In the Application log there is an Event ID 1000 that says, “The description for Event ID 1000 from source VMware VirtualCenter Server cannot be found. Either the component that raises this event is not on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: Failed to initialize VMware Virtual Center. Shutting down… the message resource is present but the message is not found in the string message table.”
There is also a corresponding Event ID 7024 in the System log that says, “The VMware Virtual Server service terminated with service-specific error The system cannot find the file specified.”
Browse to %ALLUSERSPROFILE%\VMware\VMware VirtualCenter\Logs & open the newest vpxd-XX.txt file. Near the end of the file you find some entries similar to:
2014-03-07T19:23:54.477-06:00 [01784 warning ‘Default’] Closing Response processing in unexpected state: 3
2014-03-07T19:23:54.478-06:00 [01784 error ‘[SSO][SsoFactory_CreateFacade]’] Unable to create SSO facade: Invalid response code: 404 Not Found.
2014-03-07T19:23:54.478-06:00 [01784 error ‘vpxdvpxdMain’] [Vpxd::ServerApp::Init] Init failed: Vpx::Common::Sso::SsoFactory_CreateFacade(sslContext, ssoFacadeConstPtr)
Restart the VMware Identity Management Service. Then start the VMware vSphere Profile-Driven Storage Service, VMware VirtualCenter Server, & VMware VirtualCenter Management Webservices services.