Siebel Server Installation Guide for UNIX > Installing the Siebel Gateway >

Troubleshooting Siebel Gateway Installation

This section describes potential errors that can result from a faulty installation or configuration.

Problem: The Siebel Gateway does not start.

Solution a: If you find that you are not able to start the Siebel Gateway, you may not have privileges as the Siebel Service Owner. Review the instructions in Creating Siebel Accounts, or edit the start_ns script to set the Resonate_ROOT directory to a location where Central Dispatch will not be found.

NOTE:  If you cannot start the Siebel Gateway, you will not be able to configure and start the Siebel Server you are installing in the next chapter for this Enterprise.

Solution b: Failure to start the Siebel Gateway can be caused by a number of problems including, but not limited to, an incorrectly set LD_LIBRARY_PATH (Solaris), SHLIB_PATH (HP-UX), or LIBPATH (AIX), incorrect permissions set on shared libraries, or missing shared libraries. You can use the ldd command to show missing libraries. You should also check the siebelenv.csh and siebelenv.sh and be sure that $SIEBEL_ROOT/lib is set before LD_LIBRARY_PATH (Solaris), SHLIB_PATH (HP-UX), or LIBPATH (AIX). Also make sure that $SIEBEL_ROOT/lib is included. If there are library conflicts, set $SIEBEL_ROOT/lib as the first element of the shared library path environment variable.

Problem: The Siebel Gateway terminates and produces a core dump for no apparent reason when you try to start it.

Solution: If Central Dispatch is installed on the Siebel Gateway machine, but Central Dispatch is not running, Siebel programs will fail. Edit the start_ns script by changing the default for the Resonate_ROOT environment variable to a directory that does not contain a Central Dispatch installation (for example, /dev).


 Siebel Server Installation Guide for UNIX 
 Published: 24 June 2003