Secure Global Desktop 4.40 Administration Guide > Users and Authentication > Login Script Error Messages

Login Script Error Messages

The following table lists the Error Codes and Error Names that can occur with login scripts, and a description of what to do about them. Use this information to diagnose why a login script is failing.

The Error Codes are displayed in the Launch Details area of the application launch dialog and have the following form:

"Script process_id exited with code error_code and signal signal"

The Error Name is displayed in the Launch Details area of the application launch dialog and also appears in log files.

Code	Error Name and Description
0	`OK` The login script successfully connected to the application server and started the application.
1	`ApplicationServerResourceFailure` 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.
2	`ApplicationServerNoLicenseAvailable` 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.
3	`FaultInExecutionScript` The login script contains a syntax error. Review the login script.
4	`ApplicationServerLoginFailed` The login script failed to log into the application server. Check that you can log into the application server manually. If you can log in, check that the application server's system prompt is recognized by the login script. If you are using the standard SGD login scripts, check the system prompts defined in `vars.exp`. The login script might also be timing out. Increase the `timeouts(prelogin)` value in `vars.exp` and see if this fixes the problem. See Login Script Timeouts for details.
5	`ApplicationServerLoginIncorrect` 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.
6	`ApplicationServerPasswordAged` 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.
7	`CommandExecutionFailed` 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.
8	`ApplicationServerConnectionFailed` The login script failed to log in to the application server. Check that you can log into the application server manually.
9	`ApplicationServerEndOfFileOnConnection` The login script encountered an End of File error (EOF) on connection to the application server. Investigate why an EOF error is returned.
10	`ApplicationServerTimeout` The login script timed out when trying to connect to the application server. Investigate why the login script timed out on the application server.
12	`InvalidDesktopSize` 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.
14	`CouldNotPipe` The login script was unable to create a pipe between the parent and child processes in the Execution Protocol Engine (ExecPE). 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.
15	`CouldNotFork` The login script was unable to fork a child process in the Execution Protocol Engine (ExecPE). 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.
16	`ScriptRead` The login script produced an error when trying to read from the script process in the Execution Protocol Engine (ExecPE). Try to run the application again. If the error persists, contact Technical Support.
17	`ScriptWrite` The login script produced an error when trying to write to the script process in the Execution Protocol Engine (ExecPE). Try to run the application again. If the error persists, contact Technical Support.
18	`ThirdTierWrite` The login script produced an error when trying to write to the application server in the Execution Protocol Engine (ExecPE). 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.
19	`ThirdTierRead` The login script produced an error when trying to read from the application server in the Execution Protocol Engine (ExecPE). 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.
21	`TransportNotAvailable` 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.
22	`LogFileError` This is not a application launch error. SGD was unable to create a log file for the Protocol Engine Manager. If the error persists, contact Technical Support.
27	`ThirdTierFailure` Something has gone wrong on the application server. Check that the server is available and that you can run the application manually.
31	`RequestNotSupported` 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.
32	`RequestNotImplemented` The login script cannot execute the requested operation because it has not been implemented. If the error persists, contact Technical Support.
33	`Unknown` Something went wrong in the Execution Protocol Engine (ExecPE). Check the log file and try to run the application again.
34	`InternalError` Something went wrong in the Protocol Engine Manager (PEM). Check the log file and try to run the application again.
37	`ProtocolEngineDied` The Protocol Engine process failed. Check the log file for the PID of the protocol engine and try running the application again. If the problem persists, contact Technical Support.
43	`ExpectInitialisationFailed` 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 Technical Support.
44	`EvalFileFailed` 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 the Execution Protocol Engine (ExecPE) error log file for details of any errors with the script.
45	`CreateInterpreterFailed` 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 Technical Support.
46	`ChdirFailed` The login script failed to change to the directory containing the script. Check the path to the script.
47	`ReadError` The login script produced an error when trying reading from the protocol connection between the parent and child processes in the Execution Protocol Engine (ExecPE). Try to run the application again. If the error persists, contact Technical Support.
49	`EndOfFile` The login script read an unexpected end of file on a connection. Try to run the application again. If the error persists, contact Technical Support.
51	`BadMessage` 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 Technical Support.
52	`StaleCookie` The client connected to the application but the cookie needed for the application launch 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 Technical Support.
53	`EatenCookie` The client connected to the application but the cookie needed for the application launch has already been used (probably by the user running multiple sessions). Try to run the application again. If the error persists, contact Technical Support.
54	`DifferentCookie` The client connected to the application but the cookie supplied does not match the one required for the application launch. Try to run the application again. If the error persists, contact Technical Support.
55	`LaunchPolicyNotFound` 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 Technical Support.
56	`BadLength` 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 Technical Support.
57	`InvalidConfigObject` 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 Technical Support.
58	`SessionCircuitNotFound` The connection between the protocol engine and the Protocol Engine Manager (PEM) 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 Technical Support.
59	`ExecutionCircuitNotFound` The connection between the Protocol Engine Manager and the Execution Protocol Engine (ExecPE) 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 Technical Support.
61	`CircuitNotFound` The Protocol Engine Manager (PEM) 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 Technical Support.
62	`CreateFailed` 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
63	`Complete` This is not an error. It is a message from Execution Protocol Engine (ExecPE) to the Protocol Engine Manager to indicate the launch process was completed.
65	`NonZeroConnectresult` When the SGD Client connected to the protocol engine, an error occurred. If possible, log out. Otherwise, close the web browser and end the SGD Client processes on the client device. Try to run the application again.
66	`UserAbort` This is not an error. The user canceled the application launch.
67	`ClientEndOfFileOnConnection` The connection to the SGD Client was lost. If possible, log out. Otherwise, close the web browser and end the SGD Client processes on the client device. Try to run the application again.
68	`NothingToDo` This is not an error. This message indicates that the launch request sent to the Protocol Engine Manager (PEM) does not require any protocol engines.
71	`IoError` The login script was unable to write to `stderr`. Try to run the application again. If the error persists, contact Technical Support.
73	`TscLicenseor` There are not enough Windows Terminal Services licenses available to be able to run the application. Increase the number of Windows Terminal Services licenses.

Related Topics
An Application Does Not Start Increasing the Launch Timeouts in the Login Scripts Login Scripts Supplied With SGD Login Script Tcl Commands and Procedures Login Script Variables