I've seen this issue only with version 5.1. I've never changed it after I've installed it in a different folder without spaces because there was no need. In version 5.5 I use the default folder and it works.
What I can remember is that the issue had something to do with Java. Maybe you ran a Java update and that initiates the issue?
We got the same problem after upgrading our vCenter Server to 5.5 U3 running on a physical standalone windows 2012 R2 machine,
turns out the problem was that the web client was installed on our D-drive - it worked on 5.5 original/5.5 U1/5.5 U2 on the D-drive without any problems funnily enough...
We just uninstalled the web client and did a reinstall on the default C-drive and path and everything works after that. Weird though...
Hi,It is often standard practice to install the server operating system on C: and then applications and data on additional drives such as E:, F: and so on.However vSphere Web Client since its 5.0 release though 5.1 and including the latest version at time of writing 5.5 U2, if you install vSphere Web Client to any directory other than the default installation directory you will get the following error when browsing to the vSphere Web Client page.
"HTTP Status 404
The requested requested resource is not available"
I've seen this problem for a while now and just tried latest release 5.5 U2b hoping it had been resolved (I couldn't find a reference in the release notes).
Unfortunately it is still a problem and while the rest of the components such as Single Sign On, Inventory Services and vCenter Server can be installed to another drive letter or directory, the vSphere Web Client must still be installed to the default directory of C:\Program Files\VMware\Infrastucture
If you've installed vSphere Web Client to anything other than the default directory and getting the error above, the only way to resolve this is to uninstall and re-install to the default installation directory provided by the wizard.
Fingers crossed it gets fixed in vSphere 6.0!