Verifying the Siebel Server ODBC Data Source

The Siebel Server installation program automatically creates an ODBC system data source name (DSN) that it uses to connect to the Siebel Database Server.

To verify the ODBC data source for DB2 UDB
Open the db2cli.ini file in the $SIEBEL_HOME directory and make sure that there is a section called [siebsrvr_enterprise name], where enterprise name is the name given the enterprise during installation; its default name is siebel.
Verify that the following two values are present in the section:
dbalias = aliasname (the database alias cataloged for your DB2 UDB database server)

txnisolation = 1.

If the section is missing, run the configdb2 script in $SIEBEL_HOME/bin to set it, and then reverify that the section is present.

NOTE: It is not recommended to change the default settings created automatically with the ODBC data source.

Verify that the SIEBEL_UNIXUNICODE_DB environment variable is set to DB2.
CAUTION: If you are using Siebel Marketing, which requires simultaneous heterogeneous database connectivity, you need to set this variable to ORACLE regardless of your database platform.

Test the connection by navigating to $SIEBEL_HOME/bin and entering the command:
odbcsql /u user_name /p password /s ODBC DSNW

where:

ODBC DSN is the database connect string.

If you do not receive an error message, the ODBC connection is working.

To verify the ODBC data source for Oracle
Navigate to $SIEBEL_HOME/sys/.odbc.ini.
Locate the section of the file containing a reference to ServerName and Driver.
This section defines the ODBC DSN for Siebel Server. A sample section is represented below. The ServerName, Driver, ColumnsAsChar, and ColumnSizeAsCharacter parameters are the most critical for this procedure:

[SiebSrvr_enterprise name]
Description=Oracle901
ServerName=dvlsun6
Driver=$SIEBEL_HOME/lib/SEor818.so
ColumnsAsChar=1
ColumnSizeAsCharacter=1

The ServerName should be the Oracle connect string you entered while installing the Siebel Server. (To verify this connect string, run sqlplus.) The driver should point to $SIEBEL_HOME/lib/SEor818.so, allowing you to verify the existence of this file.

CAUTION: It is critical that ColumnsAsChar and ColumnSizeAsCharacter be set to 1 to make sure that ODBC Driver behaves correctly.

Verify that the SIEBEL_UNIXUNICODE_DB environment variable is set to ORACLE.
CAUTION: If you are using Siebel Marketing, which requires simultaneous heterogeneous database connectivity, you need to set this variable to ORACLE regardless of your database platform.

Test the connection by navigating to $SIEBEL_HOME/bin and entering the command:
odbcsql /u user_name /p password /s ODBC DSN

where:

ODBC DSN is the database connect string.

If you do not receive an error message, the ODBC connection is working.

NOTE: If your ODBC DSN is not working, the program exits with an error message. Refer to Troubleshooting ODBC Data Source Connection.

Troubleshooting ODBC Data Source Connection
If your connection test for the ODBC data source fails, follow the instructions below to research the cause.

DB2 UDB
Follow the instructions below to troubleshoot connection problems on Solaris, AIX, or HP-UX.

To troubleshoot a failed ODBC connection on Solaris, AIX, or HP-UX
Verify that the database alias entered as part of the Siebel Server configuration is valid, enter:
db2 connect to Database Alias user username using password

where:

Database Alias is the alias of the database.

username is your logon ID.

password is your logon password.

Also, refer to your copy of Deployment Planning Worksheets.

If the database alias entered is correct, check the ODBCINI environment variable to verify that it was set by entering the following command:
echo ${ODBCINI}

The response should be the following:

$SIEBEL_ROOT/sys/.odbc.ini

If the ODBCINI environment variable was set correctly, verify that the.odbc.ini file has a section similar to the following:
[siebsrvr_enterprise]
ServerName=Database Alias
Driver=/instances/v7inst1/sqllib/lib/libdb2.so (Solaris and HP-UX)

or

Driver=/instances/v7inst1/sqllib/lib/libdb2.o (AIX)

Make sure that the library file referenced in the Driver key in Step 3 exists.
If the section in the .odbc.ini file, illustrated in Step 3, exists, verify that the LD_LIBRARY_PATH (Solaris), SHLIB_PATH (HP-UX), or LIBPATH (AIX) includes the path for the ODBC driver by entering the following command:
Solaris: echo ${LD_LIBRARY_PATH}

AIX: echo ${LIBPATH}

HP-UX: echo $[SHLIB_PATH}

If the response illustrated for your platform in Step 5 was correct and you are verifying a Unicode installation, make sure that the following environment variables are set in accordance with the recommendations from your database platform vendor. These variables should also be set in the siebenv.csh and siebenv.sh scripts.
SIEBEL_UNIXUNICODE_DB=DB2

Oracle
Complete the following instructions to troubleshoot connection problems on Solaris, AIX, and HP-UX.

NOTE: If you are unable to verify if your ODBC connection to your Oracle database is working, you should verify that the value of the environment variable TNS_ADMIN is the exact path of tnsnames.ora.

To troubleshoot a failed ODBC connection on Solaris, AIX, or HP-UX
Verify that the Oracle connect string entered as part of Siebel Server configuration is valid.
If the connect string entered is correct, check the ODBCINI environment variable to verify that it was set by entering the following command:
echo ${ODBCINI}

The response should be the following:

$SIEBEL_ROOT/sys/.odbc.ini

If the ODBCINI environment variable was correctly set, verify that the .odbc.ini file is valid by reviewing it for the presence of the following parameters:
[SiebSrvr_Enterprise Name]
ServerName=ora901
Driver=/$SIEBEL_ROOT/lib/SEor818.so
ColumnsAsChar=1
ColumnSizeAsCharacter=1

If these parameters are not present, the file is invalid.

If the .odbc.ini file is valid, verify that the library path includes the path for the ODBC driver on your platform by entering the following command:
Solaris: echo ${LD_LIBRARY_PATH}

AIX: echo ${LIBPATH}

HP-UX: echo ${SHLIB_PATH}

The response should be $SIEBEL_ROOT/lib.

NOTE: Siebel applications only support an Oracle 32-bit client for Oracle 8i. Therefore, if you have installed an Oracle 64-bit client on your Siebel Server, you need to add $ORACLE_HOME/lib32 instead of $ORACLE_HOME/lib to your LD_LIBRARY_PATH (Solaris), SHLIB_PATH (HP-UX), or LIBPATH (AIX).

If the response illustrated for your platform in Step 4 was correct and you are verifying a Unicode installation, make sure that the following environment variables are set in accordance with the recommendations from your database platform vendor. These variables should also be set in the siebenv.csh and siebenv.sh scripts.
SIEBEL_UNIXUNICODE_DB=ORACLE



Online Users

Siebel WebClient Launch Issue

FAQ 1773: What Are the Steps To Troubleshoot the Error Message: "The Server You Are Accessing is Either Busy or Experiencing Difficulties." in a Siebel 7 Web Client User Browser?

FAQ 1773: What Are the Steps To Troubleshoot the Error Message: "The Server You Are Accessing is Either Busy or Experiencing Difficulties…" in a Siebel 7 Web Client User Browser?

Last Modified:	9 December 2004
Area(s):	System Administration
Release(s):	V7 (Enterprise)
Database(s):	DB2, Microsoft, Oracle
App Server OS(s):	AIX, Solaris, Windows NT, Windows 2000, HP-UX
Latest release tested against:	V7 (Enterprise)
Keywords:	web client, server is busy, web browser, trying to access, busy, experiencing difficulties

You might receive the following error while trying to access a Siebel application version 7.5.x or earlier through a Siebel Web client:

The server you are accessing is either busy or experiencing difficulties. Please close the web browser, start a new one and try logging in again. For further support, please copy and send the full message text to your system administrator.[hh:mm:ss]

In Siebel Business Application version 7.7 or later, the error message that is returned through the Siebel Web client is:

The server you are trying to access is either busy or experiencing difficulties. Please close the Web browser, open a new browser window, and try logging in again. [hh:mm:ss]

NOTE: Use the hh:mm:ss information from the error message above to search for the error in the SWEApp log file.

This FAQ provides information on how to troubleshoot and isolate why the login page does not open for a Siebel 7 web application.

The first thing to try is to recycle the whole environment:

1. • Stop the web server, Siebel server and Siebel gateway in the order specified.

2. • If you have Resonate installed, make sure that there are no scheduling rules in the dispatch manager after the Siebel server service has been shutdown. To confirm if there are any scheduling rules left, log into the Central Dispatch Manager, then go to the Scheduling Rules tab and review the screen to see if there are any scheduling rules present. If there are any, manually delete them and stop and restart the Resonate site.

3. • Restart the Siebel gateway, Siebel server, web server in the order specified.

4. • Try to log in using a Siebel web client after 2-5 minutes from starting the Siebel service. (Object Managers take some time to come up after the Siebel server service has been started).

page 1 of 8 FAQ 1773: What Are the Steps To Troubleshoot the Error Message: "The Server You Are Accessing is Either Busy or Experiencing Difficulties…" in a Siebel 7 Web Client User Browser?

When you type in the URL for a particular Siebel application, the following happens:

1. • The browser sends a request to the Web server.

2. • The web server accesses the Virtual directory according to the URL.

3. • The Web server then communicates with the SWSE (Siebel Web Server Extension).

4. • The SWSE then uses the settings from the eapps.cfg file (Like AnonUserName / AnonUserPassword and the application connect string) to connect to the appropriate Siebel gateway, enterprise, server and then the Object manager.

5. • The Object manager accordingly starts tasks for the SWSE request.

Check that the appropriate Siebel gateway service and Siebel server services are up and running:

1. • Under Windows platform, navigate to the Start > Administrative Tools > Services and query for the appropriate Siebel services to see if they are running.

2. • Under UNIX platform, use the commands

list_ns or list_server siebel_server_name to see if the Siebel services are running.

Now check the following:

1. Is the web server responding?

Type in the web server address in the browser address box:

http://webserver

See if the web server default page comes up (example: an "under construction" page will be seen on the IIS web server).

If this does not return a page, check if the web server has been installed and set up correctly and is running. Refer to the 3rd party Web Server documentation for further information.

2. Is the web server recognizing the request for the web engine plug-in?

Try using the following URL directly:

Siebel version 7.0.x

http://webserver/callcenter/

Siebel version 7.5.x or later

http://webserver/callcenter_enu/

Although the login URL will generally be in the form of an application directory, for example: http://yourserver/callcenter/, the request will eventually be changed to one for a particular "page" with the extension .swe, for example http://yourserver/callcenter/start.swe.

page 2 of 8 FAQ 1773: What Are the Steps To Troubleshoot the Error Message: "The Server You Are Accessing is Either Busy or Experiencing Difficulties…" in a Siebel 7 Web Client User Browser?

If you do not see the start.swe being added to the URL you typed in, then the web engine plug-in has probably not been configured correctly. You should make sure your SWSE environment has been configured properly based on the information in the Siebel Bookshelf version 7.5 > Siebel Server Installation Guide (for Microsoft Windows or UNIX) > Installing the Siebel Web Server Extension > Post-Installation Tasks for Siebel Web Server Extension > Adding a New Virtual Web Directory to IIS > starting with Step 10 Click the Configuration Button through Step 14 Add the SWEF extension.

3. Is the web engine plug-in able to receive the request from the web server?

Try using the following URL:

http://webserver/callcenter/_stats.swe

This will help test whether the web engine plug-in is loaded correctly and is able to process requests. The statistics page can be changed from the default _stats.swe by making the change to the StatsPage parameter in the eapps.cfg file in the SIEBEL_ROOT\SWEApp\BIN directory. For more information about reconfiguring the stats page, refer to Siebel Bookshelf version 7.5 > Siebel Server Administration Guide > Siebel Web Server Extension Stats Page > Configuring the Stats Page.

If this does not return the swe statistics page then the web server is misconfigured, or the plug-in was not installed correctly.

4. Is the web engine able to find a Siebel server?

Verify that the connect strings in the web engine’s eapps.cfg file (found in the SIEBEL_ROOT\SWEApp\BIN directory) are correct.

Siebel version 7.0.x or 7.5.x

ConnectString = Siebel.TCPIP.none.NONE://siebel101:2320/Siebel/eEventsObjMgr_enu/siebel2

Siebel version 7.0.x or 7.5.x environments with Resonate

ConnectString = Siebel.TCPIP.none.NONE://siebel101:2320/Siebel/eEventsObjMgr_enu

where:

Value	Description
Siebel.TCPIP	The networking protocol
none (first instance)	The encryption type chosen
NONE (second instance)	Data compression method chosen
Siebel101 (first instance)	Siebel Gateway alias chosen (or Virtual IP address (VIP) if using Resonate)
2320	Gateway Server/VIP listening port number
Siebel	Enterprise Server name chosen
eEventsObjMgr_enu	Relevant Object Manager (in this example, the eEvents Object Manager)
Siebel2 (second instance)	Siebel server alias chosen (This is blank if using Resonate)

page 3 of 8 FAQ 1773: What Are the Steps To Troubleshoot the Error Message: "The Server You Are Accessing is Either Busy or Experiencing Difficulties…" in a Siebel 7 Web Client User Browser?

Siebel version 7.7

ConnectString = Siebel.TCPIP.none.NONE://siebel101:2321/Siebel/eEventsObjMgr_enu

where:

Value	Description
Siebel.TCPIP	The networking transport protocol
none (first instance)	The encryption type chosen
NONE (second instance)	Data compression method chosen
Siebel101 (first instance)	Siebel Gateway alias chosen (or Virtual IP address (VIP) if using load-balanced)
2321	Gateway Server/VIP listening port number
Siebel	Enterprise Server name chosen
eEventsObjMgr_enu	Relevant Object Manager (in this example, the eEvents Object Manager)

1. 5. Is the Anonymous User information correct?

If this information is not specified in the individual Object Manager sections, the default Anonymous user credentials under the [Default] section are used.

6. Is the Siebel server running the application object manager that is being requested?

In a Microsoft Dos window navigate to SIEBEL_HOME\siebsrvr\bin directory to invoke the server manager command line utility. For more information about this utility, refer to FAQ 1352.

srvrmgr /g /e /u /p

2. a. Check the status of the Siebel server:

srvrmgr> list server

Here is the output from the list server command:

srvrmgr> list server

SBLSRVR_NAME HOST_NAME INSTALL_DIR SBLMGR_PID SV_DISP_STATE SBLSRVR_STATE START_TIME END_TIME SBLSRVR_STATUS

------------ ---------- ------------------ ---------- ------------- -------

------ ------------------- -------- ----------------------------------

kkurlandP475 kkurlandP4 D:\sea752\siebsrvr 1904 Running Running

2004-05-06 13:28:59 7.5.2.100 [15252] LANG_INDEPENDENT

page 4 of 8 FAQ 1773: What Are the Steps To Troubleshoot the Error Message: "The Server You Are Accessing is Either Busy or Experiencing Difficulties…" in a Siebel 7 Web Client User Browser?

1. b. Check the status of the component on that server:

svrrmgr> list comp