Registering Site Recovery Manager with vCenter fails: Operation Failed A general system error occurred

Products

• VMware vCenter Server

Issue/Introduction

When attempting to register SRM with vCenter, the following error is presented: Operation Failed A general system error occurred

In the /var/log/vmware/dr/drconfig.log on the SRM appliance, you may see an error similar to the following: 

####-##-##T##:##:##.###Z error drconfig[03366] [SRM@6876 sub=ConfigureVrmsOp opID=71dd0b14-fb9e-482d-8818-3aed6af97fff-configure:8a91] command:
--> /usr/bin/python /opt/vmware/share/htdocs/service/hms/cgi/hms-dr.py --cmd saveembeddedconf --ls=https://VCENTER-FQDN:443/lookupservice/sdk --lspemfile=/opt/vmware/hms/conf/lsCert --ssoadmin=user@domain --vcip=VCENTER-FQDN --vcport=80 --vcthumbprint=<redacted>  --servername=VCNAME --hmshost=SRMNAME --hmsport=8043 --self-moid=unused [email protected] [email protected] --strict-certs 1
--> stdout:
--> {"error": "Error applying startup configuration: NOTE: Picked up JDK_JAVA_OPTIONS: --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED\nvSphere Replication Appliance configuration error:Unable to create solution user.\nDetails: Service account com.vmware.vr-sa-########-####-####-####-############ not found\n[ msgId: com.vmware.vr.config.unable_to_create_user; value: null; errorStacktrace :  ]\n\tat com.vmware.hms.config.helper.ServiceAccountHelper.createServiceAccount(ServiceAccountHelper.java:143)\n\tat com.vmware.hms.config.VrConfig.createServiceAccount(VrConfig.java:552)\n\tat com.vmware.hms.config.VrConfig.reconfigVr(VrConfig.java:505)\n\tat com.vmware.hms.config.VrConfig.expressSetup(VrConfig.java:345)\n\tat com.vmware.hms.config.cli.command.ExpressSetup.run(ExpressSetup.java:59)\n\tat com.vmware.hms.config.cli.command.CommandBase.run(CommandBase.java:347)\n\tat com.vmware.hms.config.cli.App.run(App.java:146)\n\tat com.vmware.hms.config.cli.App.main(App.java:206)\n"}
-->
--> stderr:
--> /usr/lib/python3.10/getpass.py:91: GetPassWarning: Can not control echo on the terminal.
-->   passwd = fallback_getpass(prompt, stream)
--> Warning: Password input may be echoed.
--> Enter ssopassword:
--> NOTE: Picked up JDK_JAVA_OPTIONS: --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
--> vSphere Replication Appliance configuration error:Unable to create solution user.
--> Details: Service account com.vmware.vr-sa-########-####-####-####-############ not found
--> [ msgId: com.vmware.vr.config.unable_to_create_user; value: null; errorStacktrace :  ]
-->     at com.vmware.hms.config.helper.ServiceAccountHelper.createServiceAccount(ServiceAccountHelper.java:143)
-->     at com.vmware.hms.config.VrConfig.createServiceAccount(VrConfig.java:552)
-->     at com.vmware.hms.config.VrConfig.reconfigVr(VrConfig.java:505)
-->     at com.vmware.hms.config.VrConfig.expressSetup(VrConfig.java:345)
-->     at com.vmware.hms.config.cli.command.ExpressSetup.run(ExpressSetup.java:59)
-->     at com.vmware.hms.config.cli.command.CommandBase.run(CommandBase.java:347)
-->     at com.vmware.hms.config.cli.App.run(App.java:146)
-->     at com.vmware.hms.config.cli.App.main(App.java:206)
-->

 

When listing out SSO services for the target vCenter Server, there will already be registrations for the SRM instance present:

com.vmware.vr.vrms
com.vmware.vcHms
vrUi
dpxa

 

Environment

vCenter Server 9.0
vSphere Replication 9.0

Cause

This is caused by a previoulsy registered instance of SRM.  

Resolution

Identify the service IDs for the previously registered instance of SRM and remove them using lstool.py

1. Using KB322196, list out the services currently registered with SSO

2. Locate the service IDs for the target SRM services to be removed.  Each service registration should look similar to the following:: 

Name: vrms-caa73e19-2417-4c94-bc2a-ca93a175c29f--########-####-####-####-############
Description: vSphere Replication
Service Product: com.vmware.cis
Service Type: com.vmware.vr.vrms
Service ID: caa73e19-2417-4c94-bc2a-ca93a175c29f
Site ID: default-first-site
Node ID: ########-####-####-####-############
Owner ID: com.vmware.vr-sa-########-####-####-####-############@vsphere.local

3. Using lstool.py, remove the target Service ID from SSO: 

/usr/lib/vmware-lookupsvc/tools/lstool.py unregister --url http://localhost:7090/lookupservice/sdk --id caa73e19-2417-4c94-bc2a-ca93a175c29f --user [email protected] --password '####'

4. Restart the vCenter Server services to complete the process:

service-control --stop --all && service-control --start --all

5. Attempt to register SRM with the target vCenter Server

Additional Information

Process to view the List of Services Registered with Single Sign-On