Users Report Initial Launch Attempts Are Slow and Fail for Applications Provisioned in SGD Environments with LDAP or Active Directory Authentication

Last updated on OCTOBER 26, 2016

Applies to:

Symptoms

Secure Global Desktop (SGD) Administrators may receive reports that some applications provisioned within SGD may fail to launch after an extended delay on the first, second, or even third launch attempt.  In this scenario, an error message may be presented to the initiating user, such as ErrLaunchPolicynotFound or Error 44 (ErrEvalFileFailed). (See http://docs.oracle.com/cd/E51728_01/E51731/html/login-script-error-messages.html )

This behavior may appear sporadic, as users fine that subsequent launch attempts will work and work quickly. 

The problem may return the next day.

Changes

The SGD deployment may rely upon a LDAP environment for remote authentication that has undergone configuration, resource, or architecture changes. 

Cause