SBL-SVR-01074

Date:

Message 1

For the benefit of the readers,

Question: During the implementation of the Loyalty environment, some questions were raised about the starting of tasks from the command line. The reproduction of this behavior and the troubleshooting of this lead to the following information raised/clarified.

Resolution:
*You need to set the MinMTServer=MaxMTServer=<Number of Loyalty Process on your Siebel server>=2 for the sake of the example. This is independent on the number of Server Key you will associate to each pair server/process.
*In order to start the Loyalty Batch Engine, you can either run a "Workflow Process Manager" job for the process "LOY Engine - Start Engine" in which you will set the number of processes and the number of thread per process to the value required for your environment. Both are set to 1 by default. This will start a number of Batch Engine tasks as per the formula (1 + (1 + Thread/Process #)) * # of Processes which is a minimum of 3 tasks per process. This makes 6 tasks in our example.
*You can alternatively start these tasks manually as per the customer description.
The first task will make the MTServer determine to which process it will be associated. In our example the second task will be associated to the 2nd key. The only way to confirm that is by reading the log in which the SRMRouting event has been set to 4.

Enhancement Change Request 12-VM0YFD: "Please add a way to read the process associated to a task via the srvrmgr" has been opened to have an easier way of verification.
Enhancement Change Request 12-VLY7CK: "Error SBL-SVR-01069 while choosing the process to work for the LoyEngineBatch tasks" has been opened to remove this message which is the expected behavior.
*Please note that a the startup of your server, you will have one log file per MTServer has this process require to start its listener on a TCP port.
*Please also note that in the Server Administration task view, you will see the entries from the S_SRM_REQUEST table which are requests for tasks and not tasks.
*When you activate a Promotion, this will generate a request for a task in order to update the Cache in the Batch Engine MTServer.
*If you do this when the Engine Tasks are not fully started, this will result in left over request that will need to be cleaned up with the component SvrTblCleanup.

SBL-SVR-01068

Date:

Applies to:

Siebel System Software - Version: 7.8.2.3 SIA [19221] and later [Release: V7 and later ]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.8.2.3 [19221] Com/Med
Database: Oracle 9.2.0.6
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 9

This document was previously published as Siebel SR 38-3199007053.

Symptoms

SBL-SVR-01068We are getting frequent SIGABRT error for "Workflow Proc Batch Mgr" comp and on checking its corresponding logs of each of the exited tasks.It is giving the below error:

PS:exited tasks are the one which is leading to a crash and generating a core.

GenericLog GenericError 1 0 2006-11-14 07:56:55 (scirkey.cpp (121) err=2001068 sys=0) SBL-SVR-01068: This component is not enabled for "Key Based Routing"

I've gone through the Supportweb and found a solution mentioned bellow : I tried to implement the same,though it gave successful change message,but it didn't reflect the change on listing the value.

FYI:

change param KeyBasedEnabled = TRUE for comp WfProcBatchMgr

*This allowed the component to run without this error but still the Tier changes were not changed.

I've even tried to compare this with other test enviornment but could see it as TRUE or False on some of the instances.Kindly help us in understanding this parameter further.

Regards

Cause

Configuration/ Setup

I'm getting the following error when trying to run EIM. This .ifb used to work.

SBL-ADM-60070: Error reported on server 'SblCRMDev01' follows:
SBL-SVR-01054: The task exited without sending a response.

The only difference that I know of is that we have extended EIM_CONTACT several times. We didn't have a problem for the other ones, though.

I've attached the ifb file I'm using, the log file produced when logging was turned up and the crash file.

Let me know if you have any questions. Thanks.

Ken Ratzlaff
425-478-1951

Cause

Configuration/ Setup

Solution

Message 1

For the benefit of othere readers,

Customer experienced issues with columns created with the 'Case Insensitivity' wizard.

It has been determined that Customer ran the 'EIM Mapping Wizard' sometime after running the 'Case Insensitivity' wizard. For this reason the EIM mapper created eim columns and mappings for the case insensitive columns.

In order to avoid the above issue you should always make sure that the EIM Mapping wizard does not take such columns in account.

Additional Keywords: Case Insensitivity, EIM Mapping

Applies to:

Siebel CRM - Version 8.0.0.13 SIA [20448] and later
Information in this document applies to any platform.

Symptoms

On : 8.0.0.13 SIA [20448] version, ADM - App. Deployment Manager

When attempting to export data using ADM command line using ADMbatchProc component, the component crashes and the following error occurs:

ERROR
-----------------------
SBL-ADM-60070: Error reported on server 'WFMDEVAPP1' follows:
SBL-SVR-01054: The task exited without sending a response.
SBL-SCL-00131: Either the RC2 or the AES cryptography engine is not initialized.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. login using srvrmgr
2. Execute following command to export LOV records using ADM.

run task for comp admbatchproc with admpath="C:\ADM\output_xml", admfilter='[Value] LIKE "SR_AREA*"', admdatatype=LOV, admeaimethod=upsert, admprefix=ADM_SR_AREA

Cause

Cause of the issue is identified as product defect.

Issue is replicated in-house and a product defect 14460219 - ADM BATCH PROC EXPORT FAILS WITH SBL-SCL-00131 ERROR is raised to address the issue.

Solution

Solution

Message 1

For the benefit of other user:

The customer has created new Object Managers for PRM Portal (for 8 different languages). As part of this, he has created new virtual directories, new components, and new entries in the eapps.cfg. And finally, he synchronized the batch server components.

But, when he tried to access the new Object Manager, it says "Page can not be displayed".

The problem has been resolved after the customer modified the web server (IIS) parameters as follows:
1. Open IIS (Start menu --> Program Files--> Administrative Tools--> Internet Services Manager)
2. Expand default web site
3. Choose Virtual directory created (for the custom component) and right click and go to Properties
4. In Virtual directory tab, choose Configuration button. Click that
5. You get another pop up- choose tab - App mappings. Highlight .swe and click on edit
6. Another pop up opens - At the bottom, there is a check box - "Check that file exists"
7. Uncheck the check box
8. Repeat this for .swef

Documentation Enhancement request 12-QAWCBM (Update the "Creating a New Virtual Directory" section from Siebel Installation Guide for MS Windows) was logged to address this matter.

Applies to:

Siebel CRM - Version: 7.5.3 [100] to 8.1.1.7 [21238] - Release: V7 to V8
Information in this document applies to any platform.
Product Release: V7 (Professional)

Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: Microsoft Windows 2000 Server SP 4

Symptoms

It was reported that there were problems using drag drop functionality in the Siebel application. When the user was trying to save an attached document, the system was displaying the following error message:

Session 
Warning: 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.

After this error, the user is usually logged out of the application.

The issue was only present in the thin client and could not be reproduced in the dedicated client.
The same error was observed in the thin client using both DB authentication and ADSI authentication.

The following messages were displayed in the SWE logs:

ProcessPluginRequest    ProcessPluginRequestError    1    0    2006-04-18
 17:15:22     5116: [SWSE] RPC coming in without a user session

ProcessPluginRequest    ProcessPluginRequestError    1    0    2006-04-18
 17:15:22     5116: [SWSE] Failed to obtain a session ID. NOT OK

ProcessPluginRequest    ProcessPluginRequestError    1    0    2006-04-18
 17:15:22     5116: [SWSE] Set Error Response (Session: Error: 00065535 
Message: NOT OK)

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:

About Siebel Gateway Name Server

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.

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.

About ERROR CODES

Privacy Policy

Contact Us

SBL-SVR-01074

Applies to:

Symptoms

Changes

Cause

Solution

Applies to:

Goal

Fix

SBL-SVR-01069

Applies to:

Symptoms

Cause

Solution

Applies to:

Symptoms

Cause

Solution

Applies to:

Symptoms

Cause

Solution

Applies to:

Symptoms

Solution

Message 1

SBL-SVR-01068

Applies to:

Symptoms

Cause

Solution

Message 1

Applies to:

Symptoms

Cause

Solution

Applies to:

Symptoms

Cause

Solution

SBL-SVR-01054

Applies to:

Symptoms

Cause

Solution

Applies to:

Symptoms

Cause

Solution

Message 1

Applies to:

Symptoms

Cause

Solution

SBL-SVR-01051

Applies to:

Symptoms

Cause

Solution

Message 1

Applies to:

Purpose

Scope

SBL-SVR-01051: SISNAPI connection refused, the server could be down: %1

Explanation

Corrective Action

Applies to:

Symptoms

Solution

Message 1

Applies to:

Symptoms

Cause

Solution

Applies to:

Symptoms

Changes