Failed to find a vCenter Server from %s.

[dbutch1976]

Hello,

I have a single platform services controller called psc.itdemoguy.ca and two vCenters called vcprod1.itdemoguy.ca and drvc1.itdemoguy.ca.  I have a single SSO domain called itdemoguy.local.  Both vCenters have been added as target sites for each other, VR appliances have been deployed and configured, and I have some VMs being replicated across the sites.

I am getting the attached error attempting to install SRM immediately after entering the information for my platform services controller.  I suspect that this error is due to the fact that I have two vCenters connecting to a single Platform Services controller, however I believe this configuration is a supported practice.

Any suggestions as to what I could try?

Thanks.

[Daniel_Georgiev]

Hello,

you can check the actual error in installation temp file - %Temp%\VMSrmInst and  which can help to identify the real reason for failure. You can check the user that is used for authentication is SSO admin user or user that has enough privileges to install SRM - administrator@itdemoguy.local and you can try with administrator@vsphere.local also.

Hope this help,

Daniel G.

[admin]

I encountered this error message and the reason was that the lookup service had duplicate service registrations for the same vcenter server instance. The VMSrmInst.log should confirm if this is the case - check for "Found a VC, dumping endpoints" and see if there are any duplicates.

We were able to remove the additional entry (which actually related to an earlier vcenter server version) to resolve.

It should be supported to use a shared PSC:

Site Recovery Manager 6.0 Documentation Center

[dbutch1976]

You're definitely onto something p_hall:

I see the 'dumping endpoints' entry in the log, however, because I have two virtual centers connected to a single Platform Services Control BOTH of the results that are being returned are correct:

VCPROD1.itdemoguy.ca

DRVC1.itdemoguy.ca

I believe there is a bug in the SRM installer, correct me if I'm wrong, but if two vCenters are connected to the same PSC (supported) then I should be able to pick which one I want to install SRM on, is that right?

Thanks.

Here is the relevant portion of the log:

2015-10-27T09:28:01.431-04:00 info -[03012] [Originator@6876 sub=Default] Connecting to LS at 'https://psc.itdemoguy.ca:443/lookupservice/sdk'

2015-10-27T09:28:01.430-04:00 info -[03436] [Originator@6876 sub=ThreadPool] Thread enlisted

2015-10-27T09:28:01.430-04:00 info -[03220] [Originator@6876 sub=ThreadPool] Thread enlisted

2015-10-27T09:28:01.467-04:00 info -[03012] [Originator@6876 sub=Default] Successfully established authenticated connection to Lookup Service

2015-10-27T09:28:01.488-04:00 info -[03012] [Originator@6876 sub=Default] Found 2 service(s) in LS.  Scanning for VCs...

2015-10-27T09:28:01.488-04:00 info -[03012] [Originator@6876 sub=Default] Found a VC, dumping endpoints...

2015-10-27T09:28:01.488-04:00 info -[03012] [Originator@6876 sub=Default] Found a VC, dumping endpoints...

<?xml version="1.0" encoding="UTF-8"?>
<SrmConfigInfo>
  <ServiceInfo>
    <Url>https://VCPROD1.itdemoguy.ca:443/sdk</Url>
    <Address>vcprod1.itdemoguy.ca</Address>
    <Port>443</Port>
    <ServiceId>dc67ee7a-ec54-4825-a1a1-5529021ce00e</ServiceId>
    <NodeId>cf20ca96-7732-11e5-b3fe-000c29bc43f2</NodeId>
    <ProductVersion>6.0</ProductVersion>
  </ServiceInfo>
  <ServiceInfo>
    <Url>https://DRVC1.itdemoguy.ca:443/sdk</Url>
    <Address>drvc1.itdemoguy.ca</Address>
    <Port>443</Port>
    <ServiceId>7a99dc23-5060-4770-8b14-a256990d2ce4</ServiceId>
    <NodeId>56ab9bae-7741-11e5-bd70-000c297605f3</NodeId>
    <ProductVersion>6.0</ProductVersion>
  </ServiceInfo>
</SrmConfigInfo>Command executed successfully.

2015-10-27T09:28:01.490-04:00 info -[03436] [Originator@6876 sub=ThreadPool] Thread delisted

2015-10-27T09:28:01.490-04:00 info -[03220] [Originator@6876 sub=ThreadPool] Thread delisted

2015-10-27T09:28:01.490-04:00 info -[02580] [Originator@6876 sub=ThreadPool] Thread delisted

2015-10-27T09:28:01.490-04:00 info -[05404] [Originator@6876 sub=ThreadPool] Thread delisted

VMware: Srm::Installation::Utility::LaunchApplication: INFORMATION: Child process stderr:

VMware: Srm::Installation::Utility::LaunchApplication: INFORMATION: Executable finished executing. Result code=0
VMware: Srm::Installation::CisRegistration::Execute: INFORMATION: Execute returned: 0
VMware: Srm::Installation::CisRegistration::Execute: INFORMATION: Execute command completed successfully.
VMware: Srm::Installation::XmlFileHandler::XmlFileHandler: INFORMATION: Opened XML file: C:\Users\DBUTCH~1.ITD\AppData\Local\Temp\2\dr1445952481
VMware: Srm::Installation::XmlFileHandler::GetElementMap: INFORMATION: Inserted key 'vcprod1.itdemoguy.ca' and value 'dc67ee7a-ec54-4825-a1a1-5529021ce00e'
VMware: Srm::Installation::XmlFileHandler::GetElementMap: INFORMATION: Inserted key 'drvc1.itdemoguy.ca' and value '7a99dc23-5060-4770-8b14-a256990d2ce4'
VMware: Srm::Installation::Utility::ParseListFromResponseFile: INFORMATION: Map returned from xml parsing.
VMware: Srm::Installation::XmlFileHandler::~XmlFileHandler: INFORMATION: Done handling XML file: C:\Users\DBUTCH~1.ITD\AppData\Local\Temp\2\dr1445952481
VMware: Srm::Installation::XmlFileHandler::XmlFileHandler: INFORMATION: Opened XML file: C:\Users\DBUTCH~1.ITD\AppData\Local\Temp\2\dr1445952481
VMware: Srm::Installation::XmlFileHandler::GetElementMap: INFORMATION: Inserted key 'vcprod1.itdemoguy.ca' and value '6.0'
VMware: Srm::Installation::XmlFileHandler::GetElementMap: INFORMATION: Inserted key 'drvc1.itdemoguy.ca' and value '6.0'
VMware: Srm::Installation::Utility::ParseListFromResponseFile: INFORMATION: Map returned from xml parsing.
VMware: Srm::Installation::XmlFileHandler::~XmlFileHandler: INFORMATION: Done handling XML file: C:\Users\DBUTCH~1.ITD\AppData\Local\Temp\2\dr1445952481
VMware: Srm::Installation::VMPopulateVcCombo: ERROR: Failed to populate VC list, no valid VC instances found.
VMware: Srm::Installation::Utility::GetMsgFromErrorTable: INFORMATION: Error message is Failed to find a vCenter Server from %s.

[admin]

This seems to be different to my case, and to another case I found with the same error. In both those cases, there were duplicate entries found - the lookup service returned two entries with identical url/address values, and that was the problem. Returning multiple vcenter instances should not in itself be a problem.

Is it possible there is a version mismatch? If you were installing SRM 6.1, you would need vCenters to be at 6.0 Update 1.

[SteveAntle]

Hello,

This website solved it for me: vB3N: Remove orphaned vCenter from PSC

I had a stale vCenter Server entry in the PSC that was causing the SRM installer to throw the same error in the install log as you were seeing.

Hope this helps!

Steve

[jrfranco2016]

hello SteveAntle the article that you mention in the URL I can not open it you could tell me some other link where you can see how you solved this problem

[curciricardo]

Hello,

I had the same type problem for install SRM 6.1 and show print bellow:

In case, it were executed the kbs bellow, but I didn't succeed:

VMware Knowledge Base

VMware Knowledge Base

VMware Knowledge Base

Could any help me about it?

Tks.

[Jitu211003 · Accepted solution]

Hi,

The error indicates that you are using an unsupported SRM.

Go through the compatibility matrix of Vmware and make sure your Vcenter version is support with SRM version.

Thanks

Vmwarediary.com

[MarkCains]

Every time I have seen this issue regardless of the versions of vCenter or Site Recovery Manager I have been able to delete the main entry for VMware Site Recovery Manager under HKLM - Software - Vmware, Inc. Once I have done this I was able to go back to the Programs Features in the Windows Server and uninstall successfully. I hope this helps!

[dbutch1976]

Got this error today.  I was relieved to find out that I was not the only person experiencing this issue, until I realized that the Original Poster was ME ALMOST THREE YEARS AGO!  Many versions later, presently running vsphere 6.7 and attempting to install srm 6.1.2.  Could just about scream.  Here's what I've tried so far:

Blown away my entire environment.  Reinstalled two PSC's and VC's.

Two Platform service controllers (not the all in one appliance)

Same SSO domain vsphere.local

Same site default-site

Two Virtual center appliances.

Everything is up and running okay, I did not receive any errors during install.  I have started from scratch several times, I have used both DHCP and static IP assignments during the install.  My A records and PTR records are resolving correctly. 

For troubleshooting I have tried:

Turning IE enhanced security off.

Adding all certificates to the trusted CA on the server I am attempting to install SRM to the local certificate store.  (All ESXi hosts, all vcenters, all platform services controllers.  I get zero certificate warnings)

I have turned UAC off.

Server is fully patched (Windows 2012R2).

Ran installer as local admin.

Finally I found that my issue was in fact being caused because my installer may not be compatible with my version of vsphere.  After downloading the most recent version of srm 8.1.0 the issue stopped occurring.

I would recommend anyone having this refer to the compatibility matrix:

VMware Site Recovery Manager

Best of luck to anyone else wrestling with this beast!

[GoggiP]

Hi All,

This is not always the case.  In my setup I had the issue where I managed to upgrade to 6.1.1.1 on DR site and on Prod Site I was not able to upgrade 6.1.1.1.  Luckily after much deep thought:) we had an intermediate patch 6.1.1 for SRM and were able to upgrade successfully.

Hope this helps someone.

Best regards,

Paul.