Error downloading plugin-in: com.vmware.h4.vsphere.client
Welcome to my first blog of 2021! Its been a crazy year so far, but glad to be back writing. This issue is one that has been bothering me for some time in my vSphere 7 environment. Every time I logged into the vSphere Client i got the following error. “Error downloading plug-in. Make sure that the URL is reachable and the registered thumbprint is correct.” I finally had a few moments to research the issue and resolve it.
On each and every login the download plugin task would run and it would fail. It would fail not only on the version 0.4.0.0 but also on the version 0.3.5.0. I did a quick google search and came across this post with some instructions that worked for me.
This was a workaround that worked for me. Make sure to take a backup and/or snapshot of the environment and open a VMware case for production environments.
Run the following command to find the plugin Service ID for the versions, in my case this was for version 0.4.0.0 and 0.3.5.0.
1/usr/lib/vmware-lookupsvc/tools/lstool.py list --ep-type com.vmware.cis.vsphereclient.plugin --url http://localhost:7090/lookupservice/sdk
Once you have your Service ID run the following command to unregister the obsolete plugin. enter in yourpassword and the Service ID
1/usr/lib/vmware-lookupsvc/tools/lstool.py unregister --url http://localhost:7090/lookupservice/sdk --user '[email protected]' --password 'yourpassword' --id 'serviceid' --no-check-cert
Repeat for each obsolete plugin. In my case I ran this twice, once with the Service ID for 0.4.0.0 and then again with the Service ID for 0.3.5.0
Restart the vSphere UI service
1vmon-cli -r vsphere-ui
You should now be able to login without any errors!
As always William comes through with some simplification! Take a look at this gist that contains code to automatically grab the SID, Unregister and Restart the service.
Here’s a quick modified code snippet that’ll automatically handle identifying the correct serviceId, unregister & restart service :)— William Lam (@[email protected]) (@lamw) February 1, 2021
Code reference is at https://t.co/qcagIVoy2a pic.twitter.com/krQu4VW3Mf
This error only seemed cosmetic which is why it took my so long to resolve it. Hopefully this will be fixed in a future release to automatically cleanup obsolete plugins. I hope this has helped resolve your issue…
If you have any additional questions or comments, please leave them below!comments powered by Disqus