Search the VMware Knowledge Base (KB)
View by Article ID

Directory sync in vRA 7.x fails with error 'Connector Communication failed with Response' (2145438)

  • 4 Ratings
Language Editions

Symptoms

  • Running the Directory sync in vRealize Automation 7.x fails.
  • In vRealize Automation 7.x UI, you see error:

    Connector Communication failed with Response

  • In the /storage/log/vmware/horizon/connector.log file of vRealize Automation, you see entries similar to:

    ERROR (tomcat-http--14) [;;] com.vmware.horizon.common.api.token.SuiteToken - No keystore file or URL specified.
    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.
    INFO  (tomcat-http--14) [3002@ESILAB;-;127.0.0.1] com.vmware.horizon.common.api.token.SuiteToken - Initializing keyStore for SuiteToken.
    ERROR (tomcat-http--14) [3002@ESILAB;-;127.0.0.1] com.vmware.horizon.common.api.token.SuiteToken - No keystore file or URL specified.
    INFO  (tomcat-http--14) [3002@ESILAB;-;127.0.0.1] com.vmware.horizon.common.api.token.SuiteToken - Suite token failed to initialize.
    INFO  (tomcat-http--14) [3002@ESILAB;-;127.0.0.1] com.vmware.horizon.connector.mvc.RestControllerInterceptor - Invalid suite token.


Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Purpose

This article provides resolution when the config-state.json has corrupted or become blank or reset with default values.

Cause

This issue occurs if the config-state.json file located in  /usr/local/horizon/conf/states/VSPHERE.LOCAL/3001/ has corrupted or become blank or reset with default values.

Resolution

Caution: This resolution is applicable only if config-state.json file has corrupted or become blank or reset with default values.
 
To resolve the issue:
  1. Take a snapshot of the vRealize Automation Appliance.
  2. SSH to vRealize Automation Appliance using root credentials.
  3. Change directory to the location of the config-state.json file by running the command:

    cd /usr/local/horizon/conf/states/<TENANT_NAME>/<TENANT_ID>

    For Ex: cd /usr/local/horizon/conf/states/VSPHERE.LOCAL/3001

  4. Back up current configuration file by running the command:

    mv config-state.json config-state.json.1

  5. Copy application backup of the configuration file by running the command:

    cp -p config-state.json.backup_v1 config-state.json

  6. Change the owner of the config-state.json to horizon user by running the command:

    chown horizon:www /usr/local/horizon/conf/states/VSPHERE.LOCAL/3001/config-state.json

  7. Change the permission of the config-state.json file by running the command:

    chmod 640 /usr/local/horizon/conf/states/VSPHERE.LOCAL/3001/config-state.json

  8. Restart vIDM/Workspace service by running the command:

    service horizon-workspace restart

Additional Information

To be alerted when this article is updated, click Subscribe to Document in the Actions box.

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 4 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 4 Ratings
Actions
KB: