Do you want to Search Something?

Those who opened the gates

Wednesday, July 4, 2012

Fix C028: “Unable to Connect to the Siebel Gateway Name Server”

Symptoms

The Server Configuration wizard has logged the following error message:
C028: Unable to Connect to the Siebel Gateway Name Server

Cause
Database Authentication failed.
Gateway authentication is a new feature in Siebel 8.1.1.  If the Configuration Wizard fails due to authentication it will log the error messages, above.

Solution

Follow these steps to resolve the issue:

1. In the ‘$SIEBEL_ROOT/gtwysrvr/siebenv.sh’ environment sourcing script, check the following environment variables and  set them appropriately before starting the Gateway server.
1a. For all servers: ORACLE_HOME must be declared before any library paths are declared.
Example:
ORACLE_HOME=/export/home/ora10g/10203 ; export ORACLE_HOME
1b. NOTE: For the following library paths, Oracle 32-bit libraries must be referenced before 64-bit libraries. An example is provided for each library path per Unix system, as follows:
For AIX: LIBPATH
LIBPATH=${SIEBEL_ROOT}/lib:${MWHOME}/lib:${SQLANY}/lib:/usr/lib:${LIBPATH}:${ORACLE_HOME}/lib32:${ORACLE_HOME}/lib
For HP-UX:  SHLIB_PATH
SHLIB_PATH=/usr/lib/hpux32:${SIEBEL_ROOT}/lib:${MWHOME}/lib:${SQLANY}/lib:${ORACLE_HOME}/lib32:${ORACLE_HOME}/lib
For Linux and Solaris:  LD_LIBRARY_PATH
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${ORACLE_HOME}/lib32:
${ORACLE_HOME}/lib
2. Open the ‘gateway.cfg’ file, which is located in the ‘$SIEBEL_ROOT/gtwysrvr/bin’ directory.
Check the ‘ServerDataSrc’ section and confirm the parameters are correct, particularly:
ConnectString
TableOwner
GatewayAddress
EntepriseServer
3. Test Siebel database connectivity using the Oracle odbcsql utility for the ‘sadmin’ user.  This is typically located in the ‘$IEBEL_ROOT/siebsrvr/bin’ directory.
For example:
odbcsql /s sia811_DSN /u sadmin /p sadmin
where:
/s = the source ODBC DSN (the Siebel ConnectString parameter) for the database connection.
/u = the user ID.
/p = the password.
If connection is possible, continue with step 4.
4. Restart the Gateway server, and then try configuring the Siebel Server.

Hope that helps !!!! have a nice day

2 comments:

Anonymous said...

Did you check if you had a 32 bit or 64 bit Oracle Client?

Anonymous said...

I have checked everything followed all the steps , still it sucks ,even tried to install it from scratch twice :-(..

Although what surprises me is that in past 4 days I have done the installation set up on 3 different servers and they all ran smoothly without running into it creepy error.