רשומות

SBL-GEN-03005: No data found

Applies to: Siebel Anywhere - Version: 7.5.3.2 SIA [16168] and later   [Release: V7 and later ] Siebel Remote - Version: 7.5.3.2 SIA [16168] to 8.0.0.5 [20420]   [Release: to V8] z*OBSOLETE: Microsoft Windows 2000 Product Release: V7 (Enterprise) Version: 7.5.3.2 [16168] Life Sci Database: Oracle 9.2.0.2 Application Server OS: Microsoft Windows 2000 Server SP 2 Database Server OS: HP-UX 11i This document was previously published as Siebel SR 38-1536475261. Symptoms We have applied QF 0239 on our production on 10/01. We have also enabled UpgradeKitBuilder and Siebel Anywhere to distribute the QF to our Remote Users. In the time synchronization we are getting the error “Unable to find Upgrade kit path”. Please check the attached error screen shot. We have followed the exact steps as mentioned in ‘Service Request #: 38-1265040051’, which was recommended on SR#38-1516696757. This works fine on all our testing Environments. Cause Wrong setup Solution...

SBL-GEN-03002: Required parameter %1 is NULL

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 When the SQL for the Dynamic Candidate was generated, then the component crashes with SBL-GEN-03002 SBL-GEN-03002: Required parameter %1 is NULL Cause Technical Support was unable to duplicate the issue.  When creating an identically configured dynamic candidate, with criteria stored in the same tables as the customer candidate, the candidate runs successfully in the Siebel lab environment. Eventually, through testing the candidate successfully on multiple versions of the application in the lab environment, it was suspected that the dictionary cache file diccache.dat or the assignment cache file rulecache.dat in the customer's installation did not contain the proper database information required to successfully perform the assignment process.  This was suspected because the customer's dyn...

SBL-GEN-03001: Error allocating %1

Applies to: Error Message Area:Generic - GEN Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-GEN-03001: Error allocating %1 Scope This document is informational and intended for any user. SBL-GEN-03001: Error allocating %1 Explanation Unable to allocate memory for the specified entity. Most likely, memory resources on the machine are exhausted. Corrective Action Check available memory on the machine. Applies to: Siebel Assignment Manager - Version: 8.0.0.5 [20420] and later   [Release: V8 and later ] Information in this document applies to any platform. Symptoms Customer recently added some organizational skills to their skill tables by migrating the data from their development. Upon this change, the assignment manager component is crashing when restarted. This means no objects can be assigned and it is holding up their business. Customer is receiving a SBL-GEN-03001 error upon resta...

SBL-GEN-01000: System was unable to allocate sufficient memory

Applies to: Siebel eCommunications eMail Response - Version: 7.7.2 SIA [18325] and later   [Release: V7 and later ] Siebel Email Response - Version: 7.7.2 SIA [18325] and later    [Release: V7 and later] z*OBSOLETE: Microsoft Windows Server 2003 Product Release: V7 (Enterprise) Version: 7.7.2 [18325] Pub Sect Database: Oracle 9.2.0.6 Application Server OS: Microsoft Windows 2003 Server Database Server OS: Microsoft Windows 2003 Server This document was previously published as Siebel SR 38-2700877531. Symptoms We have an Comm Inbound Receiver on our Test machine that worked fine up until a certain day 2 months ago and then we have not been able to get it to work again since then. I have attached the log file. I have followed all recommendations on SRs regarding POP3, but I have not been able to find a solution. I can login to the pop3 server fine from the telnet command line and lock the mailbox, but Siebel never gets to the point of try...

SBL-GEN-00231 Process exited with error

Applies to: Siebel CRM - Version: 8.1.1 [21112] and later   [Release: V8 and later ] z*OBSOLETE: IBM AIX5L Based Systems (32-bit) ***Checked for relevance on 28-FEB-2011*** Symptoms Started  JMS Receiver Component remains with the " running " state, but  does not connect to JMS Server and does not start to pick up messages from the Queue . 1. Detailed  task log indicates no errors, but also does not show JMS works. 2. Siebel Server log file gets the "BL-GEN-00231 Process 2453540 exited with error" message for the JMS Receiver Component. The component self remains available. Changes Following setting were applied in Siebel Enterprise following information, given in the Siebel Bookshelf document: Transports and Interfaces: Siebel Enterprise Application Integration (EAI Volume 2): Java Business Service > Prerequisites for Implementing a Java Business Service . 1. The DLL parameter of the “JAVA” named subsystem (used by the JMS Receiver Component) has bee...

SBL-GEN-00230 Process exited with error

תמונה
Applies to: Siebel Reports - Version: 8.1.1.1 [21211] and later   [Release: V8 and later ] Information in this document applies to any platform. Symptoms When attempting to upload a report after initial installation the following error may appear in a dialog box : Process XMLPReportServer on Siebel Server siebsrvr1 terminated Log file Entries: <enterprise_name>.<server_name>.log: ServerLog ProcessExit 1 0000a8d64beb0070:0 2010-05-13 08:54:55 XMLPReportServer 696474 SBL-GEN-00230 Process 696474 exited with error - XMLPReportServer_xxx.log: XMLPReportLog XMLPReportInfo 3 000080c04bca7024:0 2010-05-13 08:54:54 BIP's using Security Model XMLPReportLog XMLPReportDetail 4 000080c04bca7024:0 2010-05-13 08:54:54 ReportName : Account List XMLPReportLog XMLPReportDetail 4 000080c04bca7024:0 2010-05-13 08:54:54 TemplateFileName : aclist.rtf XMLPReportLog XMLPReportDetail 4 000080c04bca7024:0 2010-05-13 08:54:54 TemplateFilePath : /appl/siebel/siebsrvr/xmlp/template...

SBL-GEN-00255 Process exited with error - Internal: Error during exec

Applies to: Siebel System Software - Version: 7.5.2.100 [15252] to 8.1.1.1 SIA [21211] - Release: V7 to V8 Generic UNIX Generic Linux Product Release: V7 (Enterprise) Version: 7.5.2.100 [15252] Database: IBM DB2 8.1 FixPack 6b Application Server OS: IBM AIX 5L 5.1 Database Server OS: IBM AIX 5L 5.1 This document was previously published as Siebel SR 38-3078571521. Symptoms SBL-GEN-00255, SBL-OSD-00220, SBL-OSD-02006, SBL-OSD-02011, SBL-OSD-00204, SBL-ADM-02049, SBL-GEN-00001, OSDmprotect The Siebel Server was running fine until a few weeks ago. Now we are unable to start the Siebel Server. The Siebel Gateway Name Server is running fine. When we start the Siebel Server by using start_server all command, the main thread starts (siebsrvr) but when it spawns the child threads (siebmtsh), they are not staying alive. No Siebel multithreaded server processes are started after running start_server all and no Application Object Manager log files are being generated. The SiebSrvr.lo...