Applies to:
Siebel System Software - Version: 7.5.3 [16157] and later [Release: V7 and later ]Information in this document applies to any platform.
Error Message Area:Generic - GEN
Version:Siebel 7.7
Purpose
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-GEN-05009: Unable to connect to the gateway server.Scope
This document is informational and intended for any user.SBL-GEN-05009: Unable to connect to the gateway server.
Explanation
Could not establish a connection to the gateway.Below is a list of common causes for this error message:
1. The Siebel Gateway Name Server service may not be running.
2. Incorrect entries in the connect string (in the SWEAPP_ROOT\bin\eapps.cfg file) for the gateway server host name or port number.
3. The Siebel Server service may not be running.
4. Siebel Web Server Extension reports this error on Solaris 2.8 with iPlanet as the web server with certain kernel versions and under heavy load. Please refer to Doc ID 477725.1 for more information about the affected Siebel versions and Solaris kernel versions. The cause of this error is due to the Solaris hard limit on the number of file descriptors that can be opened per process with the fopen function (256).
5. Incorrect values for the DSConnectString and DSGatewayAddress named subsystem parameters in Siebel versions 7.5.3.x or earlier would cause this error to appear when users try to access the Server Administration screens.
Corrective Action
Verify that the gateway is running and restart it if necessary.Below is a list of corrective actions to try to resolve this error message:
1. Ensure the Siebel Gateway Name Server is running. Refer to the following Siebel Bookshelf reference:
Siebel System Administration Guide > Administering Server System Services > Administering the Siebel Gateway Name Server System Server > Siebel Gateway Name Server System Service on (Windows OR UNIX).
2. Correct the ConnectString parameter In the SWEAPP_ROOT\bin\eapps.cfg file (on UNIX in the SWEAPP_ROOT/bin/eapps.cfg) which contains the gateway server host name and port number.
ConnectString = siebel.TCPIP.none.None://dedwards5:2320/Siebel/SalesCEObjMgr_enu/SiebSrvr1
NOTE: In the above example, dedwards5 is the gateway server host name and 2320 is the port number. SalesCEObjMgr_enu is the name of the component and SiebSrvr1 is the name of the Siebel Server.
For information about the ConnectString parameter, refer to the following Siebel Bookshelf references:
a. Siebel version 7.5.3 > Siebel Server Installation Guide for (UNIX or Windows) > Structure of the eapps.cfg File > Editing the Web Server Extension Configuration File.
b. Siebel version 7.7 > Siebel System Administration Guide > Structure of the eapps.cfg File.
c. Siebel version 8.x > Siebel Installation Guide > Installing and Configuring the Siebel Web Server Extension > Postinstallation Tasks for the SWSE and the Web Server >
Editing the SWSE Configuration File (eapps.cfg)
3. Ensure the Siebel Server is running. Refer to the following Siebel Bookshelf reference:
Siebel System Administration Guide > Administering Server System Services > Administering the Siebel Server System Service > Siebel Server System Service on (Windows OR UNIX).
4. Ensure the Solaris 2.8 with iPlanet as the web server is running kernel patch 108528-24 or later. If you are unable to apply this kernel patch, make sure the nscd daemon is running which seems to temporarily work around this behavior. For more information refer to Doc ID 477725.1 .
5. Check the values for the DSConnectString and DSGatewayAddress named subsystem parameters. Try to ping the machine using these values. In some cases, try the fully qualified name for the Siebel Gateway host name like 'abc.xyz.us'.
Applies to:
Siebel System Software - Version: 7.0.4 [14068] and later [Release: V7 and later ]Oracle Solaris on SPARC (64-bit)
Oracle Solaris on SPARC (32-bit)
Solaris Operating System (SPARC 64-bit)Solaris Operating System (SPARC 32-bit)
Area(s):System Administration
Release(s):V7 (Enterprise), V7 (MidMarket)
Database(s):All Supported Databases
App Server OS(s):Solaris
Latest release tested against:V7 (Enterprise)
Keywords:SBL-GEN-05009, Unable to connect to gateway server, Solaris, iplanet, kernel, SBL-UIF-00272
This document was previously published as Siebel Alert 996.
Description
When running Siebel version 7.0.x and 7.5.x on Solaris 2.8 with iPlanet as the web server, iPlanet's httpd process makes calls to gethostbyname function, which is implemented using the fopen function in Solaris kernel patches prior to 108528-24.Solaris has a hard limitation on the number of file descriptors that can be opened per process with the fopen function (256). When the httpd process runs out of available file descriptors, users will be unable to log in to the Siebel application and errors will be reported in the SWE log file.
Solaris has a name service cache daemon called nscd that runs by default. When the nscd daemon is running, it caches the hostname details. When gethostbyname is called, it gets this data from this cache. Having the nscd daemon running will prevent the above behavior. Please note that the above behavior does not occur when Resonate is being used in the environment.
Likelihood of Occurrence
This specific behavior has been seen under the following conditions:- Using Siebel version 7.0.x or 7.5.x on Solaris with an iPlanet web server
- The iPlanet web server is running kernel patch 108528-23 or lower.
- The nscd daemon is not running.
- Resonate is not being used.
- The servers are under heavy load.
Possible Symptoms
Siebel Web Clients will be able to log in and work normally until all file descriptors are exhausted. After this, all new login attempts will receive the following error, even though the correct username and password have been supplied:
SBL-UIF-00272: The user ID or password that you entered is incorrect.
Please check the spelling and try again.
Analysis of the SWE log files named swenesPID.log (where PID is the
UNIX process ID of the web server) found in the SIEBEL_ROOT/swe/log
directory will show the following error: GenericLog GenericError 1 2003-11-26 21:28:16 NSC - ErrCode 5009 SysErr 0 GenericLog GenericError 1 2003-11-26 21:28:16 (scbconn.cpp 5(107) err=5009 sys=0) SBL-GEN-05009 Unable to connect to gateway server
Please note that if some users log out of the application, which frees up some file descriptors, the behavior will rectify itself for a short time. However, it will reoccur if the file descriptors become exhausted again.
Workaround or Resolution
One possible workaround for this behavior is to make sure that the nscd daemon is running on the iPlanet web server machine.With Solaris kernel patch 108528-24 and above, the implementation of gethostbyname has been changed by Sun Microsystems, so the 255 file descriptor limit is no longer applicable. To resolve this behavior apply the Solaris kernel patch 108528-24 or above, which can be downloaded from the following link, to all web server machines running the iPlanet web server.
SunOS 5.8: kernel update patch 108529At the page accessed from the above link, search for the description below:
4353836 if more than 255 file descriptors are already open then gethostbyname fails
Applies to:
Error Message Area:Generic - GENVersion:Siebel 7.5.3
Purpose
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-GEN-05009: Unable to connect to gateway serverScope
This document is informational and intended for any user.SBL-GEN-05009: Unable to connect to gateway server
Explanation
Could not establish a connection to the gateway.Below is a list of common causes for this error message:
1. The Siebel Gateway Name Server service may not be running.
2. Incorrect entries in the connect string (in the SWEAPP_ROOT\bin\eapps.cfg file) for the gateway server host name or port number.
3. The Siebel Server service may not be running.
4. Siebel Web Server Extension reports this error on Solaris 2.8 with iPlanet as the web server with certain kernel versions and under heavy load. Please refer to Alert 996 for more information about the affected Siebel versions and Solaris kernel versions. The cause of this error is due to the Solaris hard limit on the number of file descriptors that can be opened per process with the fopen function (256).
5. Incorrect values for the DSConnectString and DSGatewayAddress named subsystem parameters in Siebel versions 7.5.3.x or earlier would cause this error to appear when users try to access the Server Administration screens.
Corrective Action
Verify that the gateway is running and restart it if necessary.Below is a list of corrective actions to try to resolve this error message:
1. Ensure the Siebel Gateway Name Server is running. Refer to the following Siebel Bookshelf references:
a. Siebel version 7.7 > Siebel System Administration Guide > Administering Server System Services > Administering the Siebel Gateway Name Server System Server > Siebel Gateway Name Server System Service on (Windows OR UNIX).
b. Siebel version 7.5.3 > Siebel Server Administration Guide > Server System Services > Administering the Siebel Gateway System Service > Siebel Gateway System Service on (Windows OR UNIX).
2. Correct the ConnectString parameter In the SWEAPP_ROOT\bin\eapps.cfg file (on UNIX in the SWEAPP_ROOT/bin/eapps.cfg) which contains the gateway server host name and port number.
ConnectString = siebel.TCPIP.none.None://dedwards5:2320/Siebel/SalesCEObjMgr_enu/SiebSrvr1
NOTE: In the above example, dedwards5 is the gateway server host name and 2320 is the port number. SalesCEObjMgr_enu is the name of the component and SiebSrvr1 is the name of the Siebel Server.
For information about the ConnectString parameter, refer to the following Siebel Bookshelf references:
a. Siebel version 7.5.3 > Siebel Server Installation Guide for (UNIX or Windows) > Structure of the eapps.cfg File > Editing the Web Server Extension Configuration File.
b. Siebel version 7.7 > Siebel System Administration Guide > Structure of the eapps.cfg File.
3. Ensure the Siebel Server is running. Refer to the following Siebel Bookshelf references:
a. Siebel version 7.7 > Siebel System Administration Guide > Administering Server System Services > Administering the Siebel Server System Service > Siebel Server System Service on (Windows OR UNIX).
b. Siebel version 7.5.3 > Siebel Server Administration Guide > Server System Services > Administering the Siebel Server System Service > Siebel Server System Service on (Windows OR UNIX).
4. Ensure the Solaris 2.8 with iPlanet as the web server is running kernel patch 108528-24 or later. If you are unable to apply this kernel patch, make sure the nscd daemon is running which seems to temporarily work around this behavior. For more information refer to Alert 996.
5. Check the values for the DSConnectString and DSGatewayAddress named subsystem parameters. Try to ping the machine using these values. In some cases, try the fully qualified name for the Siebel Gateway host name like 'abc.xyz.us'.
Applies to:
Siebel System Software - Version: 7.7.2 [18325] and later [Release: V7 and later ]HP-UX Itanium
Product Release: V7 (Enterprise)
Version: 7.7.2 [18325]
Database: Oracle 9.2
Application Server OS: HP-UX 11.11
Database Server OS: HP-UX 11.11
This document was previously published as Siebel SR 38-1967171771.
Symptoms
SBL-GEN-05004, SBL-ICF-00018 Our database file was filled up around 1:07AM last night possibly causing our Siebel Server to fail. While troubleshooting this morning, we’ve shutdown the Siebel Server and Gateway Server and received (hand translated from Chinese) “Not Started: Unable to copy service item files into memory” when attempting to restart Gateway server.The database size has since been extended, however, we still continue to receive this error.
We have tried the following:
- Delete and rebuild svc* file
- Verify all files are owned by Siebel user (and have read write permission to siebns.dat)
- Tried using an older version of siebns.dat
- Verify port 2320 is available
I have uploaded:
- screen shot of the error (in Chinese)
- Gateway logs
- enterprise server log
Any suggestions would be much appreciated
Cause
Configuration/ SetupSolution
For the benefit of other users, the customer received the following error message when attempting to restart their Siebel Gateway Server “Not Started: Unable to copy service item files into memory”Following the failed restart, they recreated the *.svc files by running a siebctl command but still could not start the Siebel Gateway Server and received “NameSrvr - [5018] (No message)” errors in the NameSrvr.log.
Summary:
Siebel does not recommend that customers should re-create the Siebel Gateway or Server services if there are problems starting any service. The reason Siebel does not recommend re-creating the Siebel Services is because they could be created incorrectly which then cause other issues. Customers are advised to raise a Service Request with Siebel Technical Support if assistance is required diagnosing why a Siebel service failed to start.
Further research found the siebctl syntax the customer used to create the Gateway Server service is the one specified in Service Request #38-1960105998 to create the Siebel Server service. The steps used to resolve this Service Request was:
1) Ensure the Siebel Server Service and Web Server services are offline
2) Run gtwysrvr\siebenv.sh
3) Stop the Gateway Server service (stop_ns)
4) Copy svc.gtwyns. in $SIEBEL_ROOT/gtwysrvr/sys to backup.svc.gtwyns.old
5) Delete the svc.gtwyns. file
6) Run the command siebctl -S gtwyns -a -g "/f $SIEBEL_ROOT/sys/siebns.dat /t 2320" substituting the port number for the Gateway Server service in place of 2320.
7) Start the Siebel Gateway service (start_ns)
8) Type list_ns
Applies to:
Siebel CRM - Version: 8.1.1 SIA [21111] - Release: V8Information in this document applies to any platform.
Symptoms
Unattended Siebel Server configuration fails.o Gateway has already been installed/configured and is up and running
o Database has also been installed
o Same error was encountered during a subsequent attempt to run the installation manually
Cause
It was established that the Siebel Server had been installed on an unsupported Operating System.o Using the Strace debugging tool to track system calls, it was established that an incorrect OS platform was in use:
sysname="Linux", nodename="apn0.ccbs6a.net", release="2.6.9-67.ELsmp", version="#1 SMP Wed Nov 7 13:56:44 EST 2007", machine="x86_64"
[siebel@apn0 bin]$ strace -f -v -o /tmp/server.confignew.log ./ssincfgw -is:javaconsole -console -args LANG=enu MODE=LIVE MODEL_FILE=/opt/siebel/siebsrvr/admin
n/siebel_server_sia.scm
Initializing InstallShield Wizard........
Extracting Bundled JRE.[ Process PID=24822 runs in 32 bit mode. ]
[ Process PID=24705 runs in 64 bit mode. ]
[ Process PID=24824 runs in 32 bit mode. ]
[ Process PID=24826 runs in 64 bit mode. ]
[ Process PID=24824 runs in 32 bit mode. ]
[ Process PID=24826 runs in 64 bit mode. ]
[ Process PID=24824 runs in 32 bit mode. ]
and then,
21156 execve("/bin/awk", ["awk"..., "END { i=index(a, \"-is:in\"); prin"..., "a=-args"...], ["SYSTEM_ARCHIVE=/mnt/global_backu"..., "EV_AGENTID_DIRECTORY=/etc/Navisp"..., "ORACLE_INSTALL=/opt/cbuPlatform_"..., "HOSTNAME=apn0.ccbs6a.net"..., "ASM_HOME=/opt/oracle/product/10."..., "SHELL=/bin/bash"..., "TERM=xterm"..., "HISTSIZE=1000"..., "SYSTEM_HOME=/home/ccbs"..., "SSH_CLIENT=131.207.209.109 4846 "..., "BPEL_HOME=/opt/oracle/jdevstudio"..., "ORACLE_CLUSTERWARE_NODES=dbn-0 d"..., "SYSTEM_PROVIDER=nokiasiemensnetw"..., "SYSTEM_VAR=/var/opt/nokiasiemens"..., "SSH_TTY=/dev/pts/2"..., "SYSTEM_DATA=/var/opt/nokiasiemen"..., "ANT_HOME=/opt/oracle/jdevstudiob"..., "USER=siebel"..., "SIEBEL_WEB_SERVER_EXTENSION_NODE"..., "JRE_HOME=/usr/java/jdk1.6.0_06/j"..., "LS_COLORS=no=00:fi=00:di=00;34:l"..., "LD_LIBRARY_PATH=/opt/siebel/sieb"..., "ORACLE_SID=CRM"..., "ORACLE_CLIENT_NODES=apn0 apn1 ap"..., "SIEBEL_SERVER_NODES=apn0"..., "ORACLE_BASE=/opt/oracle"..., "ORACLE_EBS_NODES=apn2 apn3"..., "SYSTEM_RUN=/var/opt/nokiasiemens"..., "PATH=/usr/local/bin:/bin:/usr/bi"..., "MAIL=/var/spool/mail/siebel"..., "TNS_ADMIN=/etc/opt/nokiasiemensn"..., "SYSTEM_TYPE=CCBS"..., "ORACLE_AIA_NODES=apn4"..., "PWD=/opt/siebel/siebsrvr/bin"..., "INPUTRC=/etc/inputrc"..., "DBN_NODES=dbn-0 dbn-1"..., "JAVA_HOME=/usr/java/jdk1.6.0_06"..., "SYSTEM_STORAGE_MULTIPATHING_SW=D"..., "SYSTEM_CLASSPATH="..., "LANG=en_US.UTF-8"..., "ORACLE_WEB_SERVER_NODES=apn0"..., "SYSTEM_USERGROUP=ccbs"..., "HOME=/home/siebel"..., "SHLVL=2"..., "SYSTEM_SW_BUILD_LOCATION=local"..., "SYSTEM_STORAGE_ARRAY=emc-via-fc"..., "SYSTEM_USER=ccbs"..., "SYSTEM_LOG=/var/opt/nokiasiemens"..., "LOGNAME=siebel"..., "SIEBEL_GATEWAY_NODES=apn0"..., "SSH_CONNECTION=131.207.209.109 4"..., "CLASSPATH=/opt/siebel/siebsrvr/b"..., "ORACLE_SOA_NODES=apn4"..., "LESSOPEN=|/usr/bin/lesspipe.sh %"..., "SYSTEM_ETC=/etc/opt/nokiasiemens"..., "APN_NODES=apn0 apn1 apn2 apn3 ap"..., "SYSTEM_OPT=/opt/nokiasiemensnetw"..., "DISPLAY=localhost:10.0"..., "ORACLE_DATABASE_NODES=dbn-0 dbn-"..., "ORACLE_HOME=/opt/oracle/product/"..., "G_BROKEN_FILENAMES=1"..., "HISTTIMEFORMAT=%F %T "..., "_=/bin/awk"...]) = 0
21156 uname({sysname="Linux", nodename="apn0.ccbs6a.net", release="2.6.9-67.ELsmp", version="#1 SMP Wed Nov 7 13:56:44 EST 2007", machine="x86_64"}) = 0
Solution
In line with recommended guidelines ('Siebel System Requirements and Supported Platforms Version 8.1', p31), the only Linux-based Operating Systems that are currently supported are:o Red Hat Enterprise Linux 4 (32-bit)
o Novell SUSE Linux Enterprise Server 9 (32-bit)
o Oracle Enterprise Linux 4 Kernel level 2.6.9-42.0.0.0.1 (32-bit) and Oracle Enterprise Linux 5 kernel level 2.6.18-53el5 (32-bit) .
Applies to:
Siebel CRM Call Center - Version 8.2.2 SIA[22320] to 8.2.2 SIA[22320] [Release V8]Linux x86-64
Symptoms
The issue occurs when installing Siebel 8.2.2 on Linux version 6 update 0 or above (64bit).After running the Siebel configuration wizard -> Configured a new Gateway name server, the following error shows:
"Unable to connect to Siebel Gateway Name Server".
Siebel Gateway log shows:
Location: siebel_root/gtwysrvr/log/siebel.log
[TCPIP-client]
failed to resolve hostname: SDCR710I006E (err=852198 | Internal:
gethostbyname_r ()failed with error. (%sysError))
NameServerLayerLog Error 1 000000024f4c19ce:0 2012-02-28 09:36:10 Unable to connect to the gateway server.
GenericLog GenericError 1 000000024f4c19ce:0 2012-02-28 09:36:10 NSC -
ErrCode 5009 SysErr 0GenericLog GenericError 1 000000024f4c19ce:0
2012-02-28 09:36:10 (srvredit2.cpp (302) err=5009 sys=1) SBL-GEN-05009:
Unable to connect to the gateway server.Cause
The cause of the problem could be associated to the hostname indeed not been resolved.By default the file host.conf, located in /etc/host.conf, has the "multi on" option set.
As an example the host.conf should look like:
multi on
order hosts,bind
Note: "The multi option determines whether a host
in the /etc/hosts file can have multiple IP addresses i.e.multiple
interface ethN. Hosts that have more than one IP address are said to be
multiomed, because the presence of multiple IP addresses implies that
host has several network interfaces. As an example, a Gateway Server
will always have multiple IP address and must have this option set to
ON."
Solution
The workaround solution is to set the following environment variable to override the "multi on" option on the host.conf file. This has to be disabled in the session that starts the Wizard.1. export RESOLV_MULTI=off
Note: Make sure to use a port # lower than 32767.
2. Remove any previous installations from directory siebel_root/gtwysrvr/sys.
Run commands:
cd /home/siebel/gtwysrvr/sys
rm siebns*
rm svc.gtwyns*3. Run the Siebel configuration Wizard.
Note: Detail logs from the Siebel installation can be generated using the parameter "-verbose"
BUG:13784383 has been created.
Applies to:
Siebel Call Center - Version: 8.1.1.2 SIA[21215] and later [Release: V8 and later ]Information in this document applies to any platform.
Symptoms
Siebel Servers suddenly did not start any more, even though there was no change in the Siebel environment.SiebSrvr_28.log
immediately after benign errors like
SBL-SCC-00025: No value found in the Gateway. Default value in the repository is used.
(which means the Gateway Server can be contacted successfully, but the parameter requested is not set, so its default is used)
there were
SBL-GEN-05009: Unable to connect to the gateway server.
like
NameServerLayerLog Error 1 000024ec4c494b91:0 2010-07-23 08:26:43 Unable to connect to the gateway server.
GenericLog GenericError 1 000024ec4c494b91:0 2010-07-23 08:26:43 NSC - ErrCode 5009 SysErr 0
GenericLog GenericError 1 000024ec4c494b91:0 2010-07-23 08:26:43 (listener.cpp (184) err=5009 sys=0) SBL-GEN-05009: Unable to connect to the gateway server.
GenericLog GenericError 1 000024ec4c494b91:0 2010-07-23 08:26:43 (lstnsvc.cpp (150) err=5009 sys=0) SBL-GEN-05009: Unable to connect to the gateway server.
while the Gateway was still running,
and netstat output confirmed it was listening on its configured port (default: 2320)
Cause
Setting the Unix environment variableSIEBEL_LOG_EVENTS=5; export SIEBEL_LOG_EVENTS
in the siebenv.sh
prior to starting the Gateway Server
(in Windows, you would set the SYSTEM environment variable SIEBEL_LOG_EVENTS=5 prior to starting the Gateway Server instead)
showed the problem in the NameSrvr.log (NameSrvr_01.log here)
in
<Gateway Root>
there were about 500 entries like
SecAdptLog Debug 5 00001d2b4c495cb8:0 2010-07-23 09:49:05 username=oemxyz : authentication succeeded.
SecAdptLog Debug 5 00001d2b4c495cb8:0 2010-07-23 09:49:05 username=oemxyz : retrieving responsibilities...
per minute (the user name would reflect the username your monitoring script uses to invoke srvrmgr behind the /u (user) command line switch)
Temporarily disabling access for
DB user
oemxyz
made the logins error out, but the Siebel Servers could be started correctly again,
so this was considered the root cause.
The monitoring tool used causes about 8 ODBC connections to be opened (and closed) every second,
which seems to max out the Gateway's connections to the database
SiebSrvr_28.log
first shows 160
SBL-SCC-00025
GenericLog GenericError 1 00027c704c497cd9:0 2010-07-23 08:26:43 (sccnmsys.cpp (1305) err=2883609 sys=0) SBL-SCC-00025: No value found in the Gateway. Default value in the repository is used.
which means the gateway has been contacted and keys could be search (just no value found)
before this starts failing and a new connection cannot be made any more either
GenericLog GenericError 1 00027ea84c497cd9:0 2010-07-23 08:26:43 (sccnmsys.cpp (1305) err=2883609 sys=0) SBL-SCC-00025: No value found in the Gateway. Default value in the repository is used.
GenericLog GenericError 1 00027ea94c497cd9:0 2010-07-23 08:26:43 (sccitems.cpp (310) err=2555932 sys=0) SBL-SCM-00028: Key not found
GenericLog GenericError 1 00027ea94c497cd9:0 2010-07-23 08:26:43 (sccconfg.cpp (2149) err=2555932 sys=0) SBL-SCM-00028: Key not found
NameServerLayerLog Error 1 000024ec4c494b91:0 2010-07-23 08:26:43 Unable to connect to the gateway server.
GenericLog GenericError 1 000024ec4c494b91:0 2010-07-23 08:26:43 NSC - ErrCode 5009 SysErr 0
GenericLog GenericError 1 000024ec4c494b91:0 2010-07-23 08:26:43 (listener.cpp (184) err=5009 sys=0) SBL-GEN-05009: Unable to connect to the gateway server.
GenericLog GenericError 1 000024ec4c494b91:0 2010-07-23 08:26:43 (lstnsvc.cpp (150) err=5009 sys=0) SBL-GEN-05009: Unable to connect to the gateway server.
GenericLog GenericError 1 000024ec4c494b91:0 2010-07-23 08:26:43 (scfsis.cpp (274) err=1310725 sys=0) SBL-SVR-00005: Stale or invalid Task handle
ScfEventLog SubEvtFacFatal 0 000024ec4c494b91:0 2010-07-23 08:26:43 scfEventFac::s_pEvtFacLock is NULL and hence SCF event facility cannot be initialised
GenericLog GenericError 1 000024ec4c494b91:0 2010-07-23 08:26:43 (scfeventfac.cpp (3790) err=1319869 sys=0) SBL-SVR-09149: Could not initialize the event facility.
ScfMsgFacLog SCFMsgFacFatalError 0 000024ec4c494b91:0 2010-07-23 08:26:43 SCFMessageFacility::s_pSCFMsgFacLock is null and hence the SCFMessageFacility cannot be initialized
IPCLog IPCFatal 0 000024ec4c494b91:0 2010-07-23 08:26:43 ipcFacility GetInstance called before initialization - object is null
GenericLog GenericError 1 000024ec4c494b91:0 2010-07-23 08:26:53 (siebsvc.cpp (221) err=5009 sys=0) SBL-GEN-05009: Unable to connect to the gateway server.
Solution
If you are using monitoring scripts that connect to srvrmgr,reduce the number of srvrmgr invocations of the monitoring tool
to for example once per minute per Siebel Server
also, don't forget to reduce the logging by removing
SIEBEL_LOG_EVENTS=5; export SIEBEL_LOG_EVENTS
from the Gateway Server's siebenv.sh file
(or changing the Windows SYSTEM environment variable SIEBEL_LOG_EVENTS to 1)
to reduce the logging again.
PS: If without any changes you suddenly see the error
SBL-GEN-05009: Unable to connect to the gateway server.
in 8.1.1. and above
(all of a sudden without using monitoring tools as described here)
and this happens to be 14 days after the installation, you may want to take a look at
Siebel CRM 8.1.1 DataDirect License file IVSE.LIC is missing from Gateway Name Server
instead - this was ruled out as a root cause in the beginning of this service request
References
NOTE:751784.1 - Siebel CRM 8.1.1.x: Two weeks after installation, Siebel server cannot start and srvrmgr returns: Fatal error (2555922)Applies to:
Siebel CRM - Version: 8.1.1 SIA [21111] and later [Release: V8 and later ]Information in this document applies to any platform.
***Checked for relevance on 17-Feb-2012***
Symptoms
The Gateway daemon for Siebel Industry Applications version 8.1.1 running on IBM AIX 5.3 against Oracle 11g shows high CPU. This can be observed after starting a Siebel server, which has a duration of 2-3 minutes. After the Siebel server has started the CPU of the Gateway daemon reduces and stabilizes, however the Siebel Workflow components fail after startup. If these failed components are restarted manually via Siebel Server Manager then the CPU increases on the Gateway as before.ERROR MESSAGES
- SBL-DAT-00173: An invalid key was entered.
- SBL-NET-01218: The connection was refused by server %1. No component is listening on port %2.
- SBL-SRB-00040: Cannot open asynchronous SISNAPI connection.
- SBL-GEN-05009: Unable to connect to the gateway server.
- SBL-SVR-00052: Internal: Invalid proc handle
Cause
Issue caused by extremely large SIEBNS.DAT which can be seen by the high CPU in the gateway process originating from the reads performed by the NSClient.Bug 10643323 has been logged to address a Product Enhancement Request so that the size of the SIEBNS.DAT does not grow excessively and if it does then to provide means to reduce the size - in particular removing event log level entries.
The large amounts of reads being performed by the NSClient are directly related to the high CPU observed on the gateway
Solution
To reduce the size of the SIEBNS.DAT, the following can be employed to resolve the issue:1. Restore backup of SIEBNS.DAT after changing event log levels for large amount of server components
2. Remove unnessary component definitions
No comments:
Post a Comment