Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

Connection Server unable to accept vCenter thumbprint with an error "There was an error identifying the validity of the server" (67701)

Last Updated: 5/19/2023Categories: TroubleshootingTotal Views: 55243Language:
JapaneseEnglish

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Symptoms

The Connection Server unable to accept vCenter thumbprint with an error "There was an error identifying the validity of the server"

Unable to edit desktop pool with VC error.

vCenter status shows red in View admin dashboard

Unable to verify vCenter certificate.

Logs from the Connection server will contain error messages similar to the below:
For additional information on these logs , please see:

Location of Horizon View log files (1027744)

Collecting VMware Horizon View log bundles (1017939)

2019-03-06T08:28:14.843-06:00 DEBUG (0FC0-184C) <VirtualCenterDriver-8785064c-ad09-4db8-9b98-fd9696610b53> [CertMatchingTrustManager] invalid certificate (and no trusted thumbprint) for
vcenterfqdn.com:443 InvalidCertificateException[reasons:notTrusted; subject:'C=US, CN=vcenterfqdn.com' message:'ValidateCertificateChain Result: FAIL, EndEntityReasons: , ChainReasons: partialChain, noTrust']
2019-03-06T08:28:14.844-06:00 ERROR (0FC0-184C) <VirtualCenterDriver-8785064c-ad09-4db8-9b98-fd9696610b53> [ServiceConnection25] Problem connecting to VirtualCenter at https://vcenterfqdn.com:443/sdk
2019-03-06T08:28:14.844-06:00 WARN  (0FC0-184C) <VirtualCenterDriver-8785064c-ad09-4db8-9b98-fd9696610b53> [VirtualCenterDriver] Unable to establish a connection with VC <https://vcenterfqdn.com:443/sdk> using VIM 2.5 binding

Cause

If there are self-signed certificates on the vcenter - for instance - if the cert present on the vcenter admin page says untrusted or windows cannot verify -  the connection server will likely have the same response.

If the  vCenter certificate is added to the  trusted root of one or more connection server  but not on all.

This can also happen if only the root CA of vcenter is added to the  trusted store of Connection Server but not the complete chain

Impact / Risks

Both Provisioning and new/existing client sessions  will not be available during connection server reboot. This work is best scheduled during a maintenance window.

Resolution

The recommended and preferred method is to ensure your vCenter server has a ca signed cert.
Please refer to Replacing default certificates with CA signed SSL certificates in vSphere 6.x (2111219) or the latest documentation for your edition of vCenter.

1. Please download a copy of your vCenter root certificate using the following guide: How to download and install vCenter Server root certificates to avoid Web Browser certificate warnings (2108294)

2. Import the vCenter certificate along with the root certificates  to Connection Server trusted root folder in all the connection server ( this is the windows certificate store.

Procedure :

On the Windows Server computer, click Start and type mmc.exe.

In the MMC window, go to File > Add/Remove Snap-in.

In the Add or Remove Snap-ins window, select Certificates and click Add.

In the Certificates snap-in window, select Computer account, click Next, select Local computer, and click Finish.

In the Add or Remove snap-in window, click OK.

Navigate to the trusted root folder

7. Import the vcenter certificate here - one method is with the actions option
(more actions-> all tasks- > import )

Restart Services to bind the Certificate:

Restart the Connection Server service to load the new certificate. For more information, see Stopping, starting, or restarting VMware View services (1026026).

If you experience issues while starting the Connection Server service after installing the new certificate, please check Troubleshooting SSL certificate issues in VMware Horizon (2082408)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Horizon

Related Versions:

VMware Horizon 8

VMware Horizon 7.x

VMware Horizon 7

Take Our Survey

Support Assistant