Siebel Installation Guide for UNIX: Servers, Mobile Web Clients, Tools > Installing the Siebel Web Server Extension >

Troubleshooting Siebel Web Server Extension Installation

This section provides suggestions for troubleshooting problems you may encounter when installing the Siebel Web Server Extension.

Problem: After installation, when launching the Siebel Web Client, a message appears, stating:

Page Cannot be displayed

Cause: Virtual directories were not installed or configured properly.

Solution: Use the following procedure to resolve the problem.

1. Refresh the connection between your browser and the Web site.
2. Make sure that the Local Path for the virtual directories is correct. This path should be the following:

   $SWEAPP_ROOT/public/language

3. Make sure that the AnonUser specified in the eapps.cfg file is also specified in the database with the correct responsibilities. Otherwise, you cannot access the home page.
4. Make sure that the connect string for the Siebel application is correct. It should be defined similar to the following (where load balancing is not deployed):

   ConnectString = siebel.TCPIP.none.none://siebelserver_name:2321/enterprise_name/ProductNameObjMgr_language

Problem: Your Siebel application hangs or times out.

Cause: Appropriate parameters are not available within the [default] section of the eapps.cfg file for the Siebel eBusiness Application.

Solution: Make sure that the defaults section of the eapps.cfg file contains valid username, HTTPPort, and HTTPSPort values.

Problem: Inability to access the Web client. The browser status bar may display errors, such as SWESubmitOnEnter is undefined, and the login page may appear to hang.

Solution: Make sure that the user running the Web server has read and write permission to the $SWEAPP_ROOT directory.

Problem: After installation, when launching the Siebel Web Client, the login page does not display properly. For example, images may be missing.

Cause: The user who installed the SWSE plug-in does not have proper permissions to the $SWEAPP_ROOT/public/lang directory.

Solution: Grant read, write, and execute permissions to this user using the following steps:

1. Stop the Web server.
2. Change the permissions on the lang directory appropriately by using the chmod command (chmod 777 lang).
3. Start the Web server.