siebel

Applies to: Siebel System Software - Version 8.0.0.1 [20408] to 8.2.2.2 SIA[23016] [Release V8] Information in this document applies to any platform. Product Release: V8 (Enterprise) Version: 8.0 [20405] Database: Oracle 10.1.0.4 Application Server OS: Red Hat Linux 4.0 Database Server OS: Sun Solaris 9 This document was previously published as Siebel SR 38-3467659813. Symptoms Hi, we're trying to setup a PoC of Siebel 8.0 on Linux Redhat 4.0 and had encountered issue while trying to config LDAP authentication and an error had ocurred in the OM log file. IBM LDAP 6.0 Client is installed and is using OID 10.1.2 as the LDAP Server. We have repreatedly verified LDAPparameters many times and believed we have setup the right parmeters. We got the following error in the log file: SBL-SEC-00102 An error occurred loading the security adapter library. Please contact your system administrator for assistance. SBL-DAT-00562 An error occurred loading the security adapter library. Ple...

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...

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 ==== O...

Applies to: Siebel eCommunications - Version: 8.1.1.3 SIA[21219] and later   [Release: V8 and later ] Information in this document applies to any platform. Symptoms Unable to start the Siebel Server as SRBroker and SCBroker logs are showing the following error: ----------------------------------------------------------------- Error: cannot get version of installed components ( sia) SBL-SMI-00147: Version check failed because: Error: cannot get version of installed components ( sia) Cause The customer found the following root problem himself: Inside the <Siebel Server Root>'s BIN folder, the sub-folders SIA and PTK had (accidentally) been moved to the PTB sub-folder. PTK was not necessary, because they only used ENU and PTG, but SIA was. Solution restoring the SIA subfolder with its original content in <Siebel Server Root> fixed the error SBL-SMI-00147: Version check failed because: Error: cannot get version of installed components ( sia) Applies to: Siebel Sys...

Applies to: Siebel Workflow - Version: 7.7.2.10 [18385] to 8.0 [20405] - Release: V7 to V8 Information in this document applies to any platform. ** Checked for relevance on 27 February 2012** Symptoms Customer is facing recent and intermittent unavailability of WfProcMgr component installed in one server. Customer has noticed one occurrence this Sunday 02/15 at 10:30 AM and  02/16 3:20 AM. When it occurred they were able to restart the server. Customer is not able to always restart the siebel server because the application does not respond in a timely manner. Since WfProcMgr seems unavailable for some reason SISNAPI errors in SRBroker logs were found also as a consequence of this component being unavailable it seems that records in S_ESCL_REC are increasing. The records in S_ESCL_REC seems to be associated to triggers created for assignment of campaigns. No recent changes were made on wf policies or configuration. In the enterprise log and confirmed that WfProcMgr became unavailabl...

Applies to: Siebel System Software - Version 7.8.2.5 [19227] and later z*OBSOLETE: Microsoft Windows Server 2003 Product Release: V7 (Enterprise) Version: 7.8.2.5 [19227] Database: Oracle 10.1.0.4 Application Server OS: Microsoft Windows 2003 Server SP1 Database Server OS: Sun Solaris 9 This document was previously published as Siebel SR 38-3388527211. """"Checked for relevance on 23-MAY-2012"""" Symptoms The connections from webMethods to Siebel are intermittently failing with an error code 8234 on webMethods. Here is a sequence of events observed in logs: 1. webMethods attemps to login and open a connection. 2. a new session is instantiated in Siebel and waits, but does not proceed with authentication. 3. webMethods request reports 8234 with a timeout after 2 mins. 4. webmethods opens another connection. This goes through successfully. 5. The first Siebel session terminates with a timeout after 45 mins. The siebel log prints the typical paramet...