Are using a Windows server?
The following should applicable only to the Appliance (VCSA). I recall running into this issue a couple times and the solution was to use the post install script, passing the "uninstall" option. Then manually checking the VCSA plugin folder for any remainders. Also a quick loop through the ESXi nodes in the cluster, making sure the Plugin-In VIB was gone "esxcli software vib list". Went ahead and rebooted the VCSA, and to be thorough a rolling main/reboot of the nodes. After the all clear with the plugin-in gone from the web client. I would then install plug-in RPM, run the post-install script; and reboot the VCSA. To be completely honest I haven't encountered this issue since two VCSA updates ago. At which point I don't recall if the plug-in was actually officially released. One time I fixed this problem by just uninstalling the plugin, and updating VCSA to the latest version.
1 person found this helpful
I had the same problem on the Windows version of vCenter. You need to launch a command prompt by right clicking and then Run as Administrator. Then launch the setup from the command prompt. Right clicking the setup file and then Run as Administrator does not work. Thank you, Zach.
It is really worked! Thank you sooooo much!