Signing into VMware Aria Suite of Products with Workspace One user fails with error
search cancel

Signing into VMware Aria Suite of Products with Workspace One user fails with error

book

Article ID: 426729

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

  • Login with VIDM user to Aria Suite of Products results in the UI not loading , error is shown and the URL is redirected to https://<vIDMFQDN>/hc/error
  • The /usr/local/horizon/conf/states/<TENANT_NAME>/<WORKER_ID>/config-state.json file is not corrupted as per KB VMware Identity Manager Connector may fail to communicate due to config-state.json corruption 
  • One or more nodes in the /opt/vmware/horizon/workspace/logs/connector.log shows errors similar to: 
    2026-01-08T12:32:38,785 WARN  (resourceSyncTaskExecutor-1) [;;;] com.vmware.horizon.engine.ObjectPullEngine - Code from Service :-444 2026-01-08T12:32:38,785 ERROR (resourceSyncTaskExecutor-1) [;;;] com.vmware.horizon.pullengine.HealthCheckClient - Error while checking the health of horizon service com.vmware.horizon.connector.exception.PullEngineException: Could not retrieve required object from Horizon at com.vmware.horizon.engine.ObjectPullEngine.processResult(ObjectPullEngine.java:336) ~[connector-service-api-0.1.jar:3.3.7.0 Build 21173100] at com.vmware.horizon.engine.ObjectPullEngine.getObjectFromHorizon(ObjectPullEngine.java:91) ~[connector-service-api-0.1.jar:3.3.7.0 Build 21173100] at com.vmware.horizon.pullengine.HealthCheckClient.getStatus(HealthCheckClient.java:35) ~[connector-service-api-0.1.jar:3.3.7.0 Build 21173100] at com.vmware.horizon.connector.utils.ServiceUtils.isServiceUp(ServiceUtils.java:77) ~[classes/:3.3.7.0 Build 21173100] at com.vmware.horizon.connector.utils.ServiceUtils.waitForServiceToBeUp(ServiceUtils.java:44) ~[classes/:3.3.7.0 Build 21173100] at com.vmware.horizon.connector.admin.service.ConnectorVersionService.updateConnectorVersion(ConnectorVersionService.java:74) ~[classes/:3.3.7.0 Build 21173100] at com.vmware.horizon.connector.admin.service.ConnectorVersionService$$FastClassBySpringCGLIB$$42eb2211.invoke(<generated>) ~[classes/:3.3.7.0 Build 21173100] at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218) ~[kdc-kerberos-auth-adapter-0.1.jar:3.3.7.0 Build 21173100] at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:793) ~[kdc-kerberos-auth-adapter-0.1.jar:3.3.7.0 Build 21173100] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163) ~[kdc-kerberos-auth-adapter-0.1.jar:3.3.7.0 Build 21173100] at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:763) ~[kdc-kerberos-auth-adapter-0.1.jar:3.3.7.0 Build 21173100] at org.springframework.aop.interceptor.AsyncExecutionInterceptor.lambda$invoke$0(AsyncExecutionInterceptor.java:115) ~[kdc-kerberos-auth-adapter-0.1.jar:3.3.7.0 Build 21173100] at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_352] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_352] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_352] at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_352] 2026-01-08T12:32:38,785 INFO  (resourceSyncTaskExecutor-1) [;;;] com.vmware.horizon.connector.utils.ServiceUtils - Waiting 30 seconds to check again. Attempts = 328544

Environment

VIDM 3.3.7

Cause

Incorrect URL was added to 

Resolution

WARNING: This procedure involves manually editing a critical configuration file. This is not a standard recovery step and should be considered a last resort when all other documented procedures have failed.

  • Proceed with extreme caution. Typos or incorrect JSON formatting will prevent services from starting.
  • Broadcom Support does not typically recommend direct modification of this file.
  • Take a cold snapshot of all vIDM nodes before proceeding.
  • Back up the current (broken) config-state.json file before making any edits: 
    cp /usr/local/horizon/conf/states/<TENANT_NAME>/<WORKER_ID>/config-state.json /usr/local/horizon/conf/states/<TENANT_NAME>/<WORKER_ID>/config-state.json.MANUAL_EDIT_BACKUP

* Where <TENANT_NAME>/<WORKER_ID> is depending on your environment
  1. Identify the affected node
  2. Edit the the config-state.json file in a text editor (like vi). 
    vi /usr/local/horizon/conf/states/<TENANT_NAME>/<WORKER_ID>/config-state.json
  3. Carefully search for all string instances of the incorrect URL (e.g., node03.example.com) for example  
    "url" : "https://<node03>:443/SAAS/t/<node01>",
  4. Replace the incorrect URL with the correct FQDN of the Load Balancer (e.g., vidm.example.com) for example:  
    "url" : "https://<vidm.example.com>:443/SAAS/t/<node01>"
  5. Save and Exit: Save your changes to the file.
  6. Restart the horizon-workspace service. 
     service horizon-workspace restart
  7. Confirm you can login to the Aria Suite of Products with VIDM user
Powered by Wolken Software