siebel

Applies to: Siebel Handheld - Version 7.5.3.9 PDA [16194_2] to 8.2.2.3 SIA [23021] [Release V7 to V8] Microsoft Windows CE Product Release: V7 (Enterprise) Version: 7.7.0.1 [AN307] Database: Oracle 9i Application Server OS: Microsoft Windows 2003 Server Database Server OS: Sun Solaris 9 This document was previously published as Siebel SR 38-1719219591. ***Checked for relevance on 27-Mar-2013*** Symptoms SBL-SVR-01051, SBL-NET-01218 We are experiencing problems syncronising our Siebel Handheld devices with the Server using DSS. It has worked in the past, but since the server went down during a sync, we can't get it to work again. We continue to get these error, taken from the log on the HH device. SYSTEM    0xd290894e    01/17/2005 10:00:40    Loading Metadata. ERROR    0xd290894e    01/17/2005 10:00:40    0x7766: Failed to load configuration. Metadata file is absent ...

Applies to: Siebel Life Sciences CRM - Version: 8.1 [21039] to 8.1.1 [21112] - Release: V8 to V8 Microsoft Windows (32-bit) Symptoms Customer changed the sadmin's password following the Siebel Security Guide > Changing or Adding Passwords > Changing Passwords > Changing System Administrator Passwords on Microsoft Windows, but after changing the password the Siebel Server did not come up . In the Siebsrvr.log file it was found the following error message: GenericLog GenericError 1 00000002499b0e08:0 2009-02-17 16:41:28 (scmnsclnt.cpp (135) err=2555922 sys=0) SBL-SCM-00018: Could not open connection to Siebel Gateway configuration store (siebel03:2320). The following errors were just a symptom of the failure to connect to the Siebel Gateway: GenericLog GenericError 1 00000002499b0e08:0 2009-02-17 16:41:28 (scisvc.cpp (1391) err=1311765 sys=0) SBL-SVR-01045: No components are configured. GenericLog GenericError 1 00000002499b0e08:0 2009-02-17 16:41:28 (scfsis.cpp (27...

Applies to: Siebel Assignment Manager - Version 7.8.2 [19213] to 8.1.1 [21112] [Release V7 to V8] Information in this document applies to any platform. Symptoms Assignment Manager was offline with error code SBL-SVR-01043.   Log Snippet: SmiLayerLog Error 1 0 2009-05-17 16:35:06 Internal: Failed to schedule an MTServer (error SBL-SVR-01043: The component is not enabled) Customer had examined Metalink Doc ID 521381.1 and verified this condition did not exist in his environment. Changes Customer has recently undergone Oracle Upgrade from 9i to 10g. There were issues with the upgrade but they believed them to be resolved. A couple days post resolution, customer noticed some issues with Assignment. After a service restart, the component became completely non-functional Cause Siebns.dat file shows component as enabled but offline. Review of the more detailed logs showed 2 errors in vanilla Dynamic Candidates for Assignment Object TM Contact Dynamic Candidate Team Staging Minor # ...

Applies to: Siebel Reports - Version 7.7.2.10 SIA [18385] and later Oracle Solaris on SPARC (64-bit) Product Release: V7 (Professional) Version: 7.8.2.3 [19221] Database: Oracle 9.2.0.8 Application Server OS: Sun Solaris 10 Database Server OS: Sun Solaris 10 This document was previously published as Siebel SR 38-3270891771. Symptoms SBL-SVR-01042, SBL-SMI-00121 Hi, After applying the patch 7.8.2.5, the report server is Not working. I have attached the log file for your reference. Please take a look at this and advice soon. Below is the error. (sasess.cpp (711) err=2001042 sys=0) SBL-SVR-01042: Internal: Communication protocol error while instantiating new task SBL-SMI-00121: Internal: SISDecodeRawMessage() failed Cause Configuration/ Setup Solution Message 1 Description Hi, After applying the patch 7.8.2.5, the report server is Not working. I have attached the log file for your reference. Please take a look at this and advice soon. Below is the error. (sasess.cpp (711) err=2001042 s...

Applies to: Siebel Call Center - Version 8.0.0.7 [20426] to 8.1.1.3 SIA[21219] [Release V8] Information in this document applies to any platform. *** Checked for relevance on 05-Dec-2012 *** Goal What is the meaning of error "SBL-SVR-01031: Invalid Parameter" in the SRProc logs? Fix Log files of Server Request Processor (SRProc) show repeated 'SBL-SVR-01031: Invalid Parameter' error messages whenever a SQL statement has parameters bound to it. This behavior was reported in BUG 10642871 -"SRProc: Repeated Error: SBL-SVR-01031: Invalid Parameter". This error is benign and can be ignored. This bug has been fixed in 8.1.1.4 fix pack. Applies to: Siebel System Software - Version: 8.0.0.8[20430] and later   [Release: V8 and later ] Information in this document applies to any platform. Symptoms Customer has done fresh installation of  version 8.0 and applied patchset 8.0.0.10 on top of it. After installation all servers and components were up and running. Server...

Applies to: Siebel Email Response - Version 7.8 [19038] to 8.1.1.8 SIA [23012] [Release V7 to V8] Information in this document applies to any platform. Symptoms On Siebel 8.1.1.3 using Communications Outbound Manager component to send out Outbound Requests. When Siebel tries to send out outbound requests using CommOutboundMgr component it fails to send the emails. The following errors can be observer on Communication Outbound Manager component task for the outbound request with event trace log level increased: SrmRouting SrmRoutingSubevent 4 0000006d50341600:0 2012-08-22 01:00:45 SNDREQ  IDS  : FLAGS [1] : REQID [2-4OFLL-1BFG] : SRBSESSID [a5f315e8200003SBLGW] : SRMCONNID [11]  SRC  : SRC_ID [] : SRC_KEY []  DEST : ROUTE_ID [FSMSrvr] : ROUTE_KEY [] : ROUTE_SRVR [] : LANG_CODE [ENU] : CODE_PAGE [1200] GenericLog GenericError 1 0000006d50341600:0 2012-08-22 01:00:45 (srmconn.cpp (2571) err=1180682 sys=0) SBL-NET-01034: The SISNAPI connection was closed by the p...

Applies to: Siebel System Software - Version 7.8.2 [19213] and later z*OBSOLETE: Microsoft Windows Server 2003 Product Release: V7 (Enterprise) Version: 7.8.2 [19213] Database: Oracle 9.2.0.5 Application Server OS: Microsoft Windows 2003 Server SP1 Database Server OS: Sun Solaris 2.8 This document was previously published as Siebel SR 38-2701371851. Symptoms SBL-SVR-01014, SBL-NET-01023, SBL-NET-01553, SBL-NET-01205, SBL-NET-00000, SBL-NET-01931, SBL-NET-01924 We are trying to enable SSL in one of our environments. We have run the SSL configuration utilities for both SWE and the Enterprise/Server (only one Server in the Enterprise). SWE and Server are co-located on the same server. We are using an internal CA that is based on an Entrust.net certificate. The SSL works fine from a raw IIS web server perspective. We are using the .PEM file from the CA for the IIS server as the "Certification File Name" and an exported and converted .PEM file for the "Certificate Authority ...