Search the VMware Knowledge Base (KB)
View by Article ID

vCenter Server addresses are not listed as possible targets when installing Site Recovery Manager (2145520)

  • 2 Ratings


  • Site Recovery Manager does not display valid vCenter Server addresses in the vCenter Server Address drop down.
  • In the %temp%\VMSrmInst.log file, you see entries similar to:

    VMware: Srm::Installation::XmlFileHandler::GetElementMap: INFORMATION: Inserted key 'vCenter_FQDN' and value 'default-first-site:UUID'
    VMware: Srm::Installation::XmlFileHandler::GetElementMap: ERROR: Duplicate key 'vCenter_FQDN' exists

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


To work around the issue, remove the invalid vCenter Server registrations.


This issue occurs if there are duplicate vCenter Server entries in the environment due to multiple service registrations of one vCenter Server with different versions.


This is a known issue affecting Site Recovery Manager 6.0 and 6.1.

Currently, there is no resolution.

To work around the issue, remove the invalid vCenter Server registrations.
  1. Ensure no 5.x vCenter Servers are referencing the PSC. Repoint these vCenter Servers to an alternate SSO.  For more information, see Re-pointing and re-registering VMware vCenter Server 5.1 / 5.5 and components (2033620).

  2. Find the service registrations of your vCenter Server identified on the Platform Services Controller 6.0 by running this command on the Platform Services Controller 6.0 instances:

    Windows PSC:

    "%VMWARE_PYTHON_BIN%" "%VMWARE_CIS_HOME%\VMware Identity Services\lstool\scripts\" list --url http://localhost:7080/lookupservice/sdk --type vcenterserver 

    Appliance PSC:
    /usr/lib/vmidentity/tools/scripts/ list --url http://localhost:7080/lookupservice/sdk --type vcenterserver For Example:

    Service Product: com.vmware.cis
    Service Type: vcenterserver
    Service ID: 569984f0-0a7d-4a5f-9b57-8a0e7e04406f
    Site ID: default-prot-site
    Node ID: caad08a0-1cfd-11e6-bdb2-0050560121b6
    Owner ID: vpxd-be1aa660-1cfd-11e6-a897-0050560121b6@vsphere.local
    Version: 6.0
    Type: com.vmware.cis.workflow
    Protocol: vapi.json.http
    URL: http://vCenter_FQDN:8088/workflow/vapi
    SSL trust: <Long string>

    The Service ID is: 569984f0-0a7d-4a5f-9b57-8a0e7e04406f

  3. Remove all service registrations with this command for each Service ID found in step 2:

    Windows PSC:

    "%VMWARE_PYTHON_BIN%" "%VMWARE_CIS_HOME%\VMware Identity Services\lstool\scripts\" unregister --url http://localhost:7080/lookupservice/sdk --user administrator@vsphere.local --password password --id Service_ID --no-check-cert

    Appliance PSC:

    /usr/lib/vmidentity/tools/scripts/ unregister --url 'http://localhost:7080/lookupservice/sdk' --user "administrator@vsphere.local" --password 'password' --id 'Service_ID' --no-check-cert

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 2 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 2 Ratings