SBL-SVR-01068



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


Solution



Message 1


For the benefit of other users,



The customer was running a Siebel 7.8.2.3 eCommunications environment
and had recently started seeing SIGABRT errors which appeared to result
from Workflow Process Batch Manager instances running on the enterprise.
In addition to the SIGABRT errors the crashing processes also reported
the following error :



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"



The error message suggests that the component should be enabled for
'Key-Based Routing' but this specific form of request routing based on a
generated key for particular instances of a component is restricted in
its use. It was not expected that the WfProcBatchMgr component would
make use of this functionality and the error message appears to be
misleading. For further information on Key-Based Routing please refer to
'Siebel Field Service Guide > Scheduling and Dispatch >
Scheduling Administration > Setting Up Server Processes, Performance,
and Key-Based Routing' and Technical Note 641: How Assignment Manager,
Rule Group, and Server Key Mapping Interact.



Following comparison of the component configuration between this and
other functioning environments it was established that a number of LOV
entries were missing in the problematic Test environment and which were
required by the Workflow Process being run. (continued...)


This appeared to result in the SIGABRT errors in the component and
misleading error messages being seen in the log files. Once the customer
migrated the missing LOV entries the processes functioned correctly.


Keywords : Key, Based, Routing, enabled, Key-Based, SBL-SVR-01068, WfProcBatchMgr, SIGABRT, LOV, List of Values, KeyBasedEnabled














Applies to:


Siebel Loyalty Engine - Version: 7.7.2.2 SIA [18356] and later   [Release: V7 and later ]
IBM AIX on POWER Systems (64-bit)

Product Release: V7 (Enterprise)

Version: 7.7.2.2 [18356] Travel

Database: IBM DB2 8.1 FixPack 5

Application Server OS: IBM AIX 5L 5.2

Database Server OS: IBM AIX 5L 5.2



Symptoms


SBL-LTY-00109, SBL-SVR-01068

Hi siebel support

We have created a custom version of the
eLoyalty Processing Engine with Name = eLoyalty Tier Processing engine.
Purpose of this is to process tier changes nightly.
Creation of this
and how to make it run was discussed in other service request but we
managed to make it run in our Test envinronment. Now that we have
created the exact same component in UAT, it errors when trying to start
it.
The errormessage in the logfile is:
"SBL-LTY-00109: The
process was unable to find an available server routing key to register.
Please check the loyalty server key definition of your system."
And:
"SBL-SVR-01068: This component is not enabled for "Key Based Routing""

These messages comes right after this SQL:
SELECT
      T1.CONFLICT_ID,
      T1.LAST_UPD,
      T1.CREATED,
      T1.LAST_UPD_BY,
      T1.CREATED_BY,
      T1.MODIFICATION_NUM,
      T1.ROW_ID,
      T1.PROCESS_NUM,
      T1.SERVER_NAME
   FROM
       siebel.S_LOY_SRV_MAP T1
   WHERE
      (T1.SERVER_NAME = ?)
   ORDER BY
      T1.PROCESS_NUM
ObjMgrSqlLog    Detail    4    0    2005-09-20 19:29:26    Bind variable 1: uat_loy

Which returns my Server Key map i run directly against the database.

Please see attached logfile.



Cause


The cause was the copied component did not copy all component parameters correctly


Solution


Symptoms: After creating a new Loyalty Batch Engine Component, it does not start and gives the error message :
    "SBL-LTY-00109:
The process was unable to find an available server routing key to
register. Please check the loyalty server key definition of your
system."
    "SBL-SVR-01068: This component is not enabled for "Key Based Routing""

Troubleshooting:
    *The List of Values LOY_ENGINE_COMPONENT_KEYED for the component LoyTierEngineBatch is present in the system.
    *Indirect SupportWeb search lead to find that the SBL-SVR-01068 was caused by the advanced parameter KeyBasedEnabled.


Resolution:
    By using the srvrmgr command line utility :
        list advanced param KeyBasedEnabled for comp LoyEngineBatch
        ->True
        list advanced param KeyBasedEnabled for comp LoyTierEngineBatch
        -> False
        change param KeyBasedEnabled = TRUE for comp LoyTierEngineBatch
    *This allowed the component to run without this error but still the Tier changes were not changed.
    *Copying of component is very sensitive as there are many parameters to review.
    *By using again the srvrmgr command line utility:
        spool <myspool1.out>
        list param for comp LoyEngineBatch
        spool off
        spool <myspool2.out>
        list param for comp LoyTierEngineBatch
        spool off
    *By comparing the 2 spool files, it was found out that the Maximum Tasks had been left to 1 instead of 20.










Applies to:


Siebel Loyalty Engine - Version: 7.8.2.3 SIA [19221] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003

Product Release: V7 (Enterprise)

Version: 7.8.2.3 [19221] SVE Transp

Database: Microsoft SQL Server 2000 SP3

Application Server OS: Microsoft Windows 2003 Server

Database Server OS: Microsoft Windows 2003 Server



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



Symptoms


SBL-SVR-01068, SBL-BPR-00162Customer had an issue with the component ‘eLoyalty Processing Engine -
Realtime’.

On the server, we try to process a transaction with the Realtime component
using the 'Process' button in the GUI. We get the following error:
[1] Error invoking service
'LOY Processing Engine', method 'SubmitObjectForProcessing' at step 'Invoke Submit
Object'.(SBL-BPR-00162)
[2] Could not route message to LoyEngineRealtime with registered key
(null)
[3] no other server

Processing the transaction on the dedicated
client, the transaction is processed successfully.





Cause


The Loyalty component was not assigned and synchronised on the server


Solution


Unassigning and re-assigning the Loyalty Batch Engine component, then
synchronising the componets resolved the issue for this customer

תגובות

הוסף רשומת תגובה

פוסטים פופולריים מהבלוג הזה

Profile Attributes and Open UI

תמונה
Yes, Profile Attributes! As the ever attentive, up-to-date Siebel CRM expert that you are when you read this, you know that in Siebel Open UI (since version 15), it is no longer allowed/supported to  set  Profile Attributes from browser-side script. But  getting  them is not a problem, since the  GetProfileAttr  function works perfectly fine. Recently I found a few vanilla Profile Attributes that came quite handy in my work in Open UI JavaScript: Navigation Type : stores the navigation type such as "NAVIGATION_TAB" ActiveViewName : does what it says on the tin IsOpenUI : returns "1" when the application runs in Open UI Is SUI Theme : when "TRUE", the application theme is Synergy (aka SUI) Position:  returns the currently active position Primary Responsibility Name : guess what this one is… Profile Image : returns the URL of the user's profile image Org.Name : returns the name of the user's organization Here's a sample line of ...
המשך לקרוא

SBL-BPR-00191: The rowId of the active row of the primary buscomp '%1', '%2', does not match the Primary Id

Applies to: Product Release: V7 (Enterprise) Version: 7.5.3 [16157] ESN Database: Oracle 9.2.0.2 Application Server OS: Microsoft Windows 2000 Server SP 3 Database Server OS: Microsoft Windows 2000 Server SP 3 This document was previously published as Siebel SR 38-1386997031. Symptoms SBL-BPR-00191 We have a error with a workflow. This WF is excuted by policy when a particular activity is closed. The WF Business Object is 'Action'. Inside this WF, there is a subprocess that invokes a Business Service that creates a new activity. In a second subprocess, the region Id of this new activity is updated using the standar update method funcionality of Siebel workflow process. Error processing Siebel Operation for: Business Object 'Action' Business Component 'Action' Primary Id ''1-5NEI6' Operation 'Insert'(SBL-BPR-00100) -- The rowId of the active row of the primary buscomp 'Action', '1-4SNCV', does not match the Prima...
המשך לקרוא

SBL-SVC-00150

Applies to: Siebel CRM - Version: 7.5.3 [16157] and later   [Release: V7 and later ] z*OBSOLETE: Microsoft Windows 2000 Product Release: V7 (Enterprise) Version: 7.5.3 [16157] Database: IBM DB2/UDB 7.2 Application Server OS: Microsoft Windows 2000 Advanced Server SP 2 Database Server OS: IBM AIX 4.3.3 This document was previously published as Siebel SR 38-1153677971. Symptoms SBL-SVC-00150In callcenter (development environment) Group News administration > All News, when the ‘Status’ field of a news story is changed from ‘Submitted’ to ‘Completed’, the following error pops up. You cannot change the current field’s value from ‘Submitted’ to ‘Completed’. Rule validation failed: ‘[Total Approvers] = 0’ (SBL-SVC-00150) When the status field of a news story is changed from ‘Submitted’ to ‘Pending Approval’, the following error pops up. You cannot change the current field’s value from ‘Submitted’ to ‘Pending Approval’. R...
המשך לקרוא