RecoverPoint: RP4VM plugin not displayed in vCenter

Summary: Dell RecoverPoint for Virtual Machines plugin is not displayed in vCenter.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Symptoms

RecoverPoint for Virtual Machines (RP4VM) Plugin is not displayed in the vCenter.
vCenter version 6.0 and 6.5 (All updates)

From vCenter virgo logs: vsphere_client_virgo_timestamp

2016-05-04T10:49:42.884+02:00] [ERROR] region-dm-11                  org.eclipse.virgo.medic.eventlog.default                         AG0000E Application context creation failure for bundle 'com.emc.recoverpoint.wssdkprovider' version '1.0.0'. org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'VmDataProvider': Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'VmDataProviderImpl' defined in URL [bundleentry://365.fwk248095206/META-INF/spring/bundle-context.xml]: Resolution of declared constructors on bean Class [com.emc.recoverpoint.wssdkprovider.VmDataProviderImpl] from ClassLoader [KernelBundleClassLoader: [bundle=com.emc.recoverpoint.wssdkprovider_1.0.0]] failed; nested exception is java.lang.NoClassDefFoundError: com/vmware/vim25/RuntimeFaultFaultMsg
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1455)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294)
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225)
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291)
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:589)
    at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:925)
    at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.access$1600(AbstractDelegatedExecutionApplicationContext.java:60)
    at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:325)
    at org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
    at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:290)
    at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:137)
    at org.eclipse.virgo.kernel.agent.dm.ContextPropagatingTaskExecutor$2.run(ContextPropagatingTaskExecutor.java:95)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:745

 

Cause

Another Plugin uses different version of vim25.jar and deploys it before RP.
Classloader uses the first vim25.jar that is deployed and RP Plugin fails to load.

 

Resolution

Workaround:
Find the plugin that uses vim25.jar and disable it from VC and restart the web client service.

To disable the plugin:
From the web client, Administration > Solutions > Client Plug-ins
Right click the plugin to disable and choose disable.

Once it is deployed and running, enable the other plugin.

Resolution:
Dell Technologies engineering is currently investigating this issue. A permanent fix is still in progress.
Contact the Dell Technologies Customer Support Center or your service representative for assistance and reference this solution ID.

 

Additional Information

Find additional information about vSphere Web Client Logs here.

 

Affected Products

RecoverPoint for Virtual Machines

Products

RecoverPoint, RecoverPoint for Virtual Machines
Article Properties
Article Number: 000170787
Article Type: Solution
Last Modified: 05 Mar 2026
Version:  5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.