6.7

Solution
n
Log in to the vSphere Web Client as a user with permissions on the vCenter Server system.
The vCenter Server system will not appear in the inventory if you do not have permissions on it. For
example, if you log in as the vCenter Single Sign On administrator user, you might not have
permissions on any vCenter Server system.
n
Verify that the vCenter Server system is registered with the same Component Manager as the
vSphere Web Client.
The vSphere Web Client discovers only vCenter Server systems that are registered with the same
Componenent Manager.
Unable to Start the Virtual Machine Console
When you attempt to open a virtual machine console from the vSphere Web Client, the console does not
open.
Problem
When you attempt to open a virtual machine console from the vSphere Web Client, the console does not
open. The following error message appears:
HTTP ERROR 404
Problem accessin /. Reason:
Not Found
Errors similar to the following appear in the virgo-server.log file:
[2012-10-03 18:34:19.170] [ERROR] Thread-40
System.err
2012-10-03
18:34:19.167:WARN:oejuc.AbstractLifeCycle:FAILED org.eclipse.jetty.server.Server@315b0333:
java.net.BindException: Address already in use
[2012-10-03 18:34:19.170] [ERROR] Thread-40 System.err java.net.BindException: Address already in use
Cause
Another program or process is using port 9443, the default port used by the HTML5 virtual machine
console.
Solution
u
Edit the webclient.properties file to add the line html.console.port=port, where port is the
new port number.
The webclient.properties file is located in one of the following locations, depending on the
operating system on the machine on which the vSphere Web Client is installed:
Windows 2008
C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\
vCenter Server Appliance
/etc/vmware/vsphere-client/
vCenter Server and Host Management
VMware, Inc. 199