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-packagesvCenter 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-packagesvCenter 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.