Error: 'Response from connector: Failed to complete dry run' is seen during directory sync on VMware Identity Manager
search cancel

Error: 'Response from connector: Failed to complete dry run' is seen during directory sync on VMware Identity Manager

book

Article ID: 440209

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

  • VMware Identity Manager (vIDM) Directory synchronization fails for a specific connector. The user interface returns the following fault string: Response from connector: Failed to complete dry run
  • The /opt/vmware/horizon/workspace/logs/connector.log records the following errors:

     ERROR (Thread-4) [<VIDM_NodeName>;<User_Name>@<VIDM_NodeName>;##.###.###.##;] com.vmware.horizon.connector.mvc.UIAlerts - Failed to complete sync due to a problem with the service. Exception Info: User is not authorized.
     ERROR (Thread-4) [<VIDM_NodeName>;<User_Name>@<VIDM_NodeName>;##.###.###.##;] com.vmware.horizon.connector.rest.SyncConfigurationRestController - Failed to complete dry run.
      com.vmware.horizon.client.rest.Exception.ApiException: User is not authorized.

  • The /opt/vmware/horizon/workspace/logs/horizon.log records the following errors:
     
    ERROR (ForkJoinPool.commonPool-worker-2) [;;;] com.vmware.horizon.catalog.impl.GlobalCatalogWebClientImpl - An error occurred while checking the connectivity.
    javax.net.ssl.SSLHandshakeException: PKIX path building failed: java.security.cert.CertPathBuilderException: No issuer certificate for certificate in certification path found.
            at sun.security.ssl.Alert.createSSLException(Alert.java:131) ~[?:1.8.0_352]

Environment

VMware Identity Manager 3.3.7

Cause

This issue occurs due to a duplicate connectorUUID and ClientID within the config-state.json file across multiple connectors in the cluster.

Resolution

To resolve this issue, you must restore the backup of the configuration file on the affected nodes.

  1. Access the affected VMware Identity Manager nodes.

  2. Restore the backup of the config-state.json file by following the detailed instructions available in KB 322679.