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

vSphere Replication 6.1.2 plugin fails to load in vSphere Web Client (2149560)

  • 9 Ratings
Language Editions

Symptoms

  • vSphere Replication 6.1.2 plugin fails to load in to the vSphere Web Client.
  • You see entries similar to:

    [2017-03-06T10:17:39.693-10:00] [ERROR] vc-extensionmanager-pool-94 70000060 100005 200001 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.vcHms-6.1.2.605082273 com.vmware.vise.core.model.CompositeException: CompositeException
    Timed out waiting for bundle to start: Bundle: id:com.vmware.vr.client.vrservice, version:6.1.2.5082273, contextPath:plugins, location:/etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity
    [2017-03-09T00:30:02.243-08:00] [WARN ] region-dm-2 org.springframework.beans.factory.xml.XmlBeanDefinitionReader Ignored XML validation warning org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'http://www.springframework.org/schema/beans/spring-beans-4.3.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
    at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198)

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

Cause

This issue occurs because the vCenter Server can not access the http://www.springframework.org.

Resolution

This is a known issue affecting vSphere Replication 6.1.2.
 
Currently, there is no resolution.
 
To work around this issue:

Note: In an environment with VCs in LinkedMode, you must execute the steps in groups at different places respectively:

Group: 1

In all HMS (vSphere Replication) appliances:

    1. Unregister the vSphere Replication appliances if already registered to vCenter through VAMI page.
    2. Log into VAMI  https://vr-appliance-address:5480/.
    3. In the Configuration tab, click Unregister from vCenter Server.

  1. Download the 2149561_ngcplugin-60 file attached to this Knowledge Base article and rename it to ngcplugin-60.zip.
  2. Replace the existing ngcplugin-60.zip file with the downloaded plugin file to the following directory in the HMS appliance:

    /opt/vmware/share/htdocs/client/

Group: 2

In all the linked vCenter Servers:

  1. Remove the com.vmware.vcHms-6.1.2.605082273 downloaded plugin folder or any other files:

    Note: Remove any file prefixed with com.vmware.vcHms from this location.

    vCenter Server Appliance - /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com.vmware.vcHms-6.1.2.605082273

    To remove the downloaded com.vmware.vcHms-6.1.2.605082273 plugin folder in the vCenter Sever Appliance:

    1. Run this command to view the list of folders in the /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity location:

      bpvappvc1:/etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity # ls -l

      You see the output:

      total 8
      drwx------ 3 vsphere-client users 4096 Mar 2 10:49 com.vmware.vcDr-6.1.0.11034
      drwx------ 3 vsphere-client users 4096 Mar 3 15:13 com.vmware.vcHms-6.1.2.605082273

    2. Run this command to remove the downloaded com.vmware.vcHms-6.1.2.605082273 plugin folder or any other files:

      bpvappvc1:/etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity #rm -rf com.vmware.vcHms-6.1.2.605082273

    3. Verify that the com.vmware.vcHms-6.1.2.605082273 folder is removed by running this command:

      bpvappvc1:/etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity # ls -l

      You see the output similar to:

      total 7
      drwx------ 3 vsphere-client users 4096 Mar 2 10:49 com.vmware.vcDr-6.1.0.11034
      Windows vCenter Server - C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-packages\vsphere-client-serenity\com.vmware.vcHms 6.1.2.605082273


  2. Stop the service by running this command:

    service-control –-stop vsphere-client

    Windows vCenter Server: service-control --stop vspherewebclientsvc

  3. Clean the tomcat cache by removing all files and folders by running this command:

    /usr/lib/vmware-vsphere-client/server/work# rm -rf *

    Windows vCenter Server: C:\Program Files\VMware\vCenter Server\WebClient\server\work

    Open Command prompt for the C:\Program Files\VMware\vCenter Server\WebClient\server\work location and run the del *.* command.

    Note: Ensure that you run the #rm -rf or del *.* command only in the specified folder. If you run this command in the other folder, it may delete the content of that folder as well.

  4. Clear the serenity database by running this command:

    /storage/vsphere-client/SerenityDB/serenity# rm -rf *

    Windows vCenter Server: C:\programdata\vmware\vCenterServer\data\vSphere Web Client\SerenityDB\serenity

    Open Command prompt for the C:\programdata\vmware\vCenterServer\data\vSphere Web Client\SerenityDB\serenity location and run the del *.* command.

  5. Remove/rename the old hmsJARs in /usr/lib/vmware-virgo/server/pickup/.

    Files to be removed/renamed:

    hms-vmodl-6.1.2.5082273.jar
    topology-service-6.1.2.5082273.jar
    vr-service-6.1.2.5082273.jar
    vr-ui-war-6.1.2.5082273.war


    Command for VCSA: mv [hmsJARs] [hmsJARs.bak]

    Windows vCenter Server file location: C:\Program Files\VMware\vCenter Server\virgo\server\pickup\

  6. Remove/clear the contents from VCSA:

    /etc/vmware/vsphere-client/cmCatalog

    Windows vCenter: C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\cmCatalog

Group: 3

In all Linked vCenter Servers:
 
  1. Start the vSphere Client service by running this command (VCSA):

    service-control –-start vsphere-client

    Windows vCenter Server: service-control --start vspherewebclientsvc

Group: 4

On all vSphere Replication appliances:

  1. Register the vSphere Replication appliance again with vCenter Server from the VR appliance VAMI page.
    1. Log in to VAMI - https://vr-appliance-address:5480/.
    2. In the Configuration tab, click Register after entering the appropriate ls URL.

Group: 5

  1. In the SSO solutions and users section (Web-client), verify that the solution user are added back.
  2. Log out of the vSphere Web Client and the plugin should be visible. If the plugin is not visible, start the vSphere Client services again.

    service-control –-start vsphere-client

    Windows vCenter Server: service-control --start vspherewebclientsvc

Additional Information

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

Tags

vSphere Replication 6.1.2, Plugin, vSphere Web Client

See Also

Language Editions

ja,2150157;zh_cn,2150192

Attachments

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.

Feedback

  • 9 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.
  • 9 Ratings
Actions
KB: