Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Site Recovery Manager 8.3 Plugin does not show up in vCenter web client flash or HTML when vCenter 6.5/6.7 is installed on Windows Server (78678)

Last Updated: 5/25/2020Categories: InformationalTotal Views: 13492Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

SRM 8.3 has been installed or upgraded and registered with vCenter Server 6.5/6.7 installed on windows server does not load the plugin in the web client Flash or HTML

Error seen in vsphere_client_virgo.log is as below:

{Note: SRM client has been rename as 'draasclientplugin' from 8.3}

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'lookupServiceConnectionImpl' defined in URL [bundleentry://393.fwk1909761420/META-INF/spring/bundle-context.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.vmware.draasclientplugin.ls.LookupLookupServiceConnection]: Constructor threw exception; nested exception is java.lang.ExceptionInInitializerError

at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:279)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1201)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1103)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:513)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483)

at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:312)

at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)

at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:308)

at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)

at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:351)

... 43 common frames omitted

Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.vmware.draasclientplugin.ls.LookupLookupServiceConnection]: Constructor threw exception; nested exception is java.lang.ExceptionInInitializerError

at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:154)

at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:122)

at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:271)

... 52 common frames omitted

Caused by: java.lang.ExceptionInInitializerError: null

at com.vmware.af.VmAfClient.getLSLocation(VmAfClient.java:73)

at com.vmware.draasclientplugin.configuration.DevelopmentModeConfiguration.getLookupServiceUrl(DevelopmentModeConfiguration.java:55)

at com.vmware.draasclientplugin.ls.LookupLookupServiceConnection.createLsService(LookupLookupServiceConnection.java:77)

at com.vmware.draasclientplugin.ls.LookupLookupServiceConnection.<init>(LookupLookupServiceConnection.java:55)

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

at java.lang.reflect.Constructor.newInstance(Constructor.java:423)

at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:142)

... 54 common frames omitted

Caused by: java.lang.IllegalStateException: Only Linux is supported

at com.vmware.af.interop.NativeAdapter.<clinit>(NativeAdapter.java:52)

... 63 common frames omitted

Cause

The current plugin package does not work with Windows and only works with linux distributions so does not effect if vCenter is deployed as an appliance

Resolution

Download and replace the ngcplugin.zip (attached to this KB) for windows and appliance:

Windows SRM:
Download ngcplugin.zip, put zip file to this directory, overwrite the existed one
C:\ProgramData\VMware\VMware vCenter Site Recovery Manager\runtime\srm-client\webapps\drplugin

Appliance SRM:
Download ngcplugin.zip, put zip file to this directory, overwrite the existed one and change the file permission

/opt/vmware/dr-client/webapps/plugin

Change the file permission:
In srmva, switch to root user

cd /opt/vmware/dr-client/webapps/plugin
chown tomcat:tomcat ngcplugin.zip
chmod 670 ngcplugin.zip

Note: The file permission should be : -rw-rwx--- 1 tomcat tomcat 1780686 Apr 30 11:38 ngcplugin.zip

If only vSphere Replication is being used

Download ngcplugin.zip, put zip file to this directory, overwrite the existed one and change the file permission
/opt/vmware/share/htdocs/client

Change the file permission:
chmod 644 ngcplugin.zip

The file permission should be : -rw-r--r-- 1 root root 1780686 May 7 04:49 ngcplugin.zip

Once the above steps are completed, stop the vSphere webclient and UI services:

C:\Program Files\VMware\vCenter Server\bin
service-control --stop vsphere-client
service-control --stop vsphere-ui

Clear vsphere-client/vsphere-ui cache files:

clean com.vmware.vrUi-* file under following directory
C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\cm-service-packages\com.vmware.cis.vsphereclient.plugin
C:\ProgramData\VMware\vCenterServer\cfg\vsphere-ui\cm-service-packages\com.vmware.cis.vsphereclient.plugin

clear files under
C:\ProgramData\VMware\vCenterServer\runtime\vsphere-client\server\work
C:\ProgramData\VMware\vCenterServer\runtime\vsphere-ui\server\work

clear *draasclientplugin under
C:\ProgramData\VMware\vCenterServer\runtime\vsphere-client\server\configuration\work\Catalina\localhost

C:\ProgramData\VMware\vCenterServer\runtime\vsphere-ui\server\configuration\work\Catalina\localhost

check:
find / -name '*vrUi*'
find / -name '*draas*'
delete additional directories if such exist

Start the vSphere webclient and UI services:

C:\Program Files\VMware\vCenter Server\bin
service-control --start vsphere-client
service-control --start vsphere-ui

Logout vsphere-client/vsphere-ui and login again

Workaround

SRM UI can be accessed directly using plugin URL : https://srm-or-vr-ip/dr

Note: If custom port is used on Widows SRM for the Client Plugin then do specify the custom port in the URL (default is 443 and need not be specified) - https://srm-or-vr-ip:port/dr

Example:

With default - https://192.168.1.10/dr

With Custom - https://192.168.1.10:444/dr

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

ngcplugin

Additional Resources

KB
•
VMware 对 CVE-2020-1967 的响应：SSL_check_chain 中的 OpenSSL 1.1.1 分段故障（CVE-2020-1967） (78763)

KB
•
VMware の CVE-2020-1967 への対応SSL_check_chain での OpenSSL 1.1.1 のセグメンテーション エラー (CVE-2020-1967) (78763)

KB
•
在升级到 vRealize Log Insight 8.x 之后，主机名将恢复为 "localhost" (78761)

KB
•
ドメイン ユーザーが vRealize Log Insight 8.x でアラート クエリをフィルタリングできない (78784)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Site Recovery Manager

Related Versions:

VMware Site Recovery Manager 8.3.x

Take Our Survey

Support Assistant