Bookshelf Home | Contents | Index | Search | PDF

Siebel Server Installation Guide for Microsoft Windows > Installing the Siebel Server >

Troubleshooting Siebel Server Installation

---

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 Siebel Server, see Preparing for the Installation.
Trying to install the Siebel Server out of sequence. For the required installation sequence, see Preparing for the Installation.
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.

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

Problem: The following error messages occur in an Enterprise supported by an MS SQL Server Database:

In the SVRsetup.log file, "5000: Bad key name., exiting..."
In Microsoft SQL Server DSN Configuration, "completed with error(s):2000046," in the server field.

Solution: You used brackets in the name you gave to one or more of your Siebel Servers or to your Siebel Enterprise Server. Uninstall these and reinstall them, giving them a new name.

Problem: Siebel Server processes start, but terminate again immediately.

Solution: If Resonate Central Dispatch is installed on the Siebel Server, but the Enterprise is not configured for Resonate, Siebel programs may fail. With the Siebel Gateway running, use Server Manager to set the UseSCB parameter on this Siebel Server to FALSE.

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: 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 the DOS command window, enter the following command:

srvrmgr -g gateway address -e Siebel Enterprise name

where:

gateway address = the IP address of your Siebel Gateway.

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

At the prompt, enter:

list parameter SCBTimeout for Server Siebel Server name

where:

Siebel Server name = 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 of To verify the current SCBtimeout parameter setting and at the srvrmgr prompt type:

change parameter SCBTimeout=new value for server Siebel Server name

where:

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

Siebel Server name = the alias of the Siebel Server.

If, after trying this procedure, the component still does not start, increase the SCBTimeout parameter in 60 second increments up to 600. If you still experience problems, contact Siebel Technical Support.

For more information on changing parameter values, see Siebel Server Administration Guide.

Bookshelf Home | Contents | Index | Search | PDF