"Operation timed out" error while starting trustmanagement service

Products

VMware vCenter Server

Issue/Introduction

Restarting(starting) vCenter server services failed with "timeout" error while starting trustmanagement service

<DATE_TIME> ERROR service-control Service-control failed. Error: Failed to start services in profile ALL. RC=1, stderr=Failed to start trustmanagement, sps, vapi-endpoint, sts services. Error: Operation timed out

2. From trustmanagement-svcs.log, we found this error "Native platform error [code: 40712]" message and backtrace.

Caused by: com.vmware.identity.interop.NativeCallException: Native platform error [code: 40712][null][null]
at com.vmware.identity.interop.registry.RegistryAdapter.checkNativeErrorCode(RegistryAdapter.java:1334) ~[vmware-identity-platform.jar:?]
at com.vmware.identity.interop.registry.RegistryAdapter.openKey(RegistryAdapter.java:427) ~[vmware-identity-platform.jar:?]
at com.vmware.identity.interop.registry.LinuxRegistryAdapter.openKey(LinuxRegistryAdapter.java:77) ~[vmware-identity-platform.jar:?]
at com.vmware.identity.interop.registry.LinuxRegistryAdapter.openRootKey(LinuxRegistryAdapter.java:88) ~[vmware-identity-platform.jar:?]
at com.vmware.identity.idm.server.config.IdmServerConfig.<init>(IdmServerConfig.java:372) ~[vmware-identity-idm-server.jar:?]
at com.vmware.identity.idm.server.config.IdmServerConfig.<clinit>(IdmServerConfig.java:145) ~[vmware-identity-idm-server.jar:?]
at com.vmware.identity.idm.server.config.ConfigStoreFactory.<init>(ConfigStoreFactory.java:34) ~[vmware-identity-idm-server.jar:?]
at com.vmware.identity.idm.server.IdentityManager.<init>(IdentityManager.java:401) ~[vmware-identity-idm-server.jar:?]
at com.vmware.identity.idm.server.IdentityManager.getIdmInstance(IdentityManager.java:12878) ~[vmware-identity-idm-server.jar:?]
at com.vmware.identity.idm.client.CasIdmClient.<init>(CasIdmClient.java:154) ~[vmware-identity-idm-client.jar:?]
at com.vmware.identity.idm.client.CasIdmClient.<init>(CasIdmClient.java:141) ~[vmware-identity-idm-client.jar:?]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:1.8.0_345]

3. We can found similar logs from sts-health-status.log

<DATE_TIME> - __main__ - INFO - Stderr: Picked up JAVA_TOOL_OPTIONS: -Xms32M -Xmx128M -Dcom.sun.org.apache.xml.internal.security.ignoreLineBreaks=true -Dorg.apache.xml.security.ignoreLineBreaks=true
log4j:WARN No appenders could be found for logger (com.vmware.identity.interop.NativeLibraryPreloader).
log4j:WARN Please initialize the log4j system properly.
Exception in thread "main" com.vmware.identity.interop.NativeCallException: Native platform error [code: 40712][null][null]
at com.vmware.identity.interop.registry.RegistryAdapter.checkNativeErrorCode(RegistryAdapter.java:1334)
at com.vmware.identity.interop.registry.RegistryAdapter.openKey(RegistryAdapter.java:427)
at com.vmware.identity.interop.registry.LinuxRegistryAdapter.openKey(LinuxRegistryAdapter.java:77)
at com.vmware.identity.interop.registry.LinuxRegistryAdapter.openRootKey(LinuxRegistryAdapter.java:88)
at com.vmware.identity.configure.HostnameReader.read(HostnameReader.java:40)
at com.vmware.identity.configure.HostnameReader.readPortNumber(HostnameReader.java:66)
at com.vmware.identity.health.StsHealthStatus.main(StsHealthStatus.java:22)

4. When you check registry key using the following command with trustmanagement user like below, there is error with 40712 code.

# sudo -u trustmanagement /opt/likewise/bin/lwregshell list_keys [HKEY_THIS_MACHINE\\Services\\lsass\\Parameters\\Providers\\ActiveDirectory]

Output: lwregshell (error = 40712 - LWREG_ERROR_INVALID_ACCESS_TOKEN)

Environment

VMware vCenter Server 8.x

Resolution

Issue will be resolved after leaving the AD domain using the following command

/opt/likewise/bin/domainjoin-cli leave

Reboot the vCenter server
To check the current status of the AD domain use the following command.

/opt/likewise/bin/domainjoin-cli query