siebel

Applies to: Siebel System Software - Version 7.7.1 [18306] and later Information in this document applies to any platform. Error Message Area:Server Request Broker - SRB Version:Siebel 7.7 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-SRB-00061: Process %1 on Siebel Server %2 terminated Scope This document is informational and intended for any user. Details Explanation The process named in the error must have been shutdown on the server mentioned and could not route the message to the particular process. Corrective Action Check to make the named process is still running on the server mentioned. If not, start the component. Applies to: Siebel Sales Volume Planning - Version: 7.7.2.2 SIA [18356] to 7.8.2 SIA [19213] - Release: V7 to V7 Siebel Consumer Goods - Version: 7.7.2.2 SIA [18356] to 7.8.2 SIA [19213]   [Release: V7 to V7] Siebel CRM - Version: 7.7.2.2 SIA [18356] to 7.8.2 SIA ...

Applies to: Siebel System Software - Version: 8.1 [21039] and later   [Release: V8 and later ] Information in this document applies to any platform. Error Message Area:Server Request Broker - SRB Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-SRB-00051: Could not find connection to the component. Scope This document is informational and intended for any user. SBL-SRB-00051: Could not find connection to the component. Explanation There is no connection to the component. The component may be down. Corrective Action Check to make sure that: SRBoker is still running. Batch mode components are still active. Try restarting the component to re-establish the connection. Applies to: Product Release: V7 (Enterprise) Version: 7.8.2 [19213] Pub Sect Database: IBM DB2 for zOS and OS/390 v8 Application Server OS: IBM AIX 5L 5.2 Database Server OS: IBM zOS This document was previously published as ...

Applies to: Siebel Workflow - Version: 7.7.2.5 [18368] to 8.1.1 [21112] - Release: V7 to V8 Information in this document applies to any platform. This document was previously published as Siebel SR 38-3070028991. Symptoms Customer has several custom workflow monitor agent components created. These work fine until the last few days where the agents fail with the following logs: SrmLayerLog    Error    1    0    2006-06-19 16:51:28    (srbroute.cpp(2052) err=5700035 sys=0) no other server SrmLayerLog    Error    1    0    2006-06-19 16:51:28    (srbmsgfn.cpp(387) err=5700047 sys=0) Could not route message to WfProcMgr with registered key (null) GenericLog    GenericError    1    0    2006...

Applies to: Siebel System Software - Version 7.5.2.100 SIA [15252] to 8.1.1.4 SIA [21225] [Release V7 to V8] z*OBSOLETE: Microsoft Windows 2000 Product Release: V7 (Enterprise) Version: 7.5.2.100 [15252] Life Sci Database: Oracle 8.1.7 Application Server OS: Microsoft Windows 2000 Advanced Server SP 2 Database Server OS: Microsoft Windows 2000 Advanced Server SP 2 This document was previously published as Siebel SR 38-1020255192. CHECKED FOR RELEVANCE ON 1-FEB-2013 Symptoms SBL-SMI-00033, SBL-SRB-00041, SBL-NET-01034 Typical error is as follows: 2021 2003-06-04 00:30:05 2003-06-04 00:30:05 +0100 00000042 001 ffff 0001 09 SRBroker 36931 548 592 E:\sea752\siebsrvr\log\SRBroker_36931.log 7.5.2.102 [15255] ENUENU GenericLog    GenericError    1    2003-06-04 00:30:05    (smimtses.cpp 18(352) err=2100033 sys=0) SMI-00033: The client exited without closing the SISNAPI connection TaskCfgExit   ...

Applies to: Siebel Workflow - Version: 7.7.2.4 SIA [18365] and later   [Release: V7 and later ] IBM AIX on POWER Systems (64-bit) Product Release: V7 (Enterprise) Version: 7.7.2.4 [18365] Auto Database: Oracle 9.2.0.7 Application Server OS: IBM AIX 5L 5.2 Database Server OS: IBM AIX 5L 5.2 This document was previously published as Siebel SR 38-3011977185. Symptoms We are trying to Integrate QAS with Siebel, and are experienceing some difficulties. We have a picklist that uses a virtual Business component which is populated with data from the PAF file via the QAS DLLs. The script calls a workflow process located on the windows server, but seems to fail each time and outputs a msg to our error handling tables: Error: SiebelError: Could not route message to NWfProcMgr with registered key (null) no more remote SRB instance Error near no filename:189 [InvokeMethod()].       from no filename:189 [Query()]     ...

Applies to: Siebel Workflow - Version: 7.7.2.4 SIA [18365] and later   [Release: V7 and later ] IBM AIX on POWER Systems (64-bit) Product Release: V7 (Enterprise) Version: 7.7.2.4 [18365] Auto Database: Oracle 9.2.0.7 Application Server OS: IBM AIX 5L 5.2 Database Server OS: IBM AIX 5L 5.2 This document was previously published as Siebel SR 38-3011977185. Symptoms We are trying to Integrate QAS with Siebel, and are experienceing some difficulties. We have a picklist that uses a virtual Business component which is populated with data from the PAF file via the QAS DLLs. The script calls a workflow process located on the windows server, but seems to fail each time and outputs a msg to our error handling tables: Error: SiebelError: Could not route message to NWfProcMgr with registered key (null) no more remote SRB instance Error near no filename:189 [InvokeMethod()].       from no filename:189 [Query()]     ...

Applies to: Siebel CTI - Version: 7.5.3.8 [16192] and later   [Release: V7 and later ] z*OBSOLETE: Microsoft Windows 2000 Product Release: V7 (Enterprise) Version: 7.5.3.8 [16192] Database: Oracle 9.2.0.4 Application Server OS: Microsoft Windows 2000 Advanced Server SP 3 Database Server OS: Sun Solaris 8 This document was previously published as Siebel SR 38-2239792261. Symptoms During a recent deployment of Siebel 7.5.3.8/Genesys Voice Adapter 6.5.201.13, we encountered a "Call Stack" on the dedicated Siebel Communications Server. These Call Stacks were associated with 1) Problems with CTI Toolbar 2) Agents being logged out of tool bar 3) Agent calls being dropped. Some of the text below is: - CALL STACK - <invalid> 0x5dda484 GenModel +0x5b594 GenModel +0x10f20 = ReleaseTeleset() +0x1e70 <invalid> 0x868b57f1 This Call Stack occured 5 times during our initial deployment and subsequently was associated with these errors in the Siebel Communications Manager Logs...