Siebel Installation Guide for UNIX > Verifying and Troubleshooting Your Installation >

Troubleshooting Installation for the Siebel Web Server Extension

This topic provides suggestions for troubleshooting problems that you might encounter when installing and configuring the Siebel Web Server Extension (SWSE). Typical problems are shown in Table 16.

Table 16. Troubleshooting Siebel Web Server Extension Installation

The Siebel Web Server Extension plug-in does not start.

Failure to start the SWSE plug-in can be caused by a number of problems including, but not limited to:

  • Incorrectly set LIBPATH (AIX), SHLIB_PATH (HP-UX), or LD_LIBRARY_PATH (Linux or Oracle Solaris) environment variable
  • Incorrect permissions set on shared libraries
  • Missing shared libraries

Use the ldd command to show missing libraries.

Make sure that $SIEBEL_HOME/lib is included and set before LIBPATH (AIX), SHLIB_PATH (HP-UX), or LD_LIBRARY_PATH (Linux or Oracle Solaris). If there are library conflicts, then set $SIEBEL_HOME/lib as the first element of the shared library path environment variable.

Check the LIBPATH, SHLIB_PATH, or LD_LIBRARY_PATH settings in all applicable files, including cfgenv.csh (for C shell) or (for Bourne or Korn shell).

After installation, when the Siebel Web Client is started, a message appears, stating:

Page Cannot be displayed

The Web server instance is not running.

Make sure that the Web server instance is running.

Refresh the connection between your browser and the Web site.

The Web server port is incorrectly specified in the eapps.cfg file.

Verify that the Web server port information in the eapps.cfg file is correct.

Virtual directories were not installed or configured properly.

Make sure that the Local Path for the virtual directories is correct and resembles the following:


Anonymous users have incorrect responsibilities.

Make sure that anonymous users specified in the eapps.cfg file (AnonUserName and AnonPassword parameters) are also defined in the Siebel database with the correct responsibilities. Otherwise, end users cannot access the home page.

The connect string for the Siebel application is incorrect.

Make sure that the connect string for the Siebel application is correct. The value resembles the following example (where load balancing is not deployed):

ConnectString = siebel.TCPIP.none.none://SiebelServerHost:2321/EnterpriseServerName/ProductNameObjMgr_language

Siebel Server components or component groups might not be enabled.

Make sure that the necessary Siebel Server components and component groups are enabled.

Your Siebel application stops responding, displays a blank page or page not found, or times out.

Appropriate parameters are not available within the [defaults] section of the eapps.cfg file for Siebel Business Applications.

Make sure that the [defaults] section of the eapps.cfg file contains valid AnonUserName, AnonPassword, HTTPPort, and HTTPSPort values.

Also make sure that SessionTimeout and GuestSessionTimeout have appropriate values. For information about configuring these and other parameters, see Configuring the SWSE Logical Profile.

Inability to access the Siebel Web Client. The browser status bar might display errors such as:

SWESubmitOnEnter is undefined

Also, the login page might stop responding.

Or, the Siebel Web Client login page does not display properly; for example, images might be missing.

The user running the SWSE plug-in does not have proper permissions to the SWSE_ROOT/public/lang directory.

Stop the Web server. Make sure that the permissions meet the requirements described in Requirements for Installing and Configuring the Siebel Web Server Extension. Restart the Web server.

Siebel Installation Guide for UNIX Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices.