Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

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

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 25072Language:
JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

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:

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.

Related Information

vSphere Client を使用して vCenter Server に接続しようとすると、次のエラーで失敗する： 無効な URI: ホスト名を解析できませんでした

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
ESXi 用 QLogic HBA ドライバ/ファームウェアのデフォルト バージョン (2045449)

KB
•
执行物理机到虚拟机 (P2V) 转换失败并出现错误：出现常规系统错误。发现 SSL 无关联错误 (2002296)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
La conversión física a virtual (P2V) falla con el siguiente error: A general system error occurred. Found dangling SSL error (2002296)

Results 1-5 of 5

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 5.5.x

VMware vCenter Server 5.1.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

Take Our Survey

Support Assistant