Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

"Unable to update CM service info" while connecting to the Update Manager 6.5 (76298)

Last Updated: 1/23/2020Categories: TroubleshootingTotal Views: 13641Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

When we click on Update manager tab we get an error message "Problem occurred while connecting to the Update Manager server. See the vSphere Web Client logs for more details".

updatemgr-utility.log:
[2019-11-19 12:19:35,876 INFO] Install Key store for Jetty
[2019-11-19 12:19:36,905 INFO] Keystore installed successfully.
[2019-11-19 12:19:37,203 INFO] Updating VUM extension with VC
[2019-11-19 12:19:37,433 INFO] Updating CM service info
[2019-11-19 12:19:37,433 INFO] Enter updateCmServiceInfo
[2019-11-19 12:19:37,433 INFO] Client's property file: /usr/lib/vmware-updatemgr/firstboot/updatemgr.properties
[2019-11-19 12:19:37,625 ERROR] CM ReRegisterService failure. Exception is (cis.cm.fault.ComponentManagerFault) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
msg = '',
faultCause = <unset>,
faultMessage = (vmodl.LocalizableMessage) [],
errorCode = 0,
errorMessage = 'UNKNOWN'
}
[2019-11-19 12:19:37,625 ERROR] Unable to update CM service info

cm.log
2019-11-19T12:19:37.477+01:00 [pool-2-thread-1 [] INFO  com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider (95e80f53-2516-487a-b704-d2760bbd8add)] Site affinity is disabled
2019-11-19T12:19:37.602+01:00 [pool-2-thread-1 [] INFO  com.vmware.vim.sso.client.impl.SiteAffinityServiceDiscovery (95e80f53-2516-487a-b704-d2760bbd8add)] Site affinity is disabled
2019-11-19T12:19:37.621+01:00 [pool-2-thread-1 [] ERROR com.vmware.vim.sso.client.impl.SoapBindingImpl (95e80f53-2516-487a-b704-d2760bbd8add)] The SSL certificate of STS service cannot be verified
com.vmware.vim.sso.client.impl.ssl.UntrustedSslCertificateException: The SSL certificate of STS service cannot be verified
at com.vmware.vim.sso.client.impl.ssl.StsSslTrustManager.validateServerIdentityWithThumbprint(StsSslTrustManager.java:227) ~[wstClient.jar:?]

Cause

The update manager service is failing to start since the STS_INTERNAL_SSL_CERT certificate is expired.

Resolution

This issue can be resolve by replacing the STS_INTERNAL_SSL_CERT certificate with the MACHINE_SSL_CERT certificate.

For more information, please refer to KB article to replace the STS_INTERNAL_SSL_CERT certificate: Process to replace the STS_INTERNAL_SSL_CERT with the machine cert from the MACHINE_SSL_CERT

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
「ネイティブ Active Directory IDS または LDAP Active Directory IDS がすでに登録されています (There is already a native AD IDS or LDAP AD IDS registered)」エラーが表示され、Active Directory ドメインからの vCenter Server Appliance の分離または離脱ができない (71083)

KB
•
升级到 vSphere 6.7 Update 3 后，无法通过 HTML5 客户端检索 vSAN 相关信息 (74731)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware vCenter Update Manager 6.5.x

Take Our Survey

Support Assistant