I'm unable to unregister the vCenter extension ["EMC Avamar Backup & Restore"] . If I paste it in the UnregisterExtension, I get 'InvalidArgument' . I also can't click on the extension in the browser. I get a browser error when it tries to navigate to ..../mob/?moid=ExtensionManager&doPath=extensionList%5b"EMC%20Avamar%20Backup%20%26%20Restore"%5d , err_empty_response. I believe both are related to the spaces or the & in the name of the extension. Does anyone have ideas?
thanks
You're supposed to use the key ID which should have no spaces or ampersands. If you're trying to use the name it won't work to begin with.
I was just following the steps in the KB - VMware Knowledge Base
Step 4 - Select and copy the name of the plug-in you want to remove from the list of values under Properties
I see William Lam suggests clicking on the item, and copying the value from the key field, which appears to have the same value as the name from the previous screen https://www.virtuallyghetto.com/2010/07/how-to-unregister-vcenter.html however, if I click on mine, I get an error
I'm trying to find the file through a recursive search of the VCSA via WinSCP, since browsing through the plug-in directories I saw referenced in various KBs didn't turn anything up. I already have an SR open about rapid memory leakage in VCSA, and I thought maybe this bad plug-in was the cause. I'll just ask my support engineer about it during the call.
Yes, you'd normally click on the extension and use the "key" value as shown below. In your case, it's converting spaces to HTML codes which may be breaking it. You might want to work with support to see how to go about unregistering that extension in this case.
Hi
Did you get this resolved? I have come across exactly the same issue on a vCenter I am cleaning up before upgrading.
Thanks
Tony
SAAAAAME. 😕
*insert annoyed groan here*
Every time I click on "EMC Avamar Backup & Restore" to try to find the key, it throws the error:
upstream connect error or disconnect/reset before headers. reset reason: connection termination
...so. Kinda stuck too.
Same boat here. Would have been nice if the thread owner posted the resolution!
I ran into this too some time ago, and solved it via PowerCLI.
Some time later I read that someone solved this by simply renaming the "Key", but I never tried this myself.
André
You're awesome @a_p_ . Worked like a charm, FINALLY.
Thank you!