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:
- Connect to the ADAM database.
In Windows 2003:
- Go to Start > Programs > ADAM > ADAM ADSI Edit. The ADAM Editor opens.
- Right-click ADAM ADSI Edit and click Connect to....
- Click Distinguished Name (DN) or naming context and type:
dc=virtualcenter,dc=vmware,dc=int
In Windows 2008:
- Go to Start > Administrative Tools > ADSI Edit. The ADAM editor opens.
- Right-click ADSI Edit at the root level and click Connect to.... The Connection Settings window appears.
- For Connection Point, click Select or type a Distinguished Name or Naming Context and type:
dc=virtualcenter,dc=vmware,dc=int
- Under Computer, click Select or type a domain or server and then select localhost from the dropdown or type:
localhost:389
- Click OK.
- Expand the tree items in the left pane and find the entry
OU=Instances.
- 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
.
- Right-click
CN=VIMAPI
and click Properties. - Scroll down and locate the
vmw-vc-URL
attribute. - Click Edit and change the IP address to the FQDN. For example,
https://vCenter.vmware.com:443/sdk
. - Click Apply and then click OK.
- Repeat steps 5 through 7 for the
CN=VIMWEBSV
attribute.
You are now able to log into vCenter Server using the vSphere Client.