Search the VMware Knowledge Base (KB)
View by Article ID

NSX Plug-in does not appear in Web Client when ESXTOP plug-in installed (2145808)

  • 0 Ratings
Language Editions


After deployment of NSX and successful registration with vCenter Server, NSX plug-in does not appear in the vSphere Web Client.


This issue occurs due to the conflict between NSX plug-in and ESXTOP plug-in. NSX plug-in requires latest version of the spring framework while ESXTOP deploys Spring version 4.0.5 which is not compatible with NSX. If ESXTOP is deployed before NSX plug-in, NSX plug-in fails to install properly.

Note: This issue occurs with any plug-in which uses a spring version incompatible with NSX plug-in.


This issue is resolved in VMware NSX for vSphere 6.3.0, available at VMware Downloads.

To work around this issue if you do not want to upgrade, uninstall ESXTOP plug-in: 

Note: Ensure to take a backup or offline snapshot of the virtual machine before proceeding with the steps.
  1. Log in to the console of the vCenter Server virtual machine.
  2. Run these commands:

    • rm -R /usr/lib/vmware-vsphere-client/plugin-packages/esxtop-plugin
    • rm -R /usr/lib/vmware-vsphere-client/server/work

  3. Restart the vSphere Web client service by running this command:

    • service vsphere-client restart

  4. (optional): To confirm that plug-in is uninstalled, run this command:

    • tail -f /var/log/vmware/vsphere-client/logs/eventlog.log | grep esx

Additional Information

You experience these additional symptoms:

  • In the logs\vsphere_client_virgo.log file, you see entries similar to:

    [2016-06-01T17:18:42.685Z] [ERROR] vc-extensionmanager-pool-90  70000066 100005 200003 com.vmware.vise.extensionfw.impl.PackagesDeployer Error deploying one of more bundles for the plugin package /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com.vmware.vShieldManager- com.vmware.vise.core

    [2016-06-07T18:20:35.182Z] [ERROR] start-signalling-15 org.eclipse.virgo.medic.eventlog.default DE0006E Start failed for bundle 'com.vmware.vshield.ui.common.service' version '5.1.0'. org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'VsmInvoker' defined in URL [bundleentry://387.fwk1018231081/META-INF/spring/bundle-context.xml]: Cannot resolve reference to bean '&VsmRemotingClientExporterFB' while setting bean property 'vsmRemotingClientExporterFB'; nested exception is org.springframework.beans.factory.BeanIsNotAFactoryException: Bean named 'VsmRemotingClientExporterFB' must be of type [org.springframework.beans.factory.FactoryBean], but was actually of type [com.vmware.vshield.ui.accessframework.util.VsmRemotingClientExporterFactoryBean]

    Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

  • You can see that ESXTOP plug-in, available at Flings by VMware is installed and accessible successfully in the vSphere Web Client.

To be alerted when this article is updated, click to Subscribe to Document in the Action box.


NSX Plugin, ESXTOP plugin

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 0 Ratings