Secure Global Desktop 4.40 Administration Guide > Applications, Documents, and Application Servers > An Application Does Not Start

An Application Does Not Start

If an application does not start when a user clicks a link, check the configuration of the application as described in the following sections. If the application still does not start, try increasing the launch timeouts in the login script.

If users cannot log in or start applications, do a warm restart of the SGD servers.

# tarantella restart --warm

How to check Windows applications

1. In the SGD Administration Console, click the Applications tab and select the Windows application. The General tab is displayed.
2. Click the Hosting Application Servers tab.

   Is there at least one application server in the Effective Application Servers list? If not, add one.

   Are all the application servers listed available?

3. Click the Launch tab.
4. Check the Application Command and Arguments for Command.

   Does the command contain the full path name of the application's executable, including the correct filename extension?

   Does the path name point to a Windows shortcut? If so, change it to the full path name of the application itself.

   Is the application installed in the same location on every application server listed in the Hosting Application Servers tab?

   Are the command arguments correct?

5. Check the Windows Protocol.

   Is the correct Windows Protocol used for the type of application server?

6. Check the Login Script.

   Is a login script set?

   Is the login script appropriate for the application type?

7. Check the Environment Variables.

   Are all the environment variables required for the application set correctly?

How to check X applications

1. In the SGD Administration Console, click the Applications tab and select the X application. The General tab is displayed.
2. Click the Hosting Application Servers tab.

   Is there at least one application server in the Effective Application Servers list? If not, add one.

   Are all the application servers listed available?

3. Click the Launch tab.
4. Check the Application Command and Arguments for Command.

   Does the command contain the full path name of the application's executable.

   Is the application installed in the same location on every application server listed in the Hosting Application Servers tab?

   Are the command arguments correct?

5. Check the Connection Method.

   Is the selected Connection Method appropriate for the application servers?

6. Check the Login Script.

   Is a login script set?

   Is the login script appropriate for the application type?

7. Check the Environment Variables.

   Are all the environment variables required for the application set correctly?

Copyright © 1997-2007 Sun Microsystems, Inc. All rights reserved.