Applies to:
Siebel Life Sciences CRM - Version: 8.1 [21039] to 8.1.1 [21112] - Release: V8 to V8
Microsoft Windows (32-bit)
Symptoms
Customer changed the sadmin's password following the Siebel
Security Guide > Changing or Adding Passwords > Changing Passwords
> Changing System Administrator Passwords on Microsoft Windows, but
after changing the password the Siebel Server did not come up .
In the Siebsrvr.log file it was found the following error message:
GenericLog GenericError 1 00000002499b0e08:0 2009-02-17 16:41:28
(scmnsclnt.cpp (135) err=2555922 sys=0) SBL-SCM-00018: Could not open
connection to Siebel Gateway configuration store (siebel03:2320).
The following errors were just a symptom of the failure to connect to the Siebel Gateway:
GenericLog GenericError 1 00000002499b0e08:0 2009-02-17 16:41:28
(scisvc.cpp (1391) err=1311765 sys=0) SBL-SVR-01045: No components are
configured.
GenericLog GenericError 1 00000002499b0e08:0
2009-02-17 16:41:28 (scfsis.cpp (274) err=1310725 sys=0) SBL-SVR-00005:
Stale or invalid Task handle
ScfEventLog SubEvtFacFatal 0
00000002499b0e08:0 2009-02-17 16:41:28 scfEventFac::s_pEvtFacLock is
NULL and hence SCF event facility cannot be initialised
GenericLog
GenericError 1 00000002499b0e08:0 2009-02-17 16:41:28 (scfeventfac.cpp
(3790) err=1319869 sys=0) SBL-SVR-09149: Could not initialize the event
facility.
ScfMsgFacLog SCFMsgFacFatalError 0 00000002499b0e08:0
2009-02-17 16:41:28 SCFMessageFacility::s_pSCFMsgFacLock is null and
hence the SCFMessageFacility cannot be initialized
IPCLog IPCFatal 0 00000002499b0e08:0 2009-02-17 16:41:28 ipcFacility GetInstance called before initialization - object is null
GenericLog GenericError 1 00000002499b0e08:0 2009-02-17 16:41:28
(scfsis.cpp (64) err=1310749 sys=0) SBL-SVR-00029: Internal: Shared
memory has not been initialized.
Cause
The issue was due to the new security feature that was introduced
on Siebel 8.1.1 to avoid access to the Gateway Server without being
properly authenticated.
There are now in Siebel 8.1.1 user and password information in the
Windows registry for the Siebel Server service. This can be verified by
on "Path to executable:" field on General tab for the respective Siebel
Server service in Administrative Tools > Services. See the example
below:
C:\sia81\siebsrvr\bin\siebsvc -s siebsrvr -i Siebel_app01 -a "-g
localhost:2320 -e Siebel -s app01 -l ENU -u SADMIN -ep 9ntkUOUf" -t 120
-h C:\sia81\siebsrvr
Solution
Follow the instructions below to reflect the sadmin's password to all
Siebel Serves in the Enterprise, i.e. repeat the process on all Siebel
Servers in the Enterprise.
a) Delete the Siebel Server service
syntax:
siebctl -d -S siebsrvr -i "<enterprise name>_<siebel server name>"
example:
C:\sia81\siebsrvr\bin\siebctl -d -S siebsrvr -i "sia81_app01"
b) Restart the machine
c) Recreate the Siebel Server service providing the new password, it will be encrypted by siebctl.
syntax:
siebctl
-h %SIEBEL_ROOT% -S siebsrvr -i "<enterprise name>_<siebel
server name>" -a -g "-g <gateway hostname>:<port#> -e
<enterprise name -s <siebel server name> -u sadmin" -e <new
password> -u <NT Account> -p <NT password>
example:
C:\sia81\siebsrvr\BIN>siebctl
-h "d:\sia81\siebsrvr" -S siebsrvr -i "sia81_app01" -a -g "-g
localhost:2320 -e sia81 -s app01 -u sadmin" -e sadmin -u .\SADMIN -p
SADMIN
d) Restart the machine
NOTE: If no local user account is used, i.e. Local System is used instead, don't use -u and -p options
NOTE 2:
After recreating the service using siebctl and restarting the machine,
you may receive a failed logon message when starting the service. If
this happens navigate to Windows Control Panel, Services list, locate
the Siebel Server service and click on Properties. Under the "Log On"
tab re-enter the password for the service owner account.
Below is the updated documentation as a result of the document bug 10561582:
http://download.oracle.com/docs/cd/E14004_01/books/Secur/Secur_ChangePwd3.html
Applies to:
Siebel CRM - Version: 8.0 [20405] to 8.1 [21039] - Release: V8 to V8
Information in this document applies to any platform.
*** Checked for Relevance 15 Feb 2012 ***
Symptoms
Siebel Server failed to start.
- No new enterprise log was created
- Siebel Server log contained the following errors:
(SiebSrvr.log)
2010-07-13 15:03:33 1: [TCPIP-client] socket() closed descriptor = 8 from 10.1.1.51:49976 to 10.1.1.51:2320
2010-07-13 15:03:33 (scfsis.cpp (80) err=2555932 sys=0) SBL-SCM-00028: Key not found
2010-07-13 15:03:33 (listener.cpp (172) err=2555932 sys=0) SBL-SCM-00028: Key not found
2010-07-13 15:03:33 (lstnsvc.cpp (150) err=2555932 sys=0) SBL-SCM-00028: Key not found
2010-07-13 15:03:33 (scisvc.cpp (1391) err=1311765 sys=0) SBL-SVR-01045: No components are configured.
2010-07-13 15:03:33 (scfsis.cpp (274) err=1310725 sys=0) SBL-SVR-00005: Stale or invalid Task handle
2010-07-13 15:03:33 scfEventFac::s_pEvtFacLock is NULL and hence SCF event facility cannot be initialised
2010-07-13 15:03:33 (scfeventfac.cpp (3790) err=1319869 sys=0) SBL-SVR-09149: Could not initialize the event facility.
2010-07-13 15:03:33 SCFMessageFacility::s_pSCFMsgFacLock is null and hence the SCFMessageFacility cannot be initialized
2010-07-13 15:03:33 ipcFacility GetInstance called before initialization - object is null
2010-07-13 15:03:33 (scfsis.cpp (64) err=1310749 sys=0) SBL-SVR-00029: Internal: Shared memory has not been initialized.
Cause
Siebel Server definition is missing from Siebel Gateway Name Server Data file (siebns.dat).
At startup, the Siebel Server obtains its configuration information
from the Siebel Gateway Name Server's siebns.dat file. Refer to the
following 8.x Siebel System Administration Guide bookshelf document for
more information:
Solution
Either of the following actions should resolve the issue:
A. Restore a copy of the Gateway Name Server backup file (siebns.dat).
B. Configure a "new" Siebel Server, by running the configuration wizard.
Applies to:
Siebel CRM - Version 8.1.1 SIA [21111] and later
Generic Linux
Generic UNIX
Affected Database: Oracle
""Checked for Relevance on 11-09-2012""
Symptoms
start_server script (for staring Siebel Server) or srvrmgr command
may fail and the error message in NameSrvr.log file indicates "
SBL-SEC-10007: The password you have entered is not correct. Please
enter your password again." while the same user/password combination
works on SQLPlus.
Cause
In Siebel 8.1.x, Siebel Gateway Server (GtwySrvr) authenticates the
user who attempts to connect to GtwySrvr. In standard setting, GtwySrvr
performs database authentication against the user. Using Oracle
database, $ORACLE_HOME/lib (or $ORACLE_HOME/lib32 when Oracle Database
Server is 64 bit) must be part of the shared libraries for GtwySrvr
process (siebsvc). If it is not set correctly, starting Siebel Server
(start_server script) or launching srvrmgr will fail with following
errors..
1) start_server
- On terminal window, it does not show any error but list_server scripts reveals it is stopped in a few seconds.
- SiebSrvr.log under siebsrvr/log directory shows following error.
SBL-SCC-00005: Internal:No more items found.
SBL-SVR-01045: No components are configured.
SBL-SVR-00005: Stale or invalid Task handle
scfEventFac::s_pEvtFacLock is NULL and hence SCF event facility cannot be initialised
SBL-SVR-09149: Could not initialize the event facility.
SCFMessageFacility::s_pSCFMsgFacLock is null and hence the SCFMessageFacility cannot be initialized
ipcFacility GetInstance called before initialization - object is null
SBL-SVR-00029: Internal: Shared memory has not been initialized.
- NameSrvr.log under gtwysrvr/log directory shows following error.
SBL-SEC-10018: 523 80
SBL-SEC-10007: The password you have entered is not correct. Please enter your password again.
2) srvrmgr command
- On terminal windows, error message "Fatal error (2555922): Could not
open connection to Siebel Gateway configuration store" is shown.
- srvrmgr.log under siebsrvr/log directory shows following error.
NSS - ErrCode 4597527 SysErr 0
SBL-SCM-00018: Could not open connection to Siebel Gateway configuration store (GATEWAY SERVER HOST:GATEWAY SERVER PORT).
GATEWAY SERVER HOST = Host name for Siebel Gateway Server
GATEWAY SERVER PORT = Port number to connect to Siebel gateway Server
- NameSrvr.log under gtwysrvr/log directory shows following error.
SBL-SEC-10018: 523 80
SBL-SEC-10007: The password you have entered is not correct. Please enter your password again.
** Please note key messages is "SBL-SEC-10018: 523 80" in NameSrvr.log.
If this error is NOT recorded, this is really password problem.
Solution
Please make sure to set $ORACLE_HOME/lib in LIBPATH (AIX), SHLIB_PATH
(HP-UX), or LD_LIBRARY_PATH (Linux, Solaris) variables before start_ns
is run.
Applies to:
Siebel CRM - Version 8.1.1 SIA [21111] and later
Information in this document applies to any platform.
***Checked for relevance on 02-JAN-2013***
Symptoms
The Siebel Server is not starting on Windows platform.
Contents of the Siebel Server log file ...
2021
2011-05-12 11:49:47 2011-05-12 11:49:47 +0100 00000011 001 ffff 0001 09
SiebSrvr 3216 4768 C:\Siebel_Preprod\siebsrvr\log\SiebSrvr.log 8.1.1 SIA
[21111] ENU
GenericLog GenericError 1 000203864dca311f:0 2011-05-12 11:49:47 NSS - ErrCode 4597527 SysErr 0
GenericLog
GenericError 1 000203864dca311f:0 2011-05-12 11:49:47 (scmnsclnt.cpp
(135) err=2555922 sys=0) SBL-SCM-00018: Could not open connection to
Siebel Gateway configuration store (ojcrmppgw01:2320).
GenericLog
GenericError 1 000203864dca311f:0 2011-05-12 11:49:47 (scmobj.cpp (211)
err=2555922 sys=0) SBL-SCM-00018: Could not open connection to Siebel
Gateway configuration store (ojcrmppgw01:2320).
GenericLog
GenericError 1 000203864dca311f:0 2011-05-12 11:49:47 (scfutil.cpp (112)
err=2555922 sys=0) SBL-SCM-00018: Could not open connection to Siebel
Gateway configuration store (ojcrmppgw01:2320).
GenericLog
GenericError 1 000203864dca311f:0 2011-05-12 11:49:47 (sissrvr.cpp
(3112) err=2555922 sys=0) SBL-SCM-00018: Could not open connection to
Siebel Gateway configuration store (ojcrmppgw01:2320).
GenericLog
GenericError 1 000203864dca311f:0 2011-05-12 11:49:47 (scfsis.cpp (80)
err=2555922 sys=0) SBL-SCM-00018: Could not open connection to Siebel
Gateway configuration store (ojcrmppgw01:2320).
GenericLog
GenericError 1 000203864dca311f:0 2011-05-12 11:49:47 (listener.cpp
(172) err=2555922 sys=0) SBL-SCM-00018: Could not open connection to
Siebel Gateway configuration store (ojcrmppgw01:2320).
GenericLog
GenericError 1 000203864dca311f:0 2011-05-12 11:49:47 (lstnsvc.cpp
(150) err=2555922 sys=0) SBL-SCM-00018: Could not open connection to
Siebel Gateway configuration store (ojcrmppgw01:2320).
GenericLog
GenericError 1 000203864dca311f:0 2011-05-12 11:49:47 (scisvc.cpp
(1391) err=1311765 sys=0) SBL-SVR-01045: No components are configured.
GenericLog
GenericError 1 000203864dca311f:0 2011-05-12 11:49:47 (scfsis.cpp (274)
err=1310725 sys=0) SBL-SVR-00005: Stale or invalid Task handle
ScfEventLog
SubEvtFacFatal 0 000203864dca311f:0 2011-05-12 11:49:47
scfEventFac::s_pEvtFacLock is NULL and hence SCF event facility cannot
be initialised
GenericLog GenericError 1 000203864dca311f:0
2011-05-12 11:49:47 (scfeventfac.cpp (3790) err=1319869 sys=0)
SBL-SVR-09149: Could not initialize the event facility.
ScfMsgFacLog
SCFMsgFacFatalError 0 000203864dca311f:0 2011-05-12 11:49:47
SCFMessageFacility::s_pSCFMsgFacLock is null and hence the
SCFMessageFacility cannot be initialized
IPCLog IPCFatal 0 000203864dca311f:0 2011-05-12 11:49:47 ipcFacility GetInstance called before initialization - object is null
GenericLog
GenericError 1 000203864dca311f:0 2011-05-12 11:49:47 (scfsis.cpp (64)
err=1310749 sys=0) SBL-SVR-00029: Internal: Shared memory has not been
initialized.
GenericLog GenericError 1 000203864dca311f:0
2011-05-12 11:49:47 (siebsvc.cpp (329) err=2555922 sys=0) SBL-SCM-00018:
Could not open connection to Siebel Gateway configuration store
((null):(null)).
Cause
The customer confirmed that TCP connection could be established from the Siebel Server host to the Siebel Gateway Server host.
The following document was consulted and the customer re-registered the Siebel Server several times:
784524.1 - Siebel Server does not start after changing the SADMIN password on Siebel 8.1.1
The same behavior was persistent after this.
We
trussed the Gateway Server process (running on a Unix platform) for the
time period where the Siebel Server was attempting to start, and
connect to the Gateway Server. This was showing no connection attempt in
the truss, which was not logical, as we had determined that the Gateway
Server was listening on port 2320. The connection to port 2320 should
have generated some output in the truss. It was as though the connection
was not being properly established
After further trace routes
(tracert) were run to check the TCP connection to the Gateway Server
host machine, the customer determined that the attempted connection to
the Gateway Server was showing an incorrect IP address.
Solution
Technical Support directed the customer to the following resources / testing:
(i) Check your network interface configuration on the Windows server:
ipconfig /all
Check
that the Subnet Mask, Default Gateway and DNS Servers are configured
correctly. I suggest you compare with another Windows server that you
know to be "correct".
(ii) Check the 'hosts' file in C:\WINDOWS\system32\drivers\etc for the specification of any static routes
(iii) Perform some trace routes to the Windows server hosting siebsrvr4, to see how the routing is working in reverse.
The
customer determined that the cause was with a static route specified in
the 'hosts' file in C:\WINDOWS\system32\drivers\etc. This contained a
reference to ojcrmppgw01 (the Gateway Server host) pointing to the wrong
IP address. After removing this from the hosts file, the customer was
able to start the Siebel server.
Applies to:
Siebel CRM - Version 8.1.1 [21112] and later
Information in this document applies to any platform.
***Checked for relevance on 10-SEP-2012***
Description
With Siebel CRM version 8.1.1 it can happen that the gateway service
is unresponsive under high load. In such a scenario, no more client
connections from server manager can be established or an entire siebel
server node and additional application object manager (AOM) processes
can not be started.
Occurrence
You might run into this behavior when you run Siebel CRM version
8.1.1 or above and run an enterprise with more than 10 defined
application servers or when enterprise configuration updates to the
siebns.dat file are made. You are observing slowness in enterprise
startup in general.
Symptoms
Once it has been verified that the gateway service is up and running,
the database can be accessed and the correct passwords are provided, if
you then get one of the below error messages you might be facing the
issue discussed here:
a) The srvrmgr command needs a very
long time to connect to a single server using the /s switch or returns
the following error after a while in srvrmgr.log file:
NameServerLayerLog Error 1 000000024f5f0132:0 2012-03-13 10:12:21 Unable to connect to the gateway server.
GenericLog GenericError 1 000000024f5f0132:0 2012-03-13 10:12:21 NSC - ErrCode 5009 SysErr 0
GenericLog GenericError 1 000000024f5f0132:0
2012-03-13 10:12:21 (scmnsclnt.cpp (135) err=2555922 sys=2)
SBL-SCM-00018: Could not open connection to Siebel Gateway configuration
store (localhost:2320).
b) An Object manager process is
terminating during startup. When running the srvrmgr command "list procs
for comp <compname>", processes are stuck in the "Starting" state
and never transition to a state of "Running" or "Online"
c) The siebsvc server scheduler process
service is exiting, no processes are started and in the Siebsrvr.log
file the following error can be found:
NameServerLayerLog Error 1 0000fb2e4f7100de:0 2012-03-27 08:56:09 Unable to connect to the gateway server.
GenericLog GenericError 1 0000fb2e4f7100de:0 2012-03-27 08:56:09 NSS - ErrCode 5009 SysErr 0
GenericLog GenericError 1 0000fb2e4f7100de:0
2012-03-27 08:56:09 (scisvc.cpp (1391) err=1311765 sys=0)
SBL-SVR-01045: No components are configured.
GenericLog GenericError 1 0000fb2e4f7100de:0
2012-03-27 08:56:19 (siebsvc.cpp (221) err=2555922 sys=0)
SBL-SCM-00018: Could not open connection to Siebel Gateway configuration
store ((null):(null)).
d) The siebns.dat file is recreated
multiple times per minute. You can observe a temporary file called
siebns.dat.new frequently listed in the folder where siebns.dat is
located.
e) You are also running into this issue if
none of the above errors occur but you notice increased startup times
when adding servers to the enterprise.
Workaround
The following three bugs have been created to address this behavior:
- Bug 12561457: GATEWAY SERVER CONSUMING HIGH CPU.
This has been fixed in Fixpack 8.1.1.8
- Bug 13827461: SIEBNS.DAT FILE COMPACTION AND OPTIMISATION
Thas been fixed in Fixpack 8.1.1.6.
- Bug 13827574: EXTRA SRVRMGR CONNECTIONS CAUSING PERFORMANCE ISSUES
This has been fixed in Fixpack 8.1.1.6.
Currently there exist Quick Fixes for the following Fixpacks to address these issues:
- Fixpack 8.1.1.3: QF03CK patch 13819838
- Fixpack 8.1.1.4: QF0475 patch 13912174
- Fixpack 8.1.1.5: QF0591 patch 13910484
- Fixpack 8.1.1.6: QF0637 patch 14283967
- Fixpack 8.1.1.7: QF0723 patch 14084625
Customers that are looking to accelerate the enterprise startup
process should apply these Quick Fixes regardless if one of the above
errors is encountered or not. They should benefit from the optimized
siebns.dat write performance in any case.
To mitigate the issue on versions where currently no quickfix does
exist, the following workarounds have helped to reduce the load put on
the gateways siebsvc process:
a) do not start many siebel servers concurrently. Starting each
server with a delay of 3-5 minutes will give gateway sufficient time to
handle all incoming requests.
To monitor when a server has completely
started up, you can either run the srvrmgr "list procs for server
<servername>" command and verify all processes are in running
state or enable auditing by setting the gateway.cfg parameter
EnableAuditTrail = TRUE. Then monitor the file nameserver_audit.log. The
server has started up when no more lines are added to the audit file.
b) try to run as little srvrmgr commands as possible; use /i command
file switch switch rather than to launch multiple srvrmgr in a row.
In case a system monitoring tool is used that makes frequent use of srvrmgr, it should be disabled or poll frequency reduced.
c) if you are starting lots of additional batch component processes after initial enterprise startup:
define a dedicated admin user that only
has the Siebel administrator responsibility assigned and use this new
account to start recurring batch components like Workflow, Assignment,
EIM etc. The standard sadmin account has 228 responsibilities and all
these are retrieved from the database for each gateway login. Reducing
this to 1 makes the database login part of a gateway connection faster.
d) customers running Oracle 11g database might deploy the DRCP protocol to connect the gateways odbc source.
To setup a DRCP connection string see
note How To Setup and Trace Database Resident Connection Pooling (DRCP)
(Doc ID 567854.1). Then the gateways odbc source definition needs to be
changed to use the new drcp tnsnames connection string. Tests have shown
that gateways database login can be accelerated with this DRCP
approach by up to 30% compared to the standard dedicated database mode.
e) Configuration changes to the enterprise should only be done in a maintenance window.
To avoid the risk of frequent siebns.dat rewrites, configuration
changes that require updates to the siebns.dat like for example adding
new servers to the entrprise, assigning or unassigning components,
changes in component definition etc should only be done when the
enterprise is down or there is very little load during low volume
business hours. In 24x7 deployments special care needs to be taken to
find a period of very low activity.
Patches
Fixpack: 8.1.1.3 QF03CK
Fixpack: 8.1.1.4 QF0475
Fixpack: 8.1.1.5 QF0591
Fixpack: 8.1.1.7 QF0723
Applies to:
Siebel System Software - Version 7.7.2.6 SIA [18372] and later
z*OBSOLETE: Microsoft Windows Server 2003
Database: Oracle 9.2.0.6
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: HP-UX 10.0
This document was previously published as Siebel SR 38-3262290961.
Symptoms
We've installed a new server (JANBEBESBL37) for our production server
farm consisting of 6 siebel servers (enterprise ES_VINP). The server
runs Windows 2003 server SP1.
However, when starting the Siebel Server service, the server won't start up displaying following error messages:
GenericLog GenericError 1 0 2007-01-30
09:34:18 (sissrvr.cpp (2979) err=2000026 sys=12) SBL-SVR-00026:
Unable to allocate shared memory.
GenericLog GenericError 1 0 2007-01-30
09:34:18 (scisvc.cpp (1225) err=2001045 sys=0) SBL-SVR-01045: No
components configured !
GenericLog GenericError 1 0 2007-01-30
09:34:18 (scfsis.cpp (166) err=2000005 sys=0) SBL-SVR-00005: Stale or
invalid Task handle
GenericLog GenericError 1 0 2007-01-30
09:34:18 (scfsis.cpp (41) err=2000029 sys=0) SBL-SVR-00029: Internal:
Shared memory has not been initialized.
Cause
While carrying out tests to monitor the behaviour of the Siebel
Server service at start-up, it was determined that based on a number of
different variables (# of components enable; # of maxtasks per
components...etc), the optimal size of a Shared Memory file is
calculated.
The test Server employed for these tests was built
around the Microsoft Windows 2003 Server platform and configured with
1.8GB of physical memory.
Note, at no more point during the course
of these tests did the Server actually have more than 1107MB (approx
1.1GB) free – due to allocation made to the system itself as well as
other underlying (non-Siebel related) processes.
Observation:
With 5 Call Center Object Managers running with Default settings (Max Tasks = 20), .shm file built in memory was 13MB
With SCCObjMgr_enu (ONLY) re-configured to support 100 Masktasks, .shm file built went up to 22.7MB;
for 500 tasks, 70MB was required; while for 5000 and 10000 tasks, 564MB
of memory and 1.1GB of memory was required respectively.
**With 20000 Maxtasks enabled, the Siebel Server simply could not be starte
Solution
Resolution:
---To begin with no .shm could be created.
---After decreasing the number of max tasks set for one of the
Object Managers enabled, a 650MB shared memory file was created (note:
actual size on disk was 800MB), although the following error was also
recorded:
ServerLog ProcessExit 1 0 2007-03-05 03:20:21
ServerLog ProcessExit 1 0 2007-03-05
03:20:21 ePharmaObjMgr_egr60677 SBL-SVR-00027 Process exited
with error - Internal: Unable to attach the shared memory file.
---
By decreasing the number of max tasks set on several other components,
it was possible to reduce the size of the .Shm file created to 640MB and
also start up the Siebel Server.
אין תגובות:
הוסף רשומת תגובה