Configuring VM replication does not list target sites. Error "mor"
search cancel

Configuring VM replication does not list target sites. Error "mor"

book

Article ID: 334257

calendar_today

Updated On:

Products

VMware Live Recovery VMware vSphere ESXi

Issue/Introduction

Symptoms:

  • Configuring replication for any of the VMs in vCenter does not list target site. Target site reports the validation error: 'mor'
  • vSphere Replication status, target sites are in enabled and connected state respectively
  • Under target sites, there is reference to additional target site in unknown state.
  • In the /var/log/vmware/vsphere-client/logs/vsphere_client_virgo.log file, you see entries similar to:
[2018-01-10T21:25:06.309Z] [ERROR] data-service-pool-800        
70087483 105096 204527 com.vmware.vr.data.AbstractDataServiceAdapter                     Error while extracting property 'connectionStatus' for item ManagedObjectReference: type = HmsRemoteHmsServer, value = HMSSRV-########-####-####-####-########49e5, serverGuid = ########-####-####-####-########bfbe. Will be added to the result set. java.lang.IllegalArgumentException: mor
        at com.vmware.vr.client.topology.impl.VmodlService.createStub(VmodlService.java:170)
        at sun.reflect.GeneratedMethodAccessor546.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at com.vmware.vr.client.topology.impl.serviceManagement.Registry$ServiceProxy.invoke(Registry.java:100)
        at com.vmware.vr.client.topology.services.HmsService$$EnhancerByCGLIB$$732aa2db.createStub(<generated>)
        at com.vmware.vr.provider.target.sites.VcSitePropertyResolver.getConnectionStatus(VcSitePropertyResolver.java:159)
        at sun.reflect.GeneratedMethodAccessor5483.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at com.vmware.vr.data.PropertyReactor.getProperty(PropertyReactor.java:165)
        at com.vmware.vr.data.AbstractDataServiceAdapter.resolveProperties(AbstractDataServiceAdapter.java:173)
        at com.vmware.vr.data.DataProviderBase.handleQuery(DataProviderBase.java:278)
        at com.vmware.vr.data.DataProviderBase.getData(DataProviderBase.java:129)
        at com.vmware.vise.data.query.impl.DataAdapterUtil.getDataFromAdapter(DataAdapterUtil.java:218)
at com.vmware.vise.data.query.impl.DataAdapterUtil.getResultFromAdapter(DataAdapterUtil.java:175)
at com.vmware.vise.data.query.impl.DataAdapterUtil.access$000(DataAdapterUtil.java:42)
at com.vmware.vise.data.query.impl.DataAdapterUtil$1.call(DataAdapterUtil.java:81)
at com.vmware.vise.data.query.impl.DataAdapterUtil$1.call(DataAdapterUtil.java:78)
 at com.vmware.vise.util.concurrent.ExecutorUtil$2.call(ExecutorUtil.java:693)
 at com.vmware.vise.util.concurrent.ExecutorUtil$ThreadContextPropagatingTask.call(ExecutorUtil.java:1060)
 at com.vmware.vise.data.query.impl.DataServiceThreadPoolDecorator$1.call(DataServiceThreadPoolDecorator.java:167)
 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
 at java.lang.Thread.run(Thread.java:748)

[2018-01-10T21:25:06.333Z] [WARN ] data-service-pool-800        70087483 105096 204527 com.vmware.vr.data.DataProviderBase                               Adding item with exceptions to query 'dam-auto-generated: DamAdapter:dr-103': ConstraintResult(4 items / 4 total, 1 errors)
[2018-01-10T21:25:06.334Z] [WARN ] data-service-pool-800        70087483 105096 204527 com.vmware.vr.data.ConstraintResult                               1 exceptions registered, will return only the first: [java.lang.IllegalArgumentException: mor]

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

 

Cause

This issue occurs because there are vSphere Replication appliances listed in unknown state under target sites.

Resolution

To resolve this issue, ensure all connections under vSphere Replication target sites are valid and are in connected state.

  1. Login to the web client and go to vSphere Replication > Manage/Configure >Target sites.
  2. In the list of target sites, ensure that you do not have any connections in unknown state.
  3. If there are sites listed in unknown state, right click and choose Disconnect local site only to disconnect. 

Note: To enable replication between the two sites again, you must configure a new connection.

Additional Information

Impact/Risks:
Replication cannot be configured for any virtual machines using web client.