2025-11-17T16:55:48,453 ERROR (Timer-4) [;;;] com.vmware.horizon.connector.admin.SyncScheduleService - Unable to fetch config status for service initiated sync.
com.vmware.horizon.connector.exception.HorizonException: Could not get the Suite Token from Service.
at com.vmware.horizon.connector.admin.service.impl.TokenGenerationServiceImpl.getSuiteToken(TokenGenerationServiceImpl.java:46) ~[connector-service-api-0.1.jar:3.3.7.0 Build 21173100]
at com.vmware.horizon.connector.admin.SyncScheduleService.isServiceInitiatedFlow(SyncScheduleService.java:220) ~[classes/:3.3.7.0 Build 21173100]
at com.vmware.horizon.connector.admin.ScheduleService$2.run(ScheduleService.java:256) ~[classes/:3.3.7.0 Build 21173100]
at java.util.TimerThread.mainLoop(Timer.java:555) ~[?:1.8.0_352]
at java.util.TimerThread.run(Timer.java:505) ~[?:1.8.0_352]
Caused by: com.vmware.horizon.client.rest.Exception.ApiException: Request failed: Connect to localhost:443 [localhost/127.0.0.1] failed: connect timed out
2025-11-17T16:55:44,449 INFO (Timer-4) [;;;] org.apache.http.impl.execchain.RetryExec - I/O exception (org.apache.http.conn.ConnectTimeoutException) caught when processing request to {s}->https://localhost:443: Connect to localhost:443 [localhost/127.0.0.1] failed: connect timed out
2025-11-17T16:55:44,449 INFO (Timer-4) [;;;] org.apache.http.impl.execchain.RetryExec - Retrying request to {s}->https://localhost:443
2025-11-17T16:55:48,451 WARN (resourceSyncTaskExecutor-4) [;;;] com.vmware.horizon.client.rest.Utils - Request failed: Connect to localhost:443 [localhost/127.0.0.1] failed: connect timed out
org.apache.http.conn.ConnectTimeoutException: Connect to localhost:443 [localhost/127.0.0.1] failed: connect timed out
Identity Manager 3.3.7
Directory Sync configured with Integrated Windows Authentication requires the connector to be joined to the AD domain so it can use the machine account to do the AD searches.
The Likewise application is used within our appliances for the AD connection from Linux. At times this connection gets disrupted causing unexpected communication issues with AD.
The status of the connection can be checked from the command line by doing an SSH into the appliance that is used for the Sync process and running a likewise query:
This is the output if the server is not currently joined to a domain.
# /opt/likewise/bin/domainjoin-cli query
Name = <IDM_Hostname>
Domain =
# /opt/likewise/bin/domainjoin-cli leave