SBL-SMI-00152: TIMEOUT Component Initialization for Priority Level %1 Timed Out After %2



Applies to:


Siebel System Software - Version: 8.0.0.1 [20408] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Error Message Area:Server Management Infrastructure - SMI

Version:Siebel 8.0



Purpose


This document is intended to provide cause and corrective action
information about Siebel Error Message SBL-SMI-00152: TIMEOUT Component
initialization for priority level %1 timed out after %2 s.



SBL-SMI-00152: TIMEOUT Component Initialization for Priority Level %1 Timed Out After %2 s.



Explanation


Startup of components for this priority level timed out.


Corrective Action


Check the enterprise server log to see which component timed-out during initialization.
An example of a trace from the ent81.ss81[1].log log file may be similar to the following:


ent81.ss81[1].log:GenericLog
GenericError 1 0000132b4b4c68fa:0 2010-01-12 11:37:55 (schedule.cpp
(2162) err=1376408 sys=0) SBL-SMI-00152: TIMEOUT Component
initialization for priority level 1 timed out after 300 s.

ent81.ss81[1].log:ServerLog
ProcessExit 1 0000132c4b4c68fa:0 2010-01-12 11:43:00 SvrTblCleanup
26931 SBL-OMS-00101 Process 26931 exited with error - Error %1 loading
product configuration information


In this case, a
cursory review of the log files in the Siebel log directory indicated
the the SCBroker log was updated at about the same time as the
enterprise log file.  Reviewing the contents of the latest SCBroker log
file, SCBroker_0002_2097155[1].log, revealed the following trace:


SCBroker ScbInfo 3 000000044b4c6929:0 2010-01-12 11:36:24 Processing url: http://appserver:2381/ent81/sccobjmgr_enu

SCBroker_0002_2097155[1].log:GenericLog
GenericError 1 000000044b4c6929:0 2010-01-12 11:36:24 (scbcomp.cpp
(445) err=4653071 sys=0) SBL-SCB-00015: The component is down or not
available on this server


From the above trace, it
appears the SCBroker cannot establish a session with the call center
object manager via this URL: http://appserver:2381/ent81/sccobjmgr_enu

To troubleshoot this issue, try the following:

Option
1. Confirm that the Object Manager and SRBroker are up and available on
the application server. Restart these components, if necessary, and see
if this resolves the issue.  It is also a good idea to try to ping the
application server with the full URL and confirm it is available.  If
these steps do not resolve the issue, continue to Option 2, below:

Option 2. Setup Environment To Capture Detailed Traces at SWSE, APP and OS Level:

1. Turn up event logging for SWSE from the command shell:
Enter the following commands and set the following environment variables:

SIEBEL_LOG_EVENTS=4; export SIEBEL_LOG_EVENTS
SIEBEL_SESSMGR_TRACE=1; export SIEBEL_SESSMGR_TRACE
SIEBEL_SISNAPI_TRACE=1; export SIEBEL_SISNAPI_TRACE


B. Turn up event logging on the OM and the following components to level 4:


1. Open a command shell and start the “srvrmgr” CLI utility (should
be under the $SIEBEL_ROOT/siebsrvr/bin) and then enter the following
commands (substitute your parameters between <> marks):

(On UNIX): srvrmgr -g <gateway_name> -e <enterprise_name> -u <sadmin> -p <password>
(On Windows): srvrmgr /g <gateway_name> /e <enterprise_name> /u <sadmin> /p <password>

spool srvrmgr_trace.txt
list servers
list components
change evtloglvl % = 4 for comp SCCObjMgr_enu
change evtloglvl % = 4 for comp SRBroker
change evtloglvl % = 4 for comp SCBroker
change evtloglvl % = 4 for comp SCProc
change evtloglvl % = 4 for comp CommSessionMgr
change evtloglvl % = 4 for comp SvrTblCleanup
spool off
quit

C. Note date and time. Stop and restart the web server and siebsrvr. Wait 5 minutes.

D. Reproduce the issue end-to-end, indicate date and time per step, attach log files:


1. Note date and time. Open a browser window, and try to access the
application (call center) in the usual manner, and reproduce the issue,
and be sure to capture a complete screen shot

2. Note date and time. Open a command shell on the server running the OM and execute:
netstat -an > netstat_siebsrvr_<name>.out

3. Note date and time. Stop the web server and siebsrvr.
Compress and attach to this SR for review:
* screen shot
* srvrmgr_trace.txt
* netstat*.out files
* all the log files generated during this trace session from the web server and application server log directories
(please aggregate the files by server name, or type (eg. websrvr_<name>, siebsrvr_<name>)

4. Repeat steps A and B, but return to normal logging levels.

E. Note date and time. Restart the web server and siebsrvr.

F.
Indicate which enterprise components are running on which OS (eg. Web
server on UNIX, etc.).  Zip-up and attach the log files to the SR for
review.

תגובות

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

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

FINS Data Transfer Utilities

תמונה
The best thing while working on siebel is you are never short of options. Recently we had requirement of updating a Service request from contact. Finally we did that using "EAI Siebel Adapter" business service. However during that time i came across another business service "FINS Data Transfer Utilities" popularly known as DTU business service. As i was not having prior knowledge of it going by the rule of not learning swimming lessons while drowning i decided not to go for it. Lately i have tried to explore this service and trust me it can do wonders. Here is a sample example update of Service Request from contact. We need to follow below steps in order to understand strength of this business service. 1 - Navigate to Site Map. Go to Administration - Application -> Data Map Administration tab. Create a new Record with following options: Name: Service Request Test Source Business Object: Contact Destination Business Object: Service Request Here the source business
המשך לקרוא

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

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