Error: 'Http failure response for https://SRM-name/dr/requestHandlers/checkPscCredentials?mode=free: 500 In ternal Server Error' while pairing SRM with vCenter Server.

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

While configuring site part between SRM and vCenter, the below error message on configuration wizard.

Operation Failed
Insufficient permissions to perform this operation.
Operation ID: 029d59a9-2a55-xxxx-xxxx-0xxxxxxxx642'

The configure wizard shows the below error on UI.

Http failure response for https://####-vra.domain/dr/requestHandlers/checkPscCredentials?mode=free: 500 Internal Server Error

Ref: Screen below.

This can be validated on SRM server logs under path /opt/vmware/drconfigui/logs/dr-config.log

The event show as 'NotAuthorized' as below:

2025-02-07 12:06:56,599 [srm-reactive-thread-320] WARN  com.vmware.dr.configservice.taskMonitor.ConfigureTaskHandler 029
d59a9-2a55-4d8e-9f69-096e85ad9642 getConfigureTaskProgress - Task finished with error!
(drConfig.fault.NotAuthorized) {
   faultCause = null,
   faultMessage = null
}
        at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
        at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
        at java.base/java.lang.reflect.Constructor.newInstance(Unknown Source)
        at java.base/java.lang.Class.newInstance(Unknown Source)
        at com.vmware.vim.vmomi.core.types.impl.ComplexTypeImpl.newInstance(ComplexTypeImpl.java:174)
        at com.vmware.vim.vmomi.core.types.impl.DefaultDataObjectFactory.newDataObject(DefaultDataObjectFactory.java:25)

Environment

VMware Site Recovery Manager 8.x

Cause

Errors are due to the STALE entries on old SRM server on vCenter server.

Resolution

Remove the STALE entries of SRM server on vCenter server to fix the issue. The 

The below article has the instructions on cleaning up stale entries.

Cleaning up decommissioned SRM registration from vCenter Server