Unable to register the SRM Server with vCenter - "N7Vmacore15SystemExceptionE Failed to stop srm-server"
Article ID: 375855
Updated On:
Products
Issue/Introduction
A general system error occurred "N7Vmacore15SystemExceptionE Failed to stop srm-server (-1)" after renewing the vCenter certificate.
SRM server service was found to be in a stopped state.
vmware-dr.log
WARN com.vmware.dr.configservice.taskMonitor.ConfigureTaskHandler xxxxx-xxxx-xxxx-xxxxx-xxxxxxxxx getConfigureTaskProgress - Task finished with error!
(vmodl.fault.SystemError) {
faultCause = null,
faultMessage = null,
reason = N7Vmacore15SystemExceptionE Failed to stop srm-server (-1)
}
at java.base/jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(Unknown Source)
at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Unknown Source)
at java.base/java.lang.reflect.ReflectAccess.newInstance(Unknown Source)
at java.base/jdk.internal.reflect.ReflectionFactory.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)
Environment
SRM 8.8.0.3
SRM 9.x
Cause
The issue was observed after the vCenter certificate was updated. Incorrect thumbprints on SRM Database tables is the cause of this issue.
From /var/log/vmware/drconfigui/drconfig.log
2025-09-27T03:46:58.801Z info drconfig[00954] [SRM@6876 sub=IO.Http opID=83616b5c-0474-4d72-b0a3-3b1f66ebe40f-listVcServices] Set user agent error; state: 1, (null), N7Vmacore3Ssl18SSLVerifyExceptionE(SSL Exception: Verification parameters:
--> PeerThumbprint: ##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:76:F6
--> ExpectedThumbprint: ##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:B9:C4
--> ExpectedPeerName: ##########.####.com
--> The remote host certificate has these problems:
-->
--> * unable to get local issuer certificate)
- The yellow-highlighted thumbprint is accurate, whereas the orange-highlighted one is stale or inaccurate. The SRM database tables still have the stale.
Resolution
If the above symptoms and issue matches, please contact Broadcom Support to investigate the issue further.
Feedback
