Siebel System Administration Guide > Configuring the System Architecture > Configuring Siebel Server Load Balancing >

Troubleshooting Siebel Native Load Balancing

This topic provides guidelines for resolving problems with Siebel native load balancing. To resolve a problem, look for it in the list of symptoms/error messages in Table 11. Some problem solutions in the table require changing the function of server components.

Table 11. Resolving Siebel Native Load Balancing Problems
Symptom/Error Message
Diagnostic Steps/Cause

Users do not get a login page. Browser may display "Server Busy Error."

  • Verify IP access to Siebel Servers.

See Verifying IP Access to Siebel Servers.


  • Verify TCP port access on Siebel Servers.

See Verifying Load Balancing Port Access for Siebel Servers.


  • Verify that the SWSE is configured correctly.

The SWSE configuration file (eapps.cfg) is located in SWSE_ROOT\bin.

Open the file and check the following:

  • EnableVirtualHosts=True.
  • VirtualHostFile is set to the full path to the lbconfig.txt file. The default location for this file is as follows:


    where SWSE_ROOT is the installation directory for the SWSE.

  • For each load-balanced Application Object Manager, verify that the virtual server specified in the connect string matches the one in lbconfig.txt.


  • Verify that Siebel native load balancing is configured correctly.

The default location for the load balancing configuration file (lbconfig.txt) is:


where SWSE_ROOT is the installation directory for the Siebel Web Server Extension.

Typically, this file is generated automatically. If you have edited the virtual server definition, do the following:

  • Verify that the syntax of the virtual server definition is correct.
  • For each Siebel Server in a virtual server definition, verify that the server ID (sid) is correct.


  • Check if a Siebel Server has been reinstalled or reconfigured.

If so, the load balancing configuration file (lbconfig.txt) must be edited or regenerated.


  • Increase the SWSE logging level.

To turn on detailed SWSE logging, set the following environment variables:



Then restart the Web server.

If this logging level does not reveal the problem, set the following:


This greatly increases the logging level for SISNAPI message handling.


  • Configure a Web Server to connect directly to a Siebel Server.

Open the SWSE configuration file (eapps.cfg) and edit the connect string for an Application Object Manager to specify a known good Siebel Server. Restart the Web server and try to log in.

If the login succeeds, then the problem is with the Siebel native load balancing configuration.

If the login fails, the problem is related to network connectivity.

Users can connect but loads are not balanced evenly between Siebel Servers

  • Unequal loads may be caused by characteristics of users and jobs.

Because jobs are distributed in a round-robin fashion, it is normal for a snapshot of the servers to show somewhat unequal loads. This can be caused by several things, including the nature of the jobs and the rate at which users log in and log out on different servers. Over a longer period, the number of sessions handled by each server will even out.


  • Siebel Servers do not have equal access to computing resources.

Verify that all Siebel Servers have equal access to computing resources such as CPU and memory.


  • A Siebel Server has recently added or has been restarted.

Load balancing is based on user logins. As current sessions are terminated and new sessions started, the new Siebel Server will be included in the load sharing.


  • A Web server cannot route requests to one or more Siebel Servers.

Check for connectivity problems between the Web servers and the Siebel Server with the low workload as described earlier in this table.


  • A Siebel Server is rejecting an unusual number of user requests.

Check the SWSE log files for SISNAPI Connection Refused messages. Possible causes are:

  • SCBroker is either not running or is listening on the wrong port.
  • The requested Application Object Manager is not running or cannot run any more tasks.
  • The requested Application Object Manager has a hung task or thread.
  • The Application Object Manager cannot communicate with the database server.


  • A Siebel Server has functional or configuration problems.

Enable server diagnostics. Look for problems with components. Verify basic configuration is correct.

Siebel System Administration Guide Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices.