Users do not get a login page. The browser might display Server Busy Error.

Verify IP access to Siebel Servers.

See Verifying IP Access to Load-Balanced 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, where SWSE_ROOT is the installation directory for the SWSE.

Open the file and check the following:

• EnableVirtualHosts is True.
• VirtualHostFile is set to the full path to the lbconfig.txt file. The default location for this file is SWSE_ROOT\admin, 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 connection 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 SWSE_ROOT\admin, where SWSE_ROOT is the installation directory for the SWSE.

Typically, this file is generated automatically. If you have edited the virtual server definition, then 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 whether a Siebel Server has been reinstalled or reconfigured.

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

Users do not get a login page. The browser might display Server Busy Error.

(continued)

Increase the SWSE logging level.

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

SIEBEL_SESSMGR_TRACE=1
SIEBEL_LOG_EVENTS=ALL

Then restart the Web server.

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

SIEBEL_SISNAPI_TRACE=1

This setting 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 connection 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, then the problem is related to network connectivity.

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

Unequal loads might 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. Unequal loads 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 evens out.

Siebel Servers do not have equal access to computing resources.

Verify that all of the 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. During the process in which current sessions are terminated and new sessions are started, the new Siebel Server is 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.

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

(continued)

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

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

• The SCBroker component either is 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 task or thread that is not responding.
• 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 that the basic configuration is correct. For more information about monitoring and diagnosing server problems, see Siebel System Monitoring and Diagnostics Guide.