Secure Global Desktop Administration Guide > Users and authentication > A login script returns an error
Use the information in this topic to help diagnose why the login script is failing.
| Code | Error Name and description |
|---|---|
| 0 |
The login script has successfully connected to the application server and launched the application. |
| 1 |
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 required application. |
| 2 |
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 |
Your login script contains a syntax error. Review your script. |
| 4 |
The login script failed to log into the application server.
Check that you can manually log into the application server. If you
can, check that the application server's system prompt is
recognized by the login script. The login script may also be timing out,
try increasing the timeout value (prelogin) in |
| 5 |
The username and password supplied to the application server were not accepted. Check that the username and password are valid on that application server. |
| 6 |
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, turn the Secure Global Desktop handling of aged passwords on. See What happens when a user's password expires? for details. |
| 7 |
The login script successfully logged in to the application server but could not run the command specified in the object's Application attribute. Ensure that the command is valid. |
| 8 |
The login script failed to log in to the application server. Check that you can manually log into the application server. |
| 9 |
The login script encountered EOF on connection to the application server. Investigate why EOF is being returned. |
| 10 |
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 |
The width and height defined for a Windows application is not valid. Check the Application Width and Application Height attributes. |
| 14 |
The login script was unable to create a pipe between the parent and child processes in the Execution Protocol Engine (ExecPE). This may indicate that there is not enough memory on the application server. Check the number of other applications running on the server and/or increase size of memory. |
| 15 |
The login script was unable to fork a child process in the Execution Protocol Engine (ExecPE). This may indicate that there is not enough memory on the application server. Check the number of other applications running on the server and/or increase size of memory. |
| 16 |
The login script produced an error when trying to read from the script process in the Execution Protocol Engine (ExecPE). Try launching the application again. If the error persists, contact Support. |
| 17 |
The login script produced an error when trying to write to the script process in the Execution Protocol Engine (ExecPE). Try launching the application again. If the error persists, contact Support. |
| 18 |
The login script produced an error when trying to write to the application server in the Execution Protocol Engine (ExecPE). This usually means the connection to the application server has been lost. Check the application server is available and try launching again. |
| 19 |
The login script produced an error when trying to read from the application server in the Execution Protocol Engine (ExecPE). This usually means the connection to the application server has been lost. Check the application server is available and try launching again. |
| 21 |
The login script was unable to connect to the application server using the requested transport method. Check that the application server supports the transport method. Check that the application server is available. |
| 22 |
This is not a launch error. Secure Global Desktop was unable to create a log file for the Protocol Engine Manager. This error should never occur, contact Support. |
| 27 |
Something has gone wrong on the application server. Check that the server is available and that you can run the application manually. |
| 31 |
The login script cannot execute the requested auxiliary commands.
Check that the application server supports the auxiliary commands and that
the ability to execute commands has not been disabled in the script ( |
| 32 |
The login script cannot execute the requested operation because it has not been implemented. This error should never occur, contact Support. |
| 33 |
Something went wrong in the Execution Protocol Engine (ExecPE). Check the log file and try launching the application again. |
| 34 |
Something went wrong in the Protocol Engine Manager. Check the log file and try launching the application again. |
| 37 |
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 Support. |
| 43 |
Secure Global Desktop was unable to initialize the Expect interpreter and so the script was not run. Try running the application again. If the problem persists, contact Support. |
| 44 |
The login script file does not exist or contains a syntax error which is causing
the Expect interpreter to fail. Check that the login script is in
the specified directory (all login scripts supplied by Secure Global Desktop are stored in the |
| 45 |
Secure Global Desktop was unable to initialize the Tcl interpreter and so the script was not run. Try running the application again. If the problem persists, contact Support. |
| 46 |
The login script failed to change to the directory containing the script. Check the path to the script. |
| 47 |
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 launching the application again. If the error persists, contact Support. |
| 49 |
The login script read an unexpected end of file on a connection. Try launching the application again. If the error persists, contact Support. |
| 51 |
The login script received an invalid message, probably due to a corruption of the data packet. Try launching the application again. If the error persists, contact Support. |
| 52 |
The client connected to the application but the cookie needed for the
launch of the application has expired. Try launching the application again.
If this fails, try increasing the lifetime of
the cookie by editing the |
| 53 |
The client connected to the application but the cookie needed for the launch of the application has already been used (probably by the user running multiple sessions). Try launching the application again. If the error persists, contact Support. |
| 54 |
The client connected to the application but the cookie supplied does not match the one required for the launch. Try launching the application again. If the error persists, contact Support. |
| 55 |
Secure Global Desktop was unable to find the launch policy for this session. This error should never occur. Try launching the application again. If this fails, stop the Secure Global Desktop server, start it again and then launch the application again. If the error persists, contact Support. |
| 56 |
The login script received a message that was not the correct length, probably due to a corruption of the data packet. Try launching the application again. If the error persists, contact Support. |
| 57 |
The configuration data provided by Secure Global Desktop did not contain all the required information. This error should never occur. Try launching the application again. If this fails, stop the Secure Global Desktop server, start it again and then launch the application. If the error persists, contact Support. |
| 58 |
The connection between the protocol engine and the Protocol Engine Manager has been lost. Try launching the application again. If this fails, stop the Secure Global Desktop server, start it again and then launch the application. If the error persists, contact Support. |
| 59 |
The connection between the Protocol Engine Manager and the Execution Protocol Engine (ExecPE) has been lost. Try launching the application again. If this fails, stop the Secure Global Desktop server, start it again and then launch the application. If the error persists, contact Support. |
| 61 |
The Protocol Engine Manager can't find a circuit (connection). Try launching the application again. If this fails, stop the Secure Global Desktop server, start it again and then launch the application. If the error persists, contact Support. |
| 62 |
The create request to the protocol engine failed and Secure Global Desktop was unable to launch 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 launch the application again. |
| 63 |
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 |
When Secure Global Desktop connected to the web browser, the browser produced an error. Close the browser and try again. |
| 66 |
This is not an error. The user canceled the application launch. |
| 67 |
The connection to the client was lost. Close the browser and try again. |
| 68 |
This is not an error. It indicates that the launch request sent to the Protocol Engine Manager does not require any protocol engines. |
| 71 |
The login script was unable to write to |
| 73 |
There are not enough Windows Terminal Services licenses available to be able to launch the application. Increase the number of licenses. |
Copyright © 1997-2005 Sun Microsystems, Inc. All rights reserved.