I got this error when configuring Horizon DaaS into Workspace One Access. 

I created a Virtual App Collection and after that I uploaded / added the root and intermediate certificates of the DaaS url. And every time I tried to sync the collection I received this error message.

When you create a log bundle in the Workspace One Appliance and open the horizon.log. Then you will find this error message as well.

2022-12-12T14:28:49,016 ERROR (Thread-335) [WSONE01;dfac3873-4990-4c7e-90f7-d4d7f619b691;10.23.21.104;a53a6fc44d86761:10.23.21.104;-] com.vmware.horizon.connector.management.rest.resource.resourcesync.ResourceSyncProfileResource - Received error from the connector while running sync for the profile: 2
java.lang.Exception: Not logged in to server FQDN. Please invoke Save before Sync.
at com.vmware.vidm.eis.desktone.service.DesktoneDesktopService.getDesktopsFromDesktone(DesktoneDesktopService.java:84) ~[?:?]
at com.vmware.vidm.eis.desktone.service.DesktoneDesktopService.getDesktopsFromAllTenants(DesktoneDesktopService.java:69) ~[?:?]
at com.vmware.vidm.eis.desktone.DesktoneResourceOperations.getResourcesForType(DesktoneResourceOperations.java:51) ~[?:?]
at com.vmware.vidm.eis.IntegrationDataService.getResources(IntegrationDataService.java:78) ~[?:?]
at com.vmware.vidm.eis.sync.SyncService.syncResourceType(SyncService.java:227) ~[?:?]
at com.vmware.vidm.eis.sync.SyncService.startSync(SyncService.java:132) ~[?:?]
at com.vmware.vidm.eis.sync.SyncService.lambda$sync$0(SyncService.java:107) ~[?:?]
at com.vmware.vidm.common.async.ContextPassingExecutor.lambda$wrap$0(ContextPassingExecutor.java:48) ~[risk-score-auth-adapter-0.1.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?]
at java.lang.Thread.run(Thread.java:829) ~[?:?]

The easiest way to fix the issue is to follow the next steps:

  • I did edit the on the Virtual app Collection. 
  • I removed the tenant config in step 2
  • added a new one (same settings)

And after that the sync worked as expected.

Loading

Leave a Reply

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