Live Recovery Activation Fails with “Could not register SRM deployment pair” Due to Missing HMS Permissions
search cancel

Live Recovery Activation Fails with “Could not register SRM deployment pair” Due to Missing HMS Permissions

book

Article ID: 420534

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

Error in the GUI:
"Could not register SRM deployment pair"


Will see errors similar to this in the logs:
[2025-09-03 13:24:32.203 UTC] [dpx-agent] WARN  [vcId='NA' host='vlsrFQDN.com'] [thread='dpx-common-thread1040'] [email protected] - Failed to connect to HMS@1086305220.
java.util.concurrent.CompletionException: (vim.fault.NoPermission) {
   faultCause = null,
   faultMessage = null,
   object = ManagedObjectReference: type = HmsRemoteSiteManager, value = site-manager, serverGuid = 7c793dab-1346-4dbf-b866-##########,
   privilegeId = HmsRemote.com.vmware.vcHms.Hms.View,
   missingPrivileges = (vim.fault.EntityPrivileges) [
      (vim.fault.EntityPrivileges) {
         dynamicType = null,
         dynamicProperty = null,
         entity = ManagedObjectReference: type = HmsRemoteSiteManager, value = site-manager, serverGuid = 7c793dab-1346-4dbf-b866-##########,
         privilegeIds = (STRING) [
            HmsRemote.com.vmware.vcHms.Hms.View


[2025-09-03 13:24:32.204 UTC] [dpx-agent] WARN  [vcId='NA' host='wpcdv1-w1-vlsr.wpc.ntrs.com'] [thread='dpx-schedule-thread0'] com.vmware.atlas.agent.srm.entitlement.topology.ServerTopology - Unable to retrieve peers for Hms LsppService{_id='7c793dab-1346-4dbf-b866-##########', _serviceVersion='9.0.2.17860', _serviceNameDefault='vrms-7c793dab-1346-4dbf-b866-##########--f021e2bd-e5de-4dad-95e2-##########', _serviceNameResourceKey='', _serviceDescriptionResourceKey='', _siteId='default-first-site', _nodeId='6032e830-cab1-11ea-bfb8-##########', _ownerId='com.vmware.vr-sa-7c793dab-1346-4dbf-b866-##########@vsphere.local', _product='com.vmware.cis', _type='com.vmware.vr.vrms', _endpoints=[LsppServiceEndpoint{type='com.vmware.vim.hms', protocol='vmomi', url=https://vlsrFQDN.com:8043}, LsppServiceEndpoint{type='com.vmware.hms.health', protocol='rest', url=https://vlsrFQDN.com:5480/configureserver/health/hms}], _attributeValueByKey={solution_username=com.vmware.vr-sa-7c793dab-1346-4dbf-b866-##########, domainType=, supported_vmodl_versions=https://vlsrFQDN.com:8043/versions/hms-supported-versions.xml, config_url=http://vlsrFQDN.com/, domainName=vsphere.local, sitename=test.com, build_number=24383568, vc_proxy_port=80, vc_uuid=f021e2bd-e5de-4dad-95e2-##########, domainId=4c33bcf9-7add-4768-bd5b-##########}}.
com.vmware.vim.binding.vim.fault.NoPermission: Permission to perform this operation was denied.

Environment

 

  • VMware SRM / VLSR

  • Cloud Console site-pair activation workflow

 

Cause

HmsDpxAgentUsers permissions missing in vCenter.
The logs shows repeated vim.fault.NoPermission errors indicating the missing HmsRemote.com.vmware.vcHms.Hms.View privilege on the HmsRemoteSiteManager object.
This prevents HMS from retrieving topology information and blocks SRM deployment pair registration.

Resolution

To resolve the SRM site-pair activation failure, restore the missing HMS permissions by assigning the HmsDpxAgentUsers role in vCenter and ensuring the permissions propagate correctly.

1. Identify the Affected vCenter

Confirm which vCenter Server is associated with the VLSR/HMS instance that generated the NoPermission errors.

2. Log in to the vSphere Client

  1. Open the vSphere Client (HTML5).

  2. Log in with an account that has Administrator or equivalent privileges.

3. Navigate to the vCenter Permissions

  1. In the vSphere Client, select the vCenter Server object.

  2. Go to Menu > Administration.

  3. Under Access Control, click Permissions.

4. Add the HmsDpxAgentUsers Role

  1. Click Add.

  2. Select the appropriate vSphere.local.

  3. From the Assigned Role drop down, choose HmsDpxAgentUsers.

    • If the role does not exist, verify that HMS components were registered correctly or manually recreate the role based on required HMS privileges (including Hms.View).

5. Enable Permission Propagation

  1. Ensure Propagate to children is checked.
    This ensures the permissions apply to the objects required by HMS, including HmsRemoteSiteManager and related service endpoints.

6. Verify HMS Registration and Connectivity

  1. On the VLSR appliance UI or via logs, confirm HMS services are healthy.

  2. Check for any subsequent NoPermission errors in:

    • /var/log/dpx/dpx-agent.log

7. Retry the SRM Deployment Pair Activation

Return to the Cloud Console and retry Activate Site Pair.
If permissions are correctly applied, the SRM deployment pair should register successfully without generating HMS or DPX permission errors.

Powered by Wolken Software