Introduction
You encounter an authentication failure in VMware Live Recovery (VLR) after performing a version upgrade. This issue typically appears when you attempt to re-pair sites or configure protection groups. The underlying cause is often an unsupported interoperability state between the vCenter Server and the recovery appliance, which prevents the acquisition of the required security tokens.
Symptoms
You see the following error in the VLR interface:
SRM Server cannot connect to Unknown Service at https:####:443/sms/sdk. Access to perform the operation was denied.
Your vmware-dr.log on the VLR appliance contains these entries:
SOAP request returned HTTP failure; , ####>), /pbm/sdk>, method: fetchResourceType; code: 500(Internal Server Error); fault: (vmodl.fault.SecurityError)msg = "Received SOAP response fault from [####, ####>), /pbm/sdk>]: fetchResourceType --> Error while fetching ActAsToken"N2Dr5Fault22PbmConnectionDownFault9ExceptionE(Fault cause: dr.fault.PbmConnectionDownFault)
VLR site pairing appears connected, but the error persists after recreating the site pair or restarting vCenter/VLR servers
vCenter Server 9.0.2
VMware Live Recovery 9.0.2
VMware Site Recovery Manager 9.0.2
Unsupported interoperability configuration, which breaks the SAML token delegation chain, causing the 'Error while fetching ActAsToken' when the appliance attempts to connect to the vCenter Storage Profile Service. From the VLR Site Pair summary page screenshot above, vCenter Server 9.0.2 is incompatible with VMware Live Recovery 9.0.2
Upgrade your VMware Live Recovery or SRM appliances to version 9.0.4 or 9.0.5 as required by your vCenter version: