Applies to:
Siebel System Software - Version 7.7.1 [18306] and later
Information in this document applies to any platform.
Error Message Area:Server Request Broker - SRB
Version:Siebel 7.7
Purpose
This document is intended to provide cause and corrective action
information about Siebel Error Message SBL-SRB-00061: Process %1 on
Siebel Server %2 terminated
Scope
This document is informational and intended for any user.
Details
Explanation
The process named in the error must have been shutdown on the server
mentioned and could not route the message to the particular process.
Corrective Action
Check to make the named process is still running on the server mentioned. If not, start the component.
Applies to:
Siebel Sales Volume Planning - Version: 7.7.2.2 SIA [18356] to 7.8.2 SIA [19213] - Release: V7 to V7
Siebel Consumer Goods - Version: 7.7.2.2 SIA [18356] to 7.8.2 SIA [19213] [Release: V7 to V7]
Siebel CRM - Version: 7.7.2.2 SIA [18356] to 7.8.2 SIA [19213] [Release: V7 to V7]
Information in this document applies to any platform.
Product Release: V7 (Enterprise)
Version: 7.7.2.2 [18356] QF0212 - Cons Goods
This document was previously published as Siebel SR 38-2032520391.
Symptoms
This customer has added customizations on top of the out-of-the-box
CG SVP Process, which include a custom business service that automates
the creation of 8 concurrent workflow process tasks, executed through
the Sales Volume Planning administration view:
1) The customer
has a SVP master workflow process ("GIL ENA SVP Master Workflow") that
calls two sub processes "GIL ENA SVP Invoke Preagregation Actions" and
"GIL ENA SVP Aggregate Baseline". This executes the Pre Aggregate and
the Aggregate Tasks. The Aggregation of Baseline is carried from Level 3
and above.
2) The customer has another Interface that calls the
Stored Procedure to rollup the Baseline Units from Level 5 to Level 3.
So the customer has all the Baseline Units at Level 3. The SVP Aggregate
task rolls up these Baseline Numbers from Level 3 to above the
Hierarchy.
The SVP master workflow process is scheduled to run
every night in parallel with other process that execute every night. The
customer has a Repeating Component Request that is running this
workflow process daily.
A new Patch was applied to the Siebel
7.7.2.2 Cons Goods installation: Siebel Quick Fix version 7.7.2.2
QF0212. After this quick fix installation the customer faced a crash in
the Consumer Sector BuildTree method. When running their master workflow
process, it completed the Pre Aggregate Actions (1st Sub Process in the
Master Workflow) but when it created the Action for Aggregation of
Baseline (2nd Sub Process in the Master Workflow), the Workflow exited
with error:
"SBL-SRB-00061: Process WfProcMgr on Siebel Server gbo6016d terminated".
The Task State shows that the process exited with the following error:
"Process exited because it received signal SIGABRT."
Cause
Siebel Quick Fix version 7.7.2.2 QF0212 incorporated changes from Bug 10479739: cannot copy one product into a new product by executing a SVP copy action.
The
fix for this bug changed the forward fetch parameter from False to True
in the Execute call to the Account business component.
The following Bug was logged for the crashes observed with this quick fix:
Bug 10498681: [CR#12-10085D4][FR#12-1042O3Y] SVP WF crash after installing QF0212
It is related the following Bug:
Bug 10484347: [CR#12-REJ4Y3][FR#12-1049CQ4] ACR218:SVP Baseline Aggregation deleting/zeroing out Baseline
Solution
Engineering investigation found that rolling back the change for the
forward fetch parameter allowed the customer workflow process to
complete successfully.
This has been fixed in the following Siebel versions:
Quick Fix 7.7.2.2 [18356] QF0238
Fix Pack 7.8.2.1 [19214]
Release 8.0 and above
The
customer confirmed that the new SVP Patch (QF0238) fixed their issue
and allowed the SVP Master Workflow to complete the Baseline and the
Shipment aggregation actions.
Applies to:
Siebel CTI - Version 7.5.3.11 [16199] and later
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.5.3.11 [16199] DEU
Database: Oracle 9.2.0.6
Application Server OS: Sun Solaris 2.8
Database Server OS: Sun Solaris 2.8
This document was previously published as Siebel SR 38-2938316347.
***Reviewed for Relevance 11-Nov-2012***
Symptoms
We get Errors when we connect to Siebel-CTI with the CTI Toolbar. Sometimes it works, but sometimes (ca. 10%) not.
GenericLog GenericError 1 2006-03-01
08:49:52 (srbroute.cpp 52(6729) err=5700061 sys=0) Prozess
CommSessionMgr auf Siebel Server dab-cti01 beendet
GenericLog GenericError 1 2006-03-01
08:49:52 (srmconn.cpp 2(2976) err=5700061 sys=0) SBL-SRB-00061:
Prozess (null) auf Siebel Server (null) beendet
GenericLog GenericError 1 2006-03-01
08:49:52 (srmconn.cpp 2(2630) err=5700061 sys=0) SBL-SRB-00061:
Prozess (null) auf Siebel Server (null) beendet
GenericLog GenericError 1 2006-03-01
08:49:52 (srmconn.cpp 2(2244) err=5700061 sys=0) SBL-SRB-00061:
Prozess (null) auf Siebel Server (null) beendet
I looked for the
Task ID of the crashed Communications Session Managers (Error code
SBL-GEN-00003) in order to check out the Logfiles at the CTI Server
Machine, but there are no logfiles for the specified Task ID at the CTI
Server! Nor for this one Crashed Task, eihter for the other crashed
tasks.
Cause
Customer had set a higher value (greater than 1) to MaxMTServer and
MinMTServer parameters for the Communication Session Manager component.
They were encountering the behaviour where when the agent logs into the
Application with Communication Toolbar enabled, it would throw error.
This was intermittent. Customer was using the Aspect CTI Driver.
Solution
The Aspect driver can not handle more than one process. Expert
Services suggested the customer to set MaxMTServer = 1, MinMTServer =1
and MaxTasks = 200. Once after re-setting these parameters on the
Communication Session Manager component, the error was resolved.
Applies to:
Siebel Remote Server - Version 7.5.3.4 [16180] to 8.1 [21039] [Release V7 to V8]
Information in this document applies to any platform.
Product Release: V8 (Enterprise)
Version: 8.0 [20405]
Database: Oracle 10.2.0.2
Application Server OS: Red Hat Linux Advanced Server 2.1
Database Server OS: Red Hat Linux Advanced Server 2.1
This document was previously published as Siebel SR 38-3462177683.
Checked for relevance 10-02-2013
Symptoms
SBL-GEN-00255
The Generate New Database server task failed with the following error message:
[SBL-SRB-00061: Process GenNewDb on Siebel Server srvr1 terminated]
The Siebel Remote Component Group was running, and the [Generate New Database] was online.
There
was only one Server [srvr1], in the Enterprise Server [ENT]. The
[Siebel Remote] component group was Assigned to the Server [srvr1]. Both
the [Assigned?] & [Enabled on Server?] were checked.
Looking at the log file, the following message was found:
[GenNewDb 1851 SBL-GEN-00255 Process 1851 exited with error - Internal: Error during exec()]
Complaining about the component or Object manager is not available. Both [Siebel Remote] and UCM Object Manager were running.
The original log files are attached for your reference.
Could you please give us a way forward.
Cause
Invalid ODBC configuration
Solution
For the benefit of other readers.
The customer was running the Generate New Database component and it failed. The error returned was:-
[SBL-SRB-00061: Process GenNewDb on Siebel Server srvr1 terminated]
The
GenNewDB.log file showed that the process was stopping as it connected
to the Local DSN. Manually connecting to the local DSN showed that this
also failed.
It was then discovered that it was looking for a
library that was not in the LD_LIBRARY_PATH. After modifying the
LD_LIBRARY_PATH to re-include the SQLANY/lib everything worked.
Applies to:
Siebel Loyalty Engine - Version 8.1.1.1 [21211] to 8.1.1.8 SIA [23012] [Release V8]
Information in this document applies to any platform.
Symptoms
Loyalty, the Real Time Loyalty engine crashes while processing buckets with the following error:
SBL-SRB-00061: Process LoyEngineRealtime on Siebel Server clslyd1 terminated.
Steps to reproduce:
The issue can be reproduced at will with the following steps:
1. Go to Loyalty Member > Promotion Attribute View
2. Select a bucket and select Process button
3. The error SBL-SRB-00061 occurs as the Loyalty RealTime Engine is crashing with the following call stack:
/applic/siebel/siebsrvr/lib/libsslcshar.so(SSstring::operator=(SSstring const&)+0x22)[0x556e2d62]
/applic/siebel/siebsrvr/lib/libsssalysv.so(CSSLOYEvaluateAssignPoints::Evaluate(CSSLOYObjectProcessor*,
CSSLOYAction*, CSSLOYPromoResult*)+0x225f)[0x6a46d9cf]
/applic/siebel/siebsrvr/lib/libsssalysv.so(CSSLOYObjectProcessor::GeneratePromoResults()+0x38b)[0x6a45b91b]
/applic/siebel/siebsrvr/lib/libsssalysv.so(CSSLOYObjectProcessor::DoProcessObject(CSSLOYCacheMgr*,
CSSLOYWorkObject*)+0x20c)[0x6a45a5cc]
/applic/siebel/siebsrvr/lib/libsssalysv.so(CSSLOYObjectProcessor::ProcessObject(CSSLOYCacheMgr*,
CSSLOYWorkObject*)+0x30)[0x6a4598a0]
/applic/siebel/siebsrvr/lib/libsssalysv.so(CSSLOYProcService::DoProcessObject(CSSLOYWorkObject*)+0x821)[0x6a43be81]
/applic/siebel/siebsrvr/lib/libsssalysv.so(CSSLOYProcService::ProcessObject(CCFPropertySet
const&, CCFPropertySet&)+0x593)[0x6a438fb3]
Cause
If the Bucket Promotion has no partner associated, then, the LoyEngineRealTime crashes while processing Buckets.
Based on tests in standard environment 8.1.1.1, while attempting to
process Buckets using real time engine, the component LoyEngineRealtime:
1) crashes, if there is no Partner defined at the promotion level
2) executes correctly, if there is a Partner defined at promotion level.
Solution
On researching the issue, the engineering has confirmed that, for
bucket processing, the user is required to associate a partner at the
promotion header level. This is required for bucket processing because,
unlike a transaction processing (where the partner is available on
transaction) bucket will not get the partner information if the partner
is not mentioned on the promotion header.
Applies to:
Siebel Assignment Manager - Version: 7.7.2 SIA [18325] and later [Release: V7 and later ]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.7.2 [18325] Com/Med
Database: Oracle 9.2.0.4
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 9
This document was previously published as Siebel SR 38-1622315561.
Symptoms
SBL-OSD-02011, SBL-SRB-00061
Hi,
We are currently running batch assignments on our test environment.
We are finding that batch assignment jobs without a 'object where' clause fail, but those with a where clause are successful.
This
only seems to occur for the 'Order (Sales Credit Assignment)'
assignment object (have tried with other objects like Contacts and the
jobs run successfully).
The Batch job details are:
Assignment Object Name = Order (Sales Credit Assignment)
Replace Team Members = FALSE
The job generates the following error in the completion information field of the jobs screen:
SBL-SRB-00061: Process AsgnBatch on Siebel Server siebsrvr1 terminated
The associated task has the following error in the status field:
Process exited because of a segment violation (SIGSEGV)
We
have turned up event logging for the Batch Assignment component and
have attached the task log to this service request. The log doesn't show
any errors relating to assignment manager (i.e. invalid rule/object
configuration).
Thanks,
Cause
For the benefits of the other user, it was found out that the default
assignment object for the Order workflow policy object was copied and
modified for the customer by changing the position table from
S_ORD_CRDT_ASGN to S_ORDER_POSTN. However, not all the default
'Assignment User Prop' were disabled (they are not required).
Solution
After disabling one copied 'Assignment User Prop' the crashes have not
occurred anymore and allowed Order assignments to work as expected.
Applies to:
Siebel Enterprise Integration Manager - Version 8.0.0.3 [20416] and later
Information in this document applies to any platform.
***Checked for relevance on 12-Feb-2013***
Symptoms
Creating a custom Foreign Key column in the S_ORG_EXT table which
has the S_ADDR_ORG table as the Foreign Key table leads to the
following behaviour when running the EIM task (and after the custom FK
column has been mapped to the EIM_ACCOUNT Interface table using the EIM
Table Mapping Wizard which ran successfully):
The EIM task is terminated. The following error messages is seen in the Enterprise log file:
EIM
292668 SBL-OSD-01000 Process 292668 exited with error - Internal: The
process attempted to read from or write to a virtual address for which
it does not have the appropriate access.
Additional error message:
SBL-SRB-00061: Process EIM on Siebel Server <Siebel_server_name>terminated
Cause
Bug 10559179 has been logged to address the matter.
Solution
The current workaround is to update the custom Foreign Key column in S_ORG_EXT (pointing to S_ADDR_ORG) via Siebel Scripting.
Applies to:
Siebel Workflow - Version 7.5.2.214 SIA [16066] and later
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.5.2.214 [16066] Fin Svcs
Database: Oracle 8.1.7.4
Application Server OS: Sun Solaris 8
Database Server OS: Sun Solaris 8
This is only applicable to 7.5 version.
This document was previously published as Siebel SR 38-1020223111.
Checked for relevance as on 15-July-2012.
Symptoms
SBL-OSD-02006, SBL-SRB-00061
We have a workflow process that is causing the Workflow Process
Manager to become "unavailable". This occurs when the Workflow Process
attempts to resume from a Wait Step. The error reported in the Component
Request view and the Server Tasks view is as below:
Component Request Details
--------------------------------
Component: Workflow Process Manager
Mode: Asynchronous
Status: Error
Completion Code: 5700061
Completion Information: SRB-00061: process WfProcMgr on Siebel Server test terminated
Task Details
--------------
Component: Workflow Process Manager
Task State: Exited
Status: Process exited because it received signal SIGABRT
I have followed the steps outlined in FAQ 1482 to trace the process
(attached), however this does not reveal any additional useful
information. All that it shows is the final step before the error.
Cause
business service are customized and is designed to perform complex
computation including invocation of Incentive Compensation, ICM Calc
Engine task.
Solution
Message 1
For the benefit of the other users, the customer encounter the
following error on the component request status when invoking workflow
process manager component :
Process exited because it received signal SIGABRT
This workflow process involves mainly business service and wait steps.
These business service are customized and is designed to perform complex
computation including invocation of Incentive Compensation, ICM Calc
Engine task. Whereas, the wait step is incorporated to monitor the
status of the ICM Calc Engine task. The above error occurs when the
subsequent workflow process manager task are spawned off by the server
request broker, to resume the processing.
Do note the above error is not reproducible while running on the standard application.
This error could only be reproduced with the customer database set up
in-house. Change request# 10465646 was logged to address this and it is
only for 7.5 version, CR status is inactive now.
Applies to:
Siebel Remote - Version 7.5.3.4 [16180] and later
IBM AIX on POWER Systems (64-bit)
Product Release: V7 (Enterprise)
Version: 7.5.3.4 [16180]
Database: Oracle 8.1.7.4
Application Server OS: IBM AIX 5L 5.1
Database Server OS: IBM AIX 5L 5.1
This document was previously published as Siebel SR 38-1923792601.
***Checked for relevance on 29-Nov-2012***
Symptoms
SBL-GDB-00004, SBL-SMI-00024, SBL-SRB-00061, SBL-GEN-09103
Hi,
I am running "GenNewDb" and immediately, I got this following error.
srvrmgr:srvr007tst> start task for component GenNewDb
start task for component GenNewDb
SBL-NET-01034: The SISNAPI connection was closed by the peer
When I checked the "GenNewDb_xxxx.log",I can see the following error message.
ContextInit ContextInit 0 2005-04-18 23:15:50 SIEBEL_ASSERT_MODE = 0
GenericLog GenericWarn 2 2005-04-18 23:15:50 (smisched.cpp 17(266) err=9103 sys=0) SBL-GEN-09103: Parameter value was never set (i.e. is null)
GenericLog GenericWarn 2 2005-04-18 23:15:50 (smisched.cpp 17(269) err=9103 sys=0) SBL-GEN-09103: Parameter value was never set (i.e. is null)
GenericLog GenericError 1 2005-04-18 23:15:50 (smisched.cpp 17(285) err=2100024 sys=0) SBL-SMI-00024: Unable to load gennewdb
Please look into this ASAP as we need to provide the extract to TAM for review.
Thanks & Regards
Cause
Missing Siebel server files:
a) \siebsrvr\lib\libgennewdb.so
b) \siebsrvr\dbtempl\sse_utf8.dbf
Solution
Message 1
1 of 2
For the benefit of other readers, the issue and resolution are as follows.
Issue Description:
----------------------
When
the GenNewDB was run either from UI or from server manager, an error
occurred almost immediately. In this case, customer ran from the server
manager prompt as follows and encountered errors as described below.
srvrmgr:srvr007tst> start task for component GenNewDb
start task for component GenNewDb
SBL-NET-01034: The SISNAPI connection was closed by the peer
In GenNewDb_*.log, one could see the following error messages:
ContextInit ContextInit 0 2005-04-18 23:15:50 SIEBEL_ASSERT_MODE = 0
GenericLog GenericWarn 2 2005-04-18 23:15:50 (smisched.cpp 17(266) err=9103 sys=0) SBL-GEN-09103: Parameter value was never set (i.e. is null)
GenericLog GenericWarn 2 2005-04-18 23:15:50 (smisched.cpp 17(269) err=9103 sys=0) SBL-GEN-09103: Parameter value was never set (i.e. is null)
GenericLog GenericError 1 2005-04-18 23:15:50 (smisched.cpp 17(285) err=2100024 sys=0) SBL-SMI-00024: Unable to load gennewdb
Resolution:
--------------
After detailed analysis, Siebel Technical Support discovered the following.
1. That Siebel server environment was missing the following files
a) \siebsrvr\lib\libgennewdb.so
b) \siebsrvr\dbtempl\sse_utf8.dbf
Contd...
Message 2
2 of 2 - Contd from previous..
Customer had another
environment similar to this one (with exact same Siebel version and
QuickFixes installed), where everything was working. Since this non
working environment was a Test environment and not a Production
environment, Siebel Technical Support recommended copying the missing
library \siebsrvr\lib\libgennewdb.so and file
\siebsrvr\DBTEMPL\sse_utf8.dbf from the working environment.
After the copy was done, the Siebel Gateway and Server were restarted and GenNewDB worked successfully.
Recommendations:
-----------------------
Other recommendations made to the customer were as follows
1. Refer to "Maintenance Level Update Recommended for AIX 5L v5.1 (Document 477432.1)" (formerly Alert 899).
According to that Alert, which refers "Fileset Update Required for C++ Runtime Libraries on AIX (Document 477396.1)"
(former Alert 851), customers have to ensure Siebel deployment is
running the latest C++ runtime libraries (6.0.0.12) or later, if they
are on AIX 5L v5.1
2. Other recommendation made was to not copy
missing files, if the environment would be a Production one. If missing
files would be noticed in Production, then for long term stability,
customers should consider reinstalling the affected Siebel server.
אין תגובות:
הוסף רשומת תגובה