SBL-SMI-00151: System component initialization timed out. System will shut down.

Applies to:

Siebel System Software - Version 8.0 [20405] to 8.2.2.2 SIA[23016] [Release V8]
Information in this document applies to any platform.
Error Message Area:Server Management Infrastructure - SMI
Version:Siebel 8.0
***Checked for relevance on 20-Feb-2013***

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-SMI-00151: System component initialization timed out. System will shut down.

Scope

This document is informational and intended for any user.

Details

Explanation

Startup of system components timed out.

Corrective Action

Check the server log file for any errors related to system components. If there are no errors or a system component is expected to take a long time to start, increase the Component Priority Level Timeout parameter.

Applies to:

Siebel eCommunications - Version: 8.0.0.3 [20416] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

==== ODM Issue Clarification ====

On : 8.0.0.10 [20436] version, System Admin

When attempting to start siebel apps server after patching to 8.0.0.10,
the following error occurs.

ERROR
-----------------------
GenericLog GenericError 1 000092164eeab1a0:0 2011-12-15 20:36:11 (sccnmsys.cpp (1305) err=2883609 sys=0) SBL-SCC-00025: No value found in the Gateway. Default value in the repository is used.
ror 1 0000369c4eea7146:0 2011-12-15 20:54:48 (schedule.cpp (944) err=1376408 sys=0) SBL-SMI-00152: TIMEOUT Component initialization for priority level 2 timed out after 300 s.
GenericLog GenericFatal 0 0000369c4eea7146:0 2011-12-15 20:54:48 (schedule.cpp (955) err=1376407 sys=0) SBL-SMI-00151: System component initialization timed out. System will shut down.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Patch from 8.0.0.3 to 8.0.0.10FP
2. Start enterprise
3. Not starting the enterprise

Cause

After further investigation, it was found that home directory for the siebel user was pointing to a wrong directory path other than the directory having the siebel server installed

Solution

Resolution steps :

1. Home directory for the siebel user must point to same directory where siebel installed
2. Once point to correct directory restart the enterprise