SBL-SVR-01043



Applies to:


Siebel Assignment Manager - Version 7.8.2 [19213] to 8.1.1 [21112] [Release V7 to V8]
Information in this document applies to any platform.



Symptoms


Assignment Manager was offline with error code SBL-SVR-01043.   Log Snippet:



SmiLayerLog Error 1 0 2009-05-17 16:35:06
Internal: Failed to schedule an MTServer (error SBL-SVR-01043: The
component is not enabled)




Customer had examined Metalink Doc ID 521381.1 and verified this condition did not exist in his environment.



Changes


Customer has recently undergone Oracle Upgrade from 9i to 10g. There
were issues with the upgrade but they believed them to be resolved. A
couple days post resolution, customer noticed some issues with
Assignment. After a service restart, the component became completely
non-functional



Cause


Siebns.dat file shows component as enabled but offline.


Review of the more detailed logs showed 2 errors in vanilla Dynamic Candidates for Assignment Object TM Contact







Dynamic Candidate Team Staging Minor # TM Contact
Geo Zone Hierarchy Division Driven in Assignment Object TM Contact has
an invalid Team Type. Team Type should be either Position, Employee, or
Organization. Please check the configuration in Tools."

and



Dynamic candidate Operational # TM Contact Geo
Zone Hierarchy Division Driven in assignment object TM Contact is not
configured correctly.





Solution


To resolve the Dynamic Candidate Issues:


Dynamic Candidate Staging Minor # TM Contact Geo Zone Hierarchy
Division Driven had no Team Type. Team Type was set to the vanilla
setting of position

and

Dynamic Candidate Operational # TM Contact Hierarchy Division Driven -
it had it's candidate component set, but did not have the Candidate ID
column. This was set to the vanilla setting of POSTN_ID



rulecache.dat and diccache.dat were renamed and regenerated.



This resolved all Assignment Manager Errors and the component would now function on another server.



To resolve the issue of the siebns.dat showing the component as
"offline", the customer unassigned the component from the server,
synchronized and reassigned.












Applies to:


Siebel System Software - Version 7.8.2.2 [19219] and later
z*OBSOLETE: Microsoft Windows Server 2003

Product Release: V7 (Enterprise)

Version: 7.8.2.2 [19219]

Database: Oracle 9i

Application Server OS: Microsoft Windows 2003 Server SP1

Database Server OS: Sun Solaris 9



CHECK ON CURRENCY 2-NOV-2012







Symptoms


SBL-SVR-01015, SBL-SVR-01043, SBL-SMI-00033, SBL-NET-01034, SBL-NET-01033, SBL-ADM-01044, SBL-SCB-00015, SBL-SCB-00011


Each night a cold DB backup is taken on each environment. This is affecting a number of components on the Siebel server:

Transaction Processor
Transaction Merger
Transaction Router
Server Tables Cleanup

These
components need to be restarted each morning as the backup is affecting
them. Hence scripts were used to shutdown the siebel server 15 mins
before backup is taken and another to restart it in the morning. On
another environmnet the shutdown script appears to hang (i.e batch job
does not complete). All the parameters are correct as the command would
not run otherwise.



Cause


Configuration/ Setup



Solution


The customer's script:

D:\sea78\test\siebsrvr\BIN\srvrmgr /g UKGateway /e siebtest /s SiebTest1 /u sadmin /p password /c "shutdown appserver SiebTest1"

In
review of the customer's component log files, could see that there was a
problem with one or more components shutting down. The "shutdown
appserver" command issued from the Server manager command-line is a
synchronous process, thus the command will block until all tasks in the
server have exited. There could be a problem stopping one or more
components, caused either by the components themselves, or caused by the
synchronous nature of the shutdown process (ie. one component is
waiting on a response from another component, or the Siebel server -
that may have already been shutdown).

The customer was recommended to use the Windows command, net stop. The net stop command is used as follows:

net stop <service>

For example:

net stop SiebSrvr

Which would stop the service called SiebSrvr.

Assuming
you do not have any problem stopping your Siebel Server service using
the Windows' Services utility, then you should not experience a problem
with using the net stop command to stop the Siebel Server service.



תגובות

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

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

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...
המשך לקרוא