Operational Defect Database
BugZero updated this defect 48 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 93194
Failed to register VRMS - Unable to locate VM with address XYZ into the vCenter Server inventory
Last update date:
4/1/2024
Affected products:
vSphere Replication
Affected releases:
8.x
Fixed releases:
No fixed releases provided.
Description:
Symptoms
VRMS registration fails displaying the error – ERROROperation FailedA general system error occurred: Failed to register VRMS.Operation ID: 893c3452-878b-4677-88f7-f50e8d3fd5d02/17/23, 10:06:20 AM -0500/var/log/vmware/dr/drconfig.log: 2023-03-22T09:45:19.188-04:00 info drconfig[01296] [SRM@6876 sub=DrConfigConfigurationManager opID=2e2844dc-6da8-4fb8-bfab-429ca4fdcf87-configure:c6cc] ConfigureVRMS: Starting configuration task--> {"error": "vSphere Replication Appliance configuration error:Invalid argument: applianceAddress.\nDetails: Unable to locate VM with address VRMSPR into the vCenter Server inventory.\n[ msgId: com.vmware.vr.config.illegal_arguments; value: [applianceAddress]; errorStacktrace : ]\n\tat com.vmware.hms.config.vix.VixRemoteExecutor.findHmsVm(VixRemoteExecutor.java:611)\n\tat com.vmware.hms.config.cli.command.CommandBase.findHmsVm(CommandBase.java:195)\n\tat com.vmware.hms.config.cli.command.CommandBase.run(CommandBase.java:278)\n\tat com.vmware.hms.config.cli.App.run(App.java:152)\n\tat com.vmware.hms.config.cli.App.main(App.java:212)\n"}-->--> stderr:--> /usr/lib/python3.7/getpass.py:91: GetPassWarning: Cannot control echo on the terminal.--> passwd = fallback_getpass(prompt, stream)--> Warning: Password input may be echoed.--> Enter ssopassword:--> vSphere Replication Appliance configuration error:Invalid argument: applianceAddress.--> Details: Unable to locate VM with address VRMSPR into the vCenter Server inventory.--> [ msgId: com.vmware.vr.config.illegal_arguments; value: [applianceAddress]; errorStacktrace : ]--> at com.vmware.hms.config.vix.VixRemoteExecutor.findHmsVm(VixRemoteExecutor.java:611)--> at com.vmware.hms.config.cli.command.CommandBase.findHmsVm(CommandBase.java:195)--> at com.vmware.hms.config.cli.command.CommandBase.run(CommandBase.java:278)--> at com.vmware.hms.config.cli.App.run(App.java:152)--> at com.vmware.hms.config.cli.App.main(App.java:212)-->--> Traceback (most recent call last):--> File "/opt/vmware/share/htdocs/service/hms/cgi/hms-dr.py", line 55, in main--> response['result'] = cmd.run()--> File "/opt/vmware/share/htdocs/service/hms/cgi/commands.py", line 786, in run--> return self.command.run()--> File "/opt/vmware/share/htdocs/service/hms/cgi/commands.py", line 1142, in run--> self.reconfigureHms(passDbProperties)--> File "/opt/vmware/share/htdocs/service/hms/cgi/commands.py", line 832, in reconfigureHms--> commands.execute(cmd, 'auto', __HMS_HOME__)--> File "/opt/vmware/share/htdocs/service/hms/cgi/commands.py", line 339, in execute--> raise Exception(output[1])--> Exception: vSphere Replication Appliance configuration error:Invalid argument: applianceAddress.--> Details: Unable to locate VM with address VRMSPR into the vCenter Server inventory.--> [ msgId: com.vmware.vr.config.illegal_arguments; value: [applianceAddress]; errorStacktrace : ]--> at com.vmware.hms.config.vix.VixRemoteExecutor.findHmsVm(VixRemoteExecutor.java:611)--> at com.vmware.hms.config.cli.command.CommandBase.findHmsVm(CommandBase.java:195)--> at com.vmware.hms.config.cli.command.CommandBase.run(CommandBase.java:278)--> at com.vmware.hms.config.cli.App.run(App.java:152)--> at com.vmware.hms.config.cli.App.main(App.java:212)--> 2023-03-24T10:56:07.496-04:00 info drconfig[01061] [SRM@6876 sub=ConfigureVrmsOp opID=bbf503f4-f040-4806-bd6e-3d22d2cac961-configure:35a0] Exiting ConfigureVrms2023-03-24T10:56:07.496-04:00 error drconfig[01061] [SRM@6876 sub=ConfigureVrmsOp opID=bbf503f4-f040-4806-bd6e-3d22d2cac961-configure:35a0] Operation failed--> (vmodl.fault.SystemError) {--> faultCause = (vmodl.MethodFault) null,--> faultMessage = <unset>--> reason = "Failed to register VRMS."--> msg = ""
Cause
1. vSphere replication appliance cannot be registered to a different vCenter than the one its deployed under because of vService binding/dependency between the vSphere replication appliance OVF and vService Manager in vCenter. 2. This error can also occur when the replication appliance hostname is set to shortname but you are registering using FQDN.
Resolution
1. Deploy the replication appliance in the same vCenter you want to register with. 2. Check and update the hostname from shortname to FQDN.
Related Information
Photon Network Manager Commands to update Hostname/IP Address/DNS in SRM & vSphere replication (92586) - https://kb.vmware.com/s/article/92586
