Finally a succesfully install of vSphere 5.1 Server - had the same password issues like alot of other users. But there are problems with the VirtualCenter Management Webservices service - It cannot start (failed to start as well during install)
Trying to start the service manual :
Windows could not start the VMware VirtualCenter Management Webservices service on <SERVER>
Error 1067: The process terminated unexpectedly
Eventlog error :
The VMware VirtualCenter Management Webservices service terminated unexpectedly. It has done this 1083 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
As long this service cannot start I am not able to see Performance status on any host/ VM or health status on any hosts.
Any ideas how to make this service work?
(The last install was a clean install - uninstalled all other VMWare, removed old directories, but reused the old database, as we have a lot of configurations)
During the install I get this error : Error: 29942 Value: VMware VirtualCenter Management Webservices
UPDATE : Tried to install vShpere 5.1 Server on another server - straight forward Simple Install and no errors. So it seems that there is something one the current server that block this service?. So I guess I have to install it on a new Server and try to restore/ reuse the current MSSQL-database.
I should mean so - all ports are default by the installation and there is no firewall enabled on the server.
I remember once that you could see which ports VMware uses or are configured to use, but I forgot this?
I am having the same problem, I just upgraded my vCenter from 5.0 U1 to 5.1, and now i got this all time:
"The VMware VirtualCenter Management Webservices service terminated unexpectedly. It has done this 47 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service."
Some one, any idea? Maybe SSL?
Have a look at this KB for enabling logging for web services - this should give you more info on where the problem lies.
I gave up on my server and decided to install all over on another Bladeserver I had. (reusing the database) after that it starts succesfully. Not the perfect solution, but it got me running again.
Our workaround: We found a hidden process using a utility from sysinternal called "process explorer" which identified a process called "java" using port 8080, killed the process and web management services started. This is a workaround and the ticket remains open with VMware for a resolution. I suspect it is a JRE/Java environment issue from the previous vCenter 4.1 installer leaving something behind after the upgrade to 5.1a?
Had the same issue, here is how i resolved this.
Hope this helps someone else.
Well, I jusr uninstalled the vCenter and Installed again, working fine now, but when I re-installed, the setup adviced me that the port 8080 was being used by another program, I disable the service, and install successfully.
Please try this KB and modify the entry in VPXD.cfg file.
follow the below and try.
To work around this issue the increase the threadstack size in the vpxd.cfg file
now we are able to access the VC.
We have the issue with vsphere 5.5 .