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: 7.0.4 [14068] and later   [Release: V7 and later ] Generic Windows Area(s):System Administration Release(s):V7 (Enterprise), V7 (Professional) Database(s):All Supported Databases App Server OS(s):HP-UX, Solaris, AIX Latest release tested against:V7 (Enterprise) Keywords:Solaris, accept, failed, shutdown, signal, SIGPIPE, core, SBL-SMI-00006, hang, logout, users This document was previously published as Siebel Alert 1206. Description Process signals are used for the purpose of interrupting normal process execution and informing it about a certain error condition that needs some recovery activity by a process or by a certain thread of a process. These signals could be generated by the operating system, or could be invoked via C/C++ code. Examples: A custom C++ application (library) is invoked from a Call Center Object Manager user or thread via the Siebel eScript SELib mechanism. The library connects to a process or files via ...

Applies to: Siebel System Software - Version: 7.7.2.2 [18356] and later   [Release: V7 and later ] z*OBSOLETE: Microsoft Windows Server 2003 Product Release: V7 (Enterprise) Version: 7.7.2.2 [18356] Database: Oracle 9.2.0.6 Application Server OS: Microsoft Windows 2003 Server SP1 Database Server OS: Microsoft Windows 2003 Server SP1 This document was previously published as Siebel SR 38-3194443421. Symptoms Customer is experiencing a recurring issue with their Web Client environment. More times a day the following error is logged in the SCBroker log file. SBL-SCB-00011: Failed to connect to pipe (SEBL_11_4248) on process 4248 At this moment no users can logon anymore and the ones which are logged on receive the error "The Siebel Server is experiencing problems". By re-starting the EAFObjMgr_enu the issue gets resolved for the time being. But it's unclear why this happens. I attached a full .zip file of the \log directory. The SCBroker component has evtloglvl %=4. This is...

Applies to: Siebel CRM - Version: 7.8.2.8 SIA [19237] and later   [Release: V7 and later ] Information in this document applies to any platform. Goal The following errors are happening in the scbroker files - err=7100008 sys=0) SBL-SCB-00008: El componente (ecommwirelessobjmgr_esn) no estM-CM-! disponible en este servidor - why ? Solution An1: Hi Clemente, Thank you for taking my call earlier. As discussed I believe your issue is related to the your VirtualServer section in your lbconfig.txt containing servers where OM's are not running. The following 7.8 bookshelf reference explains how to configure your lbconfig.txt and eapps.cfg to cater for this scenario > Siebel System Administration Guide > Configuring the System Architecture > Configuring Siebel Server Load Balancing > Optimizing the Siebel Load-Balancing Performance. Please review this section and modify your lbconfig.txt and eapps.cfg accordingly. I suggest you test this configuration on your pre-pro...

Applies to: Error Message Area:Server Infrastructure - SCB Version:Siebel 8.0 and later Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-SCB-00007: Enterprise name ( %1) in the request is invalid. Scope This document is informational and intended for any user. SBL-SCB-00007: Enterprise name ( %1) in the request is invalid. Explanation Enterprise name in connect string could be wrong. Corrective Action Check eapps.cfg configuration - make sure that enterprise name matches that of the server. Applies to: Product Release: V7 (Enterprise) Version: 7.8.2.3 [19221] Database: IBM DB2 8.2 Application Server OS: Microsoft Windows 2003 Server Database Server OS: IBM AIX 5L 5.2 This document was previously published as Siebel SR 38-3365847407. Symptoms SBL-SCB-00007What is the error code SBL-SCB-00007. I was not able to retrieve anything from the search on this from the knowledge base. In our production environment we get a erro...