Siebel Server does not startup and shows SBL-SMI-00152 error for component initialization (Doc ID 2057890.1)

Last updated on SEPTEMBER 22, 2017

Applies to:

Siebel Field Service - Version 8.1.1.11.12 [IP2013] and later
Information in this document applies to any platform.

Symptoms

The Siebel server would not start and the following errors are seen in Siebel enterprise logs:


ServerLog ProcessExit 1 000fd13855f816e4:0 2015-09-16 12:52:45 SRBroker 3188 TERMINATED Process 3188 was terminated
NotifyEvt NotifyErrors 1 000fd13855f816e4:0 2015-09-16 12:52:45 SBL-ADM-09152Could not send a notification message because we could not connect to the notification pipe (ENTSRVPRD_SRVTI339_7), retCode = (9609), nSysErr = (0)
GenericLog GenericError 1 000034de55f911c8:0 2015-09-16 12:57:39 (schedule.cpp (2296) err=1376409 sys=6) SBL-SMI-00153: SRBroker NOT READY Component is not ready.
GenericLog GenericError 1 000034de55f911c8:0 2015-09-16 12:57:39 (schedule.cpp (2237) err=1376408 sys=0) SBL-SMI-00152: TIMEOUT Component initialization for priority level 2 timed out after 300 s.
GenericLog GenericFatal 0 000034de55f911c8:0 2015-09-16 12:57:39 (schedule.cpp (2248) err=1376407 sys=0) SBL-SMI-00151: System component initialization timed out. System will shut down.
GenericLog GenericError 1 000034de55f911c8:0 2015-09-16 12:57:39 (schedule.cpp (708) err=1376407 sys=0) SBL-SMI-00151: System component initialization timed out. System will shut down.
GenericLog GenericError 1 000034de55f911c8:0 2015-09-16 12:57:39 (schedule.cpp (146) err=1376407 sys=0) SBL-SMI-00151: System component initialization timed out. System will shut down.
ServerLog ProcessExit 1 000fd13855f816e4:0 2015-09-16 12:57:39 SCBroker 4304 TERMINATED Process 4304 was terminated
GenericLog GenericError 1 000fd12d55f816e4:0 2015-09-16 12:57:39 (listener.cpp (434) err=1376297 sys=126) SBL-SMI-00041: Internal: Could not start the scheduler thread (1376407)
GenericLog GenericError 1 000fd12d55f816e4:0 2015-09-16 12:57:39 (lstnsvc.cpp (181) err=1376297 sys=0) SBL-SMI-00041: Internal: Could not start the scheduler thread (1376407)
ServerLog ServerShutdown 1 000fd12d55f816e4:0 2015-09-16 12:57:39 Scheduler error

SCBroker logs shows below errors:

2021 2015-09-16 12:52:39 0000-00-00 00:00:00 -0300 00000000 001 ffff 0001 09 SCBroker 3145731 4304 3044 D:\Siebel\8.1.1.11.0\ses\siebsrvr\log\SCBroker_0003_3145731.log 8.1.1.11 SIA [23030] ENU
GenericLog GenericError 1 0000000255f910d0:0 2015-09-16 12:52:39 (scbcomp.cpp (447) err=4653071 sys=0) SBL-SCB-00015: The component is down or not available on this server.
GenericLog GenericError 1 0000000255f910d0:0 2015-09-16 12:52:39 (scbcomp.cpp (266) err=4653071 sys=0) SBL-SCB-00015: The component is down or not available on this server.

Upon Siebel server startup, the SRBroker component does not initialize and the SCBroker logs for similar timestamp shows that the component is down. The system components were not initializing and timing out and this could be the reason why the Siebel server was not starting up.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms