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

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                  / This file is only created in the default tenant folder
  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
         

hferch has written 76 articles

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">