Bookshelf Home | Contents | Index | Search | PDF

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

Troubleshooting Siebel Server Installation

---

This section provides guidelines for resolving Siebel Server installation problems.

Installation problems can be caused by a number of things, but the reasons listed below are the most common:

Insufficient user privileges. For information about setting up appropriate administrative user privileges to install, see Preparing for the Installation.
Trying to install the Siebel Server out of sequence. For the required installation sequence, see Preparing for the Installation.
Environment variables not set properly. For more information about these, see Managing Environment Variables.
Failure to install required hardware or software. Installation errors related to software requirements are logged in the SES installer log file. For prerequisites, see System Requirements and Supported Platforms.
Faulty network connection. Sometimes a faulty network connection can result in the system administrator being unable to install to the $HOME directory in which he or she has write privileges. Verify that your network connection is stable.
Object Manager does not start. Heavily used servers running more than 50 instances of Object Manager may experience a condition where some of the Object Managers do not start correctly and log the following error message:

Got error 1801210 when dequeueing a connection request (62)

This error is rectified by changing TCP stack parameters. For more information, see Tuning Object Manager Instances for Solaris.

The following list provides other, less common reasons for a faulty installation or configuration.

Problem: The Siebel Server 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 Server, but the Enterprise is not configured for Central Dispatch, Siebel programs may fail. With the Siebel Gateway running, set the UseSCB parameter on this Siebel Server, using Server Manager, to FALSE. For information on how to set Siebel Server parameters, see Siebel Server Administration Guide.

Problem: The Siebel Server does not start after configuration.

Solution a: Verify that the Siebel Gateway was started. Start it if it was stopped.

Solution b: Verify that the values input during configuration were valid.

Solution c: Verify that you have sufficient system privileges to start the service. For more information on this subject, see Preparing for the Installation.

Problem: The Siebel Server does not start and the log file shows a Central Dispatch timeout error for the server.

Solution: Increase your Central Dispatch timeout value, using the Siebel parameter SCBtimeout.

NOTE:  The default setting of this parameter is 300 seconds.

To verify the current SCBtimeout parameter setting

From a UNIX shell, enter the following command:

srvrmgr -g gateway address -e Siebel Enterprise name

where:

gateway address is the IP address of your Siebel Gateway.

Siebel Enterprise name is the alias of your Siebel Enterprise Server.

At the prompt, enter:

list parameter SCBTimeout for Server Siebel Server name

where:

Siebel Server name is the alias of the Siebel Server in which the components failed to start.

At this point, you will want to add more time, starting with an additional 60 seconds, to the value returned by the above procedure.

To increase the timeout value for a failed component

Run the srvrmgr utility from Step 1 in the To verify the current SCBtimeout parameter setting procedure, and at the srvrmgr prompt type:

change parameter SCBTimeout=new value to server Siebel Server name

where:

new value is the new timeout value (in seconds).

Siebel Server name is the alias of the Siebel Server.

Bookshelf Home | Contents | Index | Search | PDF