Connector Failed to load Auth Adapters | Auth Adapters are missing from vIDM Node

Products

• VMware

Issue/Introduction

Symptoms:
Directory Creation/ Sync fails with the error featured below error:
        " Connector Communication failed with Response or Invalid Suite Token"

Login with AD user fails with below stack trace under connector.log:

java.lang.NullPointerException
at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:187)
at com.vmware.horizon.client.rest.Api.getOAuth2AccessToken(Api.java:109)
at com.vmware.horizon.client.rest.Api.signIn(Api.java:95)
at com.vmware.horizon.client.rest.Api.signIn(Api.java:90)

The horizon.log my also feature the below events:

com.vmware.horizon.connector.management.ConnectorServiceImpl - Connector Already Exists for hostname:vidm.domain.com
2020-11-24T12:13:05,862 WARN (Thread-34826) [IDM-TENANT;dbef9405-xxxx-xxxx-b262-00c275537e91;127.0.0.1;] com.vmware.horizon.common.utils.Messages - No such key connector.exists

INFO (tomcat-http--14) [;;] com.vmware.horizon.common.api.token.SuiteToken - Suite token failed to initialize.
WARN (tomcat-http--14) [3002@ESILAB;-;127.0.0.1] com.vmware.horizon.common.api.token.SuiteToken - SuiteToken revocation check failed. The SuiteTokenConfiguration.getRevokeCheckUrl was not set.

Environment

VMware Identity Manager 3.3.x

Cause

The errors and events above are generated due to a corrupt config-states.json file.

Resolution

To resolve this issue, revert to working config-states.json file located under /usr/local/horizon/conf/states/<TENANT_NAME>/<WORKER_ID> following the article HW-134096 - VMware Identity Manager Connector may fail to communicate due to config-state.json corruption