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

Troubleshooting missing plug-ins in vSphere Web Client when vCenters are in Enhanced Linked Mode (57727)

Last Updated: 11/7/2018Categories: TroubleshootingTotal Views: 33831Language:
Chinese (Simplified)JapaneseEnglish

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

Specific vSphere Web Client with missing plug-ins when vCenters Servers are in Enhanced Linked Mode. For Example: Update manager plugin, SRM plugin, NSX plugin

And

vsphere_client_virgo.log reports:

com.vmware.vise.vim.extension.VcExtensionManager Package <plug-in Name> was not installed!
followed by
Error downloading <plug-in download URL>

Location of vsphere_client_virgo.log:

vCenter Server that runs on Windows: C:\ProgramData\VMware\vCenterServer\logs\vsphere-client\logs

vCenter Server Appliance : /var/log/vmware/vsphere-client/logs

Cause

This situation occurs when the same plug-in extension is registered through multiple vCenters.
The extension manager of vSphere Web Client selects the first registration to download the package instead of downloading the same package multiple times.
This would avoid potential package deployment problems from same plug in getting downloaded more than once.
In case the first vCenter plug-in URL selected is not reachable, it might result in missing plug-ins situation with vSphere Web Client.

Resolution

Ensure network connectivity can be established from the impacted vCenter server to the plug-in download URL noticed in vsphere_client_virgo.log

Workaround

Manually upload the package to impacted vSphere Web Client from another vCenter:

Stop vSphere Web Client service on the impacted vCenter Server

Take backup of vc-packages/cm-service-package folder in the vCenter with impacted vSphere Web Client

vc-packages folder location for the plug ins published to web client as vCenter Extensions:

vCenter Server that runs on Windows: C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-packages
vCenter Server Appliance : /etc/vmware/vsphere-client/vc-packages

cm-service-package folder location for the plug-ins published as SSO service:
vCenter Server that runs on Windows: C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\cm-service-packages
vCenter Server Appliance : /etc/vmware/vsphere-client/cm-service-packages

Take the relevant  plug-in package folders from the vCenter where Plug-in is visible in vSphere Web Client and copy to impacted vCenter Server's vc-packages/cm-service-package folder

Take the backup of work and pickup folder from the impacted vCenter Server and delete the contents of the pickup and work folder.

Note: copy the folders to some other location as backup and avoid renamed backup folders in the same location

pickup and work folder location:

vCenter 6.0 that runs on Windows:
C:\Program Files\VMware\vCenter Server\virgo\server\pickup
C:\Program Files\VMware\vCenter Server\WebClient\server\work
vCenter Server Appliance 6.0:
/usr/lib/vmware-virgo/server/pickup
/usr/lib/vmware-vsphere-client/server/work

vCenter 6.5 and 6.7 that runs on Windows:
C:\programdata\VMware\vCenterServer\runtime\vsphere-client\server\work
C:\programdata\VMware\vCenterServer\runtime\vsphere-client\server\pickup
vCenter Server Appliance 6.5 and 6.7:
/usr/lib/vmware-vsphere-client/server/pickup
/usr/lib/vmware-vsphere-client/server/work

start the vSphere Web Client

Log in to the vSphere Web Client and check the plug-in availability

If this issue persists, contact VMware Support and note this Article ID (57727) in the problem description. For more information, see How to Submit a Support Request.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

VMware vCenter Server

Related Versions:

VMware vCenter Server Appliance 6.7.x

VMware vCenter Server Appliance 6.5.x

VMware vCenter Server Appliance 6.0.x

VMware vCenter Server 6.7.x

VMware vCenter Server 6.5.x

VMware vCenter Server 6.0.x

Take Our Survey

Support Assistant