Was unable to start the VMware vSphere Web Client after upgrading from 5.1 to 5.5 (it’s same after restore a vcenter 5.5)
Noticed that the VMware Vsphere web client service wasn’t started.
Tried manually via Services.msc got the following error;
Windows could not start the VMware Vsphere web client service on local computer.
Error 1053: The service did not respond to the start or control request in a timely fashion.
I realized that the folders in the new version installation had changed and for that reason paths should be changed also.
Check your Registry value for hkey_local_machine\system\currentcontrolset\services\vspherewebclientsvc:
“C:\Program Files\VMware\Infrastructure\vSphereWebClient\server\bin\service\bin\wrapper.exe” -s “C:\Program Files\VMware\Infrastructure\vSphereWebClient\server\bin\service\conf\wrapper.conf” set.default.SERVER_HOME=C:\Program Files\VMware\Infrastructure\vSphereWebClient\server set.default.JMX_PORT=9875
Look at these value and confirm that the WRAPPER file is located and accessible on the path mentioned above.
Always backup your registry before making changes.
For me I had to change the port (see below) for it to work, for others I have seen it is due to the path being incorrect or inaccessible. (with quote because Program Files have a space in name)
“C:\Program Files\VMware\Infrastructure\vSphereWebClient\server\bin\service\bin\wrapper.exe” -s “C:\Program Files\VMware\Infrastructure\vSphereWebClient\server\bin\service\conf\wrapper.conf” set.default.SERVER_HOME= »C:\Program Files\VMware\Infrastructure\vSphereWebClient\server » set.default.JMX_PORT=9877
Restart the server.