SRM services fails to start during SRM Registration

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

• SRM Registration is completed successfully, but service are in stopped state,
  
  
• SRM VAMI shows below error under certificates.
  
  

Environment

VMware vSphere Replication 8.x
VMware vSphere Replication 9.x
VMware Site Recovery Manager 8.x
VMware Live Site Recovery 9.x

Cause

The issue is caused by incorrect/short FQDN updated for Site Recovery manager. The FQDN is essential for certificate, hence short names are not allowed. The Hostname with short FQDN fails to resolve DNS. 

• Host Name displays short name,
  
  

• Below Logs displays error,
  
  /var/log/vmware/drconfigui/drconfig.log:
  
  2025-06-04T20:02:52.180Z verbose drconfig[00774] [SRM@6876 sub=Default.SiteConnections opID=bd06a10d-bf5c-4193-81ab-8da29cd4509d-isReconfigureRequired] SiteConnections created for 'https://###.##.##.##:443/lookupservice/sdk' with thumbprint'##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:DE:B4:77:AA:72:94:B9:1D:C5:19:54:78:55:96:FF:A1:FB'
2025-06-04T20:02:52.184Z verbose drconfig[00774] [SRM@6876 sub=vmomi.soapStub[12] opID=bd06a10d-bf5c-4193-81ab-8da29cd4509d-isReconfigureRequired] Connected to host using internallookup/2.0 (lookup. version. version2)
2025-06-04T20:03:13.780Z warning drconfig[01363] [SRM@6876 sub=Default] Failed to connect socket; , <TCP '172.x.x.22 : 443'>>, e: 110(Connection timed out)
2025-06-04T20:03:13.780Z verbose drconfig[01362] [SRM@6876 sub=vmomi.soapStub[11] opID=8f3c8409-f5b3-4096-9a87-2f6eab6999d2-isReconfigureRequired] Resetting stub adapter for server: Closed
2025-06-04T20:03:13.780Z error drconfig[01362] [SRM@6876 sub=DrConfigConfigurationManager opID=8f3c8409-f5b3-4096-9a87-2f6eab6999d2-isReconfigureRequired] Failed to obtain VC instance id by URL.

Resolution

• To Fix the issue related to Short name follow below article,
  
  vSphere Replication Management Server could not establish connection to remote vSphere Replication Management Server at 'unknown:-1'.
  
  
• For DNS, The issue should be resolved by the administrators in charge of DNS servers or Domain Controllers for workaround follow below KN article,

        http://127.0.0.1:9286/sdk invocation failed with "java.net.SocketTimeoutException: 30,000 milliseconds timeout