Cannot Log In To VirtualCenter Server Using VI Client After VirtualCenter Server Upgrade or Installation

Details

Why can't I log in to my VirtualCenter Server using the VI Client after I've upgraded or installed it?

Solution

After you install or upgrade to VirtualCenter 2.0, the VirtualCenter service does not start properly, and you cannot log in to the VirtualCenter Server using the VI Client. If you check the status of the VirtualCenter service by choosing Start > Programs > Administrative Tools > Services, the VirtualCenter service is shown as stopped.

This problem is caused by a port conflict between the VirtualCenter service and another application. In addition to listening for VI Client connections on port 902, VirtualCenter uses:

Port 80 for the VirtualCenter WebServer components used by VI Web Access
Port 443 for the VirtualCenter SDK Web service

If applications such as Microsoft IIS have conflicts on these ports, one solution is to stop the conflicting service and start the VirtualCenter service as follows:

Choose Start > Programs > Administrative Tools > Services to display the services control panel.
Right-click the conflicting service and choose Stop from the drop-down menu.
Right-click the VirtualCenter service and choose Start from the drop-down menu.

If you must run VirtualCenter and the conflicting service simultaneously, another solution is to change the default ports used by the VirtualCenter components:

Uninstall VirtualCenter Server.
Reinstall VirtualCenter Server, specifying different default ports in the installation wizard to avoid the conflicts.

Keywords

relnotes;2150

Feedback

Actions

KB Article: 2150
Updated: Aug 14, 2009

Products:
VMware VirtualCenter
Product Versions:
VMware VirtualCenter 2.0.x

Knowledge Base