#NATIVE ACCESS SERVER PROBLEM FULL#

A Siebel Server has recently added or has been restarted.Verify that all Siebel Servers have equal access to computing resources such as CPU and memory. Siebel Servers do not have equal access to computing resources.Over a longer period, the number of sessions handled by each server will even out. 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. Unequal loads may be caused by characteristics of users and jobs.īecause jobs are distributed in a round-robin fashion, it is normal for a snapshot of the servers to show somewhat unequal loads.Users can connect but loads are not balanced evenly between Siebel Servers If the login fails, the problem is related to network connectivity. If the login succeeds, then the problem is with the Siebel native load balancing configuration. Restart the Web server and try to log in. Open the SWSE configuration file (eapps.cfg) and edit the connect string for an Application Object Manager to specify a known good Siebel Server. Configure a Web Server to connect directly to a Siebel Server.This greatly increases the logging level for SISNAPI message handling. If this logging level does not reveal the problem, set the following: To turn on detailed SWSE logging, set the following environment variables: If so, the load balancing configuration file (lbconfig.txt) must be edited or regenerated. Check if a Siebel Server has been reinstalled or reconfigured.For each Siebel Server in a virtual server definition, verify that the server ID (sid) is correct.Verify that the syntax of the virtual server definition is correct.If you have edited the virtual server definition, do the following:

Typically, this file is generated automatically. Where SWSE_ROOT is the installation directory for the Siebel Web Server Extension. The default location for the load balancing configuration file (lbconfig.txt) is:

Verify that Siebel native load balancing is configured correctly.

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

Where SWSE_ROOT is the installation directory for the SWSE. The default location for this file is as follows:

#NATIVE ACCESS SERVER PROBLEM FULL#

VirtualHostFile is set to the full path to the lbconfig.txt file.The SWSE configuration file (eapps.cfg) is located in SWSE_ROOT in. Verify that the SWSE is configured correctly.See Verifying Load Balancing Port Access for Siebel Servers. Verify TCP port access on Siebel Servers.See Verifying IP Access to Siebel Servers.

Native access server problem