Troubleshooting Migration to Omnissa Access Connector 22.09

Use this information to troubleshoot errors that can occur during the migration to Omnissa Access connector 22.09.

• Error: When you try to migrate a directory of type Active Directory over Integrated Windows Authentication, you get the following error: Enterprise service <connector hostname>(EAS) response: Adapter configuration invalid: Authentication failed for the given user name and password.

  Solution: This error occurs if there is a time skew between the connector server clock and the domain controller clock. Update the time on the connector server. A best practice is to set up time synchronization using an NTP server.

• Error: resourceSync.profile.write.prohibited.in.preview.state: Create or update or delete of virtual app collection is prohibited when profile migration is in preview state.

  Solution: During the Preview stage of migration, you cannot create, update, or delete virtual apps collections. If you want to make any changes to virtual apps collections, click Abort in the Migration dashboard to cancel the migration process, make your changes, then begin the migration process again.

• Error: enterprise.service.migration.eis.not.found: Cannot transition to the next state because the Virtual App service is not configured.

  Solution: You must install at least one instance of the Virtual App service before you can migrate virtual apps collections.

• Error: enterprise.service.migration.all.profiles.not.migrated: Cannot transition to the next state because one or more virtual apps collections have not been migrated.

  Solution: You must migrate all virtual apps collections that are configured in the Omnissa Access service before you can continue with migration. In the Migrate Virtual Apps Collections section of the Migration dashboard, click Review and, for each virtual apps collection, select a connector that has the Virtual App service installed and in Active state.

• Error: enterprise.service.migration.old.connector: This connector version cannot be upgraded to the latest connector. Upgrade your connector to version 19.03.

  Solution: Migration is supported from connector version 19.03 and 19.03.0.1 to 22.09.

• Error: After migration, when you try to add a Horizon pod, or sync a Horizon or Horizon Cloud virtual apps collection, you get the following error: Enterprise service <connectorFQDN>(EIS) response: Unable to get certificate from the URL: <https://FQDN/SAML/metadata/sp.xml>.

  Solution: Ensure that the Horizon Connection Servers, or the Horizon Cloud tenant's underlying Horizon servers, have valid certificates signed by a trusted Certificate Authority (CA). If the Horizon servers have self-signed certificates, you must upload the certificate chain to the Omnissa Access connector instances on which the Virtual App service is installed to establish trust between the connectors and the Horizon servers. This is a new requirement beginning with Omnissa Access connector 21.08. You upload the certificates using the connector installer. See Installing Workspace ONE Connector 22.09 for more information. Make sure that you restart the connector services after uploading the certificates.