The login script successfully connected to the application server and started the application.

The login script failed due to a lack of system resources on the application server.

Ensure that the application server is capable of running the application.

No licenses were available on the application server.

Ensure that the application server has sufficient licenses for the number of connections you expect to make.

The login script contains a syntax error.

Review the login script.

The login script failed to log into the application server.

See see Troubleshooting ErrApplicationServerLoginFailed Errors.

The user name and password supplied to the application server were not accepted.

Check that the user name and password are valid on that application server.

The user’s password on the application server has expired.

Ensure that the user has a valid password on the application server.

To avoid seeing this error, configure SGD to handle aged passwords. You configure this on the Global Settings -> Application Authentication tab in the Administration Console.

The login script successfully logged in to the application server but could not run the application.

Ensure that the application object’s Application Command attribute contains a valid command.

Ensure that the user has write permissions for the /tmp directory on the application server.

The login script failed to log in to the application server.

Check that you can log into the application server manually.

The login script encountered an End of File error (EOF) on connection to the application server.

Investigate why an EOF error is returned.

The login script timed out when trying to connect to the application server.

See Troubleshooting ErrApplicationServerTimeout Errors.

The width and height defined for a Windows application is not valid.

Check the application object’s Window Size: Width and Window Size: Height attributes.

The login script was unable to create a pipe between the parent and child processes in the Execution Protocol Engine.

This error might indicate that there is not enough memory on the application server. Check the number of other applications running on the server and increase size of memory if necessary.

The login script was unable to fork a child process in the Execution Protocol Engine.

This error might indicate that there is not enough memory on the application server. Check the number of other applications running on the server and increase the amount of memory if necessary.

The login script produced an error when trying to read from the script process in the Execution Protocol Engine.

Try to run the application again. If the error persists, contact Oracle Support.

The login script produced an error when trying to write to the script process in the Execution Protocol Engine.

Try to run the application again. If the error persists, contact Oracle Support.

The login script produced an error when trying to write to the application server in the Execution Protocol Engine.

This error usually means the connection to the application server was lost. Check the application server is available and try to run the application again.

The login script produced an error when trying to read from the application server in the Execution Protocol Engine.

This error usually means the connection to the application server was lost. Check the application server is available and try to run the application again.

The login script was unable to connect to the application server using the requested connection method method.

Check that the application server supports the connection method. Check that the application server is available.

This is not an application startup error. SGD was unable to create a log file for the Protocol Engine Manager.

If the error persists, contact Oracle Support.

Something has gone wrong on the application server.

Check that the server is available and that you can run the application manually.

The login script was unable to supply the application server with a password.

This error usually means the Execution Protocol Engine timeout has been triggered. See Other Timeouts for details of how to increase the Execution Protocol Engine timeout.

The login script cannot execute the requested auxiliary commands.

Check that the Arguments for Command attribute for the application object is configured correctly and that the additional commands work on the application server.

The login script cannot execute the requested operation because it has not been implemented.

If the error persists, contact Oracle Support.

An error occurred in the Execution Protocol Engine.

Check the log file and try to run the application again.

An error in the Protocol Engine Manager.

Check the log file and try to run the application again.

The Protocol Engine process failed.

Check the log file for the process ID of the protocol engine and try running the application again. If the problem persists, contact Oracle Support.

SGD was unable to initialize the Expect interpreter and so the script was not run.

Try to run the application again. If the problem persists, contact Oracle Support.

The login script file does not exist or contains a syntax error that is causing the Expect interpreter to fail.

Check that the login script is in the specified directory. All login scripts supplied by SGD are stored in the /opt/tarantella/var/serverresources/expect directory. Check the Execution Protocol Engine error log file for details of any errors with the script.

SGD was unable to initialize the Tcl interpreter and so the script was not run.

Try to run the application again. If the error persists, contact Oracle Support.

The login script failed to change to the directory containing the script.

Check the path to the script.

The login script produced an error when trying reading from the protocol connection between the parent and child processes in the Execution Protocol Engine.

Try to run the application again. If the error persists, contact Oracle Support.

The login script read an unexpected end of file on a connection.

Try to run the application again. If the error persists, contact Oracle Support.

The login script received an invalid message, probably due to a corruption of the data packet.

Try to run the application again. If the error persists, contact Oracle Support.

The client connected to the application but the cookie needed for the application startup has expired.

Try to run the application again.

If this fails, increase the lifetime of the cookie. You do this with the following command:

$ tarantella config edit --tarantella-config-applaunch-reconnecttimeout seconds

The default value is 60 (60 seconds). If the error persists, contact Oracle Support.

The client connected to the application but the cookie needed for the application startup has already been used, probably by the user running multiple sessions.

Try to run the application again. If the error persists, contact Oracle Support.

The client connected to the application but the cookie supplied does not match the one required for the application startup.

Try to run the application again. If the error persists, contact Oracle Support.

SGD was unable to find the details needed to run the application.

This error might never occur. Try to run the application again. If this fails, stop the SGD server, start it again, and then run the application again. If the error persists, contact Oracle Support.

The login script received a message that was not the correct length, probably due to a corruption of the data packet.

Try to run the application again. If the error persists, contact Oracle Support.

The configuration data provided by SGD did not contain all the required information.

This error might never occur. Try to run the application again. If this fails, stop the SGD server, start it again and then run the application. If the error persists, contact Oracle Support.

The connection between the protocol engine and the Protocol Engine Manager was lost.

Try to run the application again. If this fails, stop the SGD server, start it again and then run the application. If the error persists, contact Oracle Support.

The connection between the Protocol Engine Manager and the Execution Protocol Engine was lost.

Try to run the application again. If this fails, stop the SGD server, start it again, and then run the application. If the error persists, contact Oracle Support.

The Protocol Engine Manager cannot find a circuit (connection).

Try to run the application again. If this fails, stop the SGD server, start it again and then run the application. If the error persists, contact Oracle Support.

The create request to the protocol engine failed and SGD was unable to run the application.

The definition of the application is missing some attributes. Check the log file for details of the missing attributes and correct these errors before trying to run the application again

This is not an error. It is a message from the Execution Protocol Engine to the Protocol Engine Manager to indicate the launch process was completed.

When the SGD Client connected to the protocol engine, an error occurred.

If possible, log out. Otherwise, close the browser and end the SGD Client processes on the client device. Try to run the application again.

This is not an error. The user canceled the application launch.

The connection to the SGD Client was lost.

If possible, log out. Otherwise, close the browser and end the SGD Client processes on the client device. Try to run the application again.

This is not an error.

This message indicates that the launch request sent to the Protocol Engine Manager does not require any protocol engines.

The login script was unable to write to stderr.

Try to run the application again. If the error persists, contact Oracle Support.

There are not enough Windows Terminal Services licenses available to be able to run the application.

Increase the number of Windows Terminal Services licenses.