My Oracle Support Banner

"ErrCommandExecutionFailed" error when launching Windows Applications after installing Oracle Secure Global Desktop 5.3 Patch 1 (Doc ID 2278137.1)

Last updated on NOVEMBER 16, 2017

Applies to:

Oracle Secure Global Desktop - Version 5.3 to 5.3 [Release 5.0]
Information in this document applies to any platform.

Symptoms

After installing either Secure Global Desktop (SGD) 5.3 Patch Set Update (PSU) 1 (bundle_Patch_53p1_i3li.tar.gz) or PSU2, Windows applications fail to launch.  On attempting to launch a Windows applications, after entering the username/password, during the "Connection Progress - Secure Global Desktop Client". It displays:

Session failed: Command execution failed

Clicking on "Details" shows the following:

-START-
Trying application server server1.server.com
Starting execution protocol engine



ErrCommandExecutionFailed
Script 4006 exited with code 7 and signal 0
Standard error of script process:

ttatsc: error while loading shared libraries: libkrb5.so.3: cannot open shared object file: No such file or directory (error = 127)
ErrCommandExecutionFailed

Third tier output log:

Session failed: Command execution failed
Session failed: Command execution failed
-STOP-

NOTE: server1.server.com is the Windows application server.


Changes

 This worked fine before patching on SGD 5.3 (5.3.914)

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.