Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Connecting to vCenter Server using the vSphere Client fails with the error: Invalid URI: The hostname could not be parsed (1033990)

Symptoms

  • vSphere Client fails to connect to vCenter Server
  • Connecting to vCenter Server using the vSphere Client fails
  • You see one of these errors:

    Invalid URI: The hostname could not be parsed

    Invalid URI: The format of the URI could not be determined

Resolution

This issue occurs if you have modified the VirtualCenter.VimApilurl and VirtualCenter.VimWebServicesUrl attributes in the vCenter Server advanced settings and have set these attributes to the vCenter Server IP address instead of the FQDN.

Note: vCenter Server advanced settings can be modified by navigating to Administration > vCenter Server Settings > Advanced Settings.

After these attributes are modified, you are unable to log into vCenter Server using the vSphere Client and, therefore, cannot revert these attributes back to the FQDN.

To resolve this issue, modify the ADAM database in vCenter Server to revert these attributes to the FQDN.

To modify the ADAM database:
  1. Connect to the ADAM database.

    In Windows 2003:

    1. Go to Start > Programs > ADAM > ADAM ADSI Edit. The ADAM Editor opens.
    2. Right-click ADAM ADSI Edit and click Connect to....
    3. Click Distinguished Name (DN) or naming context and type:

      dc=virtualcenter,dc=vmware,dc=int

    In Windows 2008:

    1. Go to Start > Administrative Tools > ADSI Edit. The ADAM editor opens.
    2. Right-click ADSI Edit at the root level and click Connect to.... The Connection Settings window appears.
    3. For Connection Point, click Select or type a Distinguished Name or Naming Context and type:

      dc=virtualcenter,dc=vmware,dc=int

    4. Under Computer, click Select or type a domain or server and then select localhost from the dropdown or type:

      localhost:389

    5. Click OK.

  2. Expand the tree items in the left pane and find the entry OU=Instances.
  3. Expand the OU=Instances folder and double-click the Instance.

    Note: If Linked Mode is in use, select the Instance ID that corresponds to the vCenter Server with the issue.

    You see two entries: CN=VIMAPI and CN=VIMWEBSV.

  4. Right-click CN=VIMAPI and click Properties.
  5. Scroll down and locate the vmw-vc-URL attribute.
  6. Click Edit and change the IP address to the FQDN. For example, https://vCenter.vmware.com:443/sdk.
  7. Click Apply and then click OK.
  8. Repeat steps 5 through 7 for the CN=VIMWEBSV attribute.

    You are now able to log into vCenter Server using the vSphere Client.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 2 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 2 Ratings
Actions
KB: