vCenter Infrastructure navigator – re-register vCenter server extension

Ran into some issue with our vCenter server recently which caused the refresh icon to keep spinning (updating) and would slow down performance and also could not perform any searches.

VMware support could not figure out the problem but eventioally provided information to investigate our plugins.

Troubleshooting:

Firstly we disable all the plugins and restarted vCenter server appliance services.
This caused the web client to crash whenever we selected the plugins!
Only way I found to fix this is:
–  Create copy of file /etc/vmware-vsphere-client/SerenityDB/serenity/ALL/client.package.states
–  Delete the original file
–  Close all browsers and login again.
–  All plugins should now again show enabled.
( Disclaimer:  I recommend contacting VMware support since this is not supported by VMware so please take snapshot&backup of VM and be careful)

Logged into vCenter Server MOB and unregistered all non-system extension.  This did not seem to fix the problem either but we found that Orchestrator connection was never fixed after we regenerated the certificate for vCenter server.
Not sure this caused our problems or the reset and deletion of plugins but soon after application was working as expected.

After un-registering plugins we have to of course register vCenter Infrastructure manager again:

Solution:

Log into the vSphere client pointing to the vCenter with the issue.
In top menu select Administration > vCenter Server Settings > Runtime Settings.
Verify the IP is correct for the vCenter you are wanting to monitor.

Shut down Navigator.
– These steps can only be performed from the .net vSphere client.
– Power down the virtual machine, right click the virtual machine from within the vSphere Desktop Client, select Edit Settings.
– Choose the vServices tab, click Edit. Under Provider select .
– Click OK and then OK again.
– Do not re-add it yet.

Log into the MOB for vCenter – https://Vc IP/MOB :
– Open a web browser and navigate to:
https://virtual_center_address/mob
– Click Content.
– Click ExtensionManager.
– Verify com.vmware.vadm is listed as an Extension.
– If listed, copy this string and click UnregisterExtension.
– Paste string into Value box and click Invoke Method.

If vCenter server on Microsoft OS, log in to the vCenter servers and find a similar path to:
C:\Program Files\VMware\Infrastructure\VirtualCenterServer\extensions\com.vmware.vadm
– Delete the entire com.vmware.vadm

Add the provider back in:
– Go back to vSphere
–  Right click the virtual machine from within the vSphere Desktop Client, select Edit Settings.
– Choose the vServices tab, click Edit. Under Provider select the one below No Provider.
– Click OK and then OK again.
– Turn the system back on and verify connection.

If not coming up then restart the vSphere web client service

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s