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

"VUM failed to authenticate" error when accessing Update Manager Plug-in from HTML Client 6.7 (60436)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 30931Language:
Chinese (Simplified)Portuguese (Brazil)JapaneseSpanishEnglish

13 like this article

Subscribe to get an email
newsletter with new updates

13 people found this helpful Please provide article feedback:

Symptoms

Update Manager Plug-in for vSphere Client/HTML5 Client 6.7 fails with an error:

error: VUM failed to authenticate

Update Manager plug-in for the vSphere Client becomes unauthenticated

Mostly observed only in HTML client, able to access update manager from Flash Client

On the updates tab of the vSphere client, you might see one of these error messages:

The session is not authenticated

VUM failed to authenticate

Security Error

In the vsphere_client_virgo.log (ui) file, you see entries similar to:

[2018-06-04T14:40:00.150-05:00] [INFO ] http-nio-5090-exec-4 com.vmware.vsphere.client.security.util.Util getUserSession called on an inactive session.
[2018-06-04T14:40:00.152-05:00] [ERROR] http-nio-5090-exec-4 com.vmware.vum.client.exceptions.LoggingController null
[2018-06-04T14:40:00.152-05:00] [ERROR] http-nio-5090-exec-4 com.vmware.vum.client.exceptions.LoggingController com.vmware.vum.client.exceptions.AuthenticationException
at com.vmware.vum.client.remoting.impl.VumServiceProviderImpl.getService(VumServiceProviderImpl.java:87)
at sun.reflect.GeneratedMethodAccessor3162.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333)
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:56) at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:60)at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:133) at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:121)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.eclipse.gemini.blueprint.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:57)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:133)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:121)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213)
at com.sun.proxy.$Proxy736.getService(Unknown Source)

Cause

This issue occurs when the Update Manager plug-in for the vSphere Client becomes unauthenticated if the Update Manager functionality is not used for some time.

Resolution

This issue is resolved in vSphere 6.7 U1, available at VMware Downloads.

To resolve this issue if you do not want to upgrade, reset the VUM database.

To reset the VUM database:

Connect to VCSA 6.7 via SSH.

Stop VMware Update Manger service by running this command:

# service-control --stop vmware-updatemgr

Reset VMware Update Manager Database by running this command:

# /usr/lib/vmware-updatemgr/bin/updatemgr-utility.py reset-db

Delete the content of VMware Update Manager patch store by running this command:

# rm -rf /storage/updatemgr/patch-store/*

Start the VMware Update Manager service by running this command:

# service-control --start vmware-updatemgr

Related Information

"Response with status: 401 OK for URL" while performing Update Manager Tasks on FireFox in vSphere 6.7 (59696)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (Brazil)JapaneseSpanishEnglish

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:

Related Versions:

Take Our Survey

Support Assistant