| Siebel SQLs/Error Messages > SBL-GEN-05043, SBL-GEN-05044, SBL-GEN-05045, SBL-GEN-05046 , SBL-GEN-09401, SBL-GEN-09501
SBL-GEN-05031 Key type does not match operationSBL-GEN-05031 Key type does not match operation
SBL-GEN-05032 Request object internal buffer is not initialized
SBL-GEN-05033 Unable to get list of request objects
SBL-GEN-05034 Attempt to create already existing key
SBL-GEN-05035 Method not implemented
SBL-GEN-05036 No child nodes in sub-tree to read
SBL-GEN-05037 Request was not executed, possibly due to prior error
SBL-GEN-05038 Internal: error %1 creating scrParam.
SBL-GEN-05039 The Gateway parameter %1 does not exist.
SBL-GEN-05040 Internal: error %1 in scbResCmd::Init().
SBL-GEN-05041 Error %1 adding the nameserver scheduling rule to Resonate.
SBL-GEN-05042 A login is required to access data from the name server.
SBL-GEN-05043 The specified user does not have the proper privileges to connect to the name server.
SBL-GEN-05043: The Specified user does not have the Proper Privileges to connect to the Name Server (Doc ID 1455217.1)
APPLIES TO:
Siebel eClinical - Version 8.1.1.5 SIA [21229] and laterInformation in this document applies to any platform.Checked for relevance 08 Jan 2014SYMPTOMSAfter server reboot unable to start the siebel service.
Observed the below errors in NameServer.log file:
2009-09-18 16:14:49 select T2.NAME from SIEBEL.S_PER_RESP T1, SIEBEL.S_RESP T2, SIEBEL.S_USER T3 where T1.RESP_ID=T2.ROW_ID AND T1.PER_ID=T3.PAR_ROW_ID AND T3.LOGIN='SADMIN'2009-09-18 16:14:49End 10 Worst Performing Queries ***********2009-09-18 16:14:49 (SQLFreeEnv) Env Handle: 812926856, Time: 0.004ms2009-09-18 16:14:49 Invoking SecurityGetRoles for user sadmin.2009-09-18 16:14:49 user sadmin has 246 responsibilities.2009-09-18 16:14:49 (client.cpp (325) err=5043 sys=0) SBL-GEN-05043: The specified user does not have the proper privileges to connect to the name server.
CAUSES
ADMIN user got deleted.
SOLUTION
After restoring the SADMIN user and restarting the gateway along with Siebel server resolved the issue.
Siebel Server Fails to Start (Doc ID 1471909.1)
APPLIES TO:Siebel Call Center - Version 8.1.1.5 SIA [21229] and laterMicrosoft Windows (32-bit)***Checked for relevance on 04-Dec-2013***SYMPTOMSThe Gateway Server starts fine, but the Siebel Server does not.
The NameSrvr.log indicated that SADMIN user did not have proper privileges to connect to the name server.
SBL-GEN-05043: The specified user does not have the proper privileges to connect to the name server
CAUSES
ADMIN was missing the 'Siebel Administrator' responsibility, this is similar to the issue described on Doc ID 944161.1.
SOLUTION
After adding the 'Siebel Administrator' responsibility to SADMIN via Dedicated Client, the Siebel Server could be started, but the login page could not displayed.
It was found that Anonymous User was receiving the following errors in the object manager logs while the error "Server is busy error..." was returned to the browser:
ObjMgrLog Error 1 0000001a4fec5b44:0 2012-06-28 14:07:39 (odbccon.cpp (2097)) SBL-DBC-00105: An error has occurred executing a Sql statement.
Please continue or ask your systems administrator to check your application configuration if the problem persists.
DBCLog DBCLogError 1 0000001a4fec5b44:0 2012-06-28 14:07:39 SQLError: [S0002],[Microsoft][SQL Native Client][SQL Server]Invalid object name 'dbo.S_APP_VER'.
DBCLog DBCLogError 1 0000001a4fec5b44:0 2012-06-28 14:07:39 SQLError: [37000],[Microsoft][SQL Native Client][SQL Server]Statement(s) could not be prepared.
It was verified through Query Analyzer the Anonymous User had the proper rights to access the table. Changing the Anonymous User in eapps.cfg to SADMIN was helpful to have the Login Page displayed.
SADMIN could login without issues, but regular users could not login. A similar error was being written to OM logs in the transition from anonymou session to regular session type, this was preventing the regular users (non-admin) from login in to the application.
SQLError: [S0002],[Microsoft][SQL Native Client][SQL Server]Invalid object name 'dbo.S_PARTY'
It was determined this offending query could be successfully executed via Query Analyzer, but it was giving the same "Invalid object name 'dbo.S_PARTY'" error when executed through odbcsql using the user id in question:
SELECTT1.CONFLICT_ID,CONVERT (VARCHAR (10),T1.LAST_UPD, 101) + ' ' + CONVERT (VARCHAR (10),T1.LAST_UPD, 8),CONVERT (VARCHAR (10),T1.CREATED, 101) + ' ' + CONVERT (VARCHAR (10),T1.CREATED, 8),T1.LAST_UPD_BY,T1.CREATED_BY,T1.MODIFICATION_NUM,T1.ROW_ID,T5.PAR_ROW_ID,T5.NAME,T2.FST_NAME,T2.JOB_TITLE,T2.LAST_NAME,T3.LOGIN,T2.NEW_USER_RESP_NAME,T6.LOGIN,T7.NAME,T2.TIMEZONE_ID,T2.BU_ID,T3.STATUS_CD,T2.ROW_ID,T2.PAR_ROW_ID,T2.MODIFICATION_NUM,T2.CREATED_BY,T2.LAST_UPD_BY,CONVERT (VARCHAR (10),T2.CREATED, 101) + ' ' + CONVERT (VARCHAR (10),T2.CREATED, 8),CONVERT (VARCHAR (10),T2.LAST_UPD, 101) + ' ' + CONVERT (VARCHAR (10),T2.LAST_UPD, 8),T2.CONFLICT_ID,T2.PAR_ROW_ID,T3.ROW_ID,T3.PAR_ROW_ID,T3.MODIFICATION_NUM,T3.CREATED_BY,T3.LAST_UPD_BY,CONVERT (VARCHAR (10),T3.CREATED, 101) + ' ' + CONVERT (VARCHAR (10),T3.CREATED, 8),CONVERT (VARCHAR (10),T3.LAST_UPD, 101) + ' ' + CONVERT (VARCHAR (10),T3.LAST_UPD, 8),T3.CONFLICT_ID,T3.PAR_ROW_IDFROM dbo.S_PARTY T1 INNER JOIN dbo.S_CONTACT T2 ON T1.ROW_ID = T2.PAR_ROW_IDINNER JOIN dbo.S_USER T3 ON T1.ROW_ID = T3.PAR_ROW_IDLEFT OUTER JOIN dbo.S_PARTY_PER T4 ON T2.PR_DEPT_OU_ID = T4.PARTY_ID AND T2.PAR_ROW_ID = T4.PERSON_IDLEFT OUTER JOIN dbo.S_ORG_EXT T5 ON T4.PARTY_ID = T5.PAR_ROW_IDLEFT OUTER JOIN dbo.S_USER T6 ON T2.EMP_ID = T6.PAR_ROW_IDLEFT OUTER JOIN dbo.S_TIMEZONE T7 ON T2.TIMEZONE_ID = T7.ROW_IDWHERE (T3.LOGIN = 'USERABC')
Finally, there were basically two issues on the environment:
SADMIN user didn't have the "Siebel Administrator" responsibility set, this was preventing the Siebel Server startup.The ODBC DSN configured for the Siebel Server was somewhat corrupted, it was causing the following error in the object manager logs and was preventing users from login in to the applicationSQLError: [S0002],[Microsoft][SQL Native Client][SQL Server]Invalid object name 'dbo.S_PARTY'
Adding "Siebel Administrator" responsibility to SADMIN user, and recreating the ODBC DSN from scratch helped to resolve the issues.
SBL-GEN-05044 Checkpoint file was not found.
SBL-GEN-05044: Checkpoint file was not found. (Doc ID 830062.1)
APPLIES TO:
Error Message Area:Generic - GENVersion:Siebel 8.1PURPOSEThis document is intended to provide cause and corrective action information about Siebel Error Message SBL-GEN-05044: Checkpoint file was not found.SCOPEThis document is informational and intended for any user.SBL-GEN-05044: CHECKPOINT FILE WAS NOT FOUND.ExplanationThe Gateway server checkpoint file was not found.Corrective ActionPlease specify a valid Siebel gateway server checkpoint file.
SBL-GEN-05045 Rollback of name server backing file failed.
SBL-GEN-05045: Rollback of name server backing file failed. (Doc ID 830063.1)
APPLIES TO:
Error Message Area:Generic - GENVersion:Siebel 8.1PURPOSEThis document is intended to provide cause and corrective action information about Siebel Error Message SBL-GEN-05045: Rollback of name server backing file failed.SCOPEThis document is informational and intended for any user.SBL-GEN-05045: ROLLBACK OF NAME SERVER BACKING FILE FAILED.ExplanationThe rollback of the name server backing file failed. The old backing file is still in use.Corrective ActionPlease check the name server log file for details on the cause of the failure.
SBL-GEN-05046 Fatal error occurred during rollback - name server backing file may not exist or is corrupt.
SBL-GEN-05046: Fatal error occurred during rollback - name server backing file may not exist or is corrupt. (Doc ID 830064.1)
APPLIES TO:
Error Message Area:Generic - GENVersion:Siebel 8.1PURPOSEThis document is intended to provide cause and corrective action information about Siebel Error Message SBL-GEN-05046: Fatal error occurred during rollback - name server backing file may not exist or is corrupt.SCOPEThis document is informational and intended for any user.SBL-GEN-05046: FATAL ERROR OCCURRED DURING ROLLBACK - NAME SERVER BACKING FILE MAY NOT EXIST OR IS CORRUPT.ExplanationA fatal error occurred during the rollback of the name server backing file. The backing file may no longer exist or may be corrupt.Corrective ActionTry to issue another rollback command without a file argument to revert to the checkpoint file created during the failed rollback.
SBL-GEN-09001 Siebel internal error (CCF layer)
SBL-GEN-09002 Siebel internal error (CCF layer), bad arguments
SBL-GEN-09003 Siebel internal error (CCF layer), bad mode
SBL-GEN-09101 The system was unable to allocate sufficient memory for the specified operation.
SBL-GEN-09102 Server is shutting down, cleanup processing should be initiated
SBL-GEN-09103 Parameter value was never set (i.e. is null)
SBL-GEN-09201 Error initializing program context main thread
SBL-GEN-09202 Failed to load the adapter for the specified program mode
SBL-GEN-09203 Internal: unable to resolve required entry points in the CCF adapter
SBL-GEN-09204 Program Context returned existed prior the creation request
SBL-GEN-09205 Process language setting has been changed to %1
SBL-GEN-09301 Error creating the thread context
SBL-GEN-09401 Unable to load specified DLL or shared object library
Delay escript execution using sleep() function in Windows and Unix (Doc ID 541719.1)
APPLIES TO:
Siebel Tools - Version 7.0.4.10 [14072] and laterOracle Solaris on SPARC (64-bit)Product Release: V7 (Enterprise)Version: 7.0.4.10 [14072]Database: Oracle 8.1.7.0Application Server OS: Sun Solaris 8Database Server OS: HP-UX 11.0
This document was previously published as Siebel SR 38-1042896367.
SYMPTOMS
SBL-GEN-09401
How do you implement a sleep function in escript - we have a need to code a polling loop in eScript as follows:
while (true){Check conditionIf condition satisfiedbreak;
sleep for 5 seconds}
CAUSE
custom DLL required
SOLUTION
There is no eScript Sleep function or equivalent, but there are several ways for achieving the same functionality:
1. If the process is driven from Browser script (JavaScript), there is a SetTimer() function that allows repeating a process every few seconds. This could call a Business Service to do server client-side processing.
2. On Windows platforms only, it is possible to call the Windows API Sleep function directly. More information on Microsoft’s Knowledge Base (Article 231298: "HOWTO: Use SetWaitableTimer With Visual Basic")
3. Writing a dynamic linked library (DLL for Windows or so for Unix). This dynamic object can be written in any language. The VB language offers the delay function and/or timer functions, but it is only available on Windows platform. For Unix platform, the most common language is C.Solution implemented DLL on Window platform / on Unix platform:
For compiling the so file on Solaris, the customer has used the Doc ID 476274.1: Calling a shared library from eScript available on SupportWeb, but has added the following flags:-static-libgcc
Full line for the link step was:
gcc libtest.o -static-libgcc -shared -o libtest.so
Generic eScript code for using on both platforms (Windows and Unix):// Assume we are running on UNIX// If libc.so does not load (or any exception), we are running // on NT and make the WIN32 call// Sleep for 2 secondstry{ SElib.dynamicLink("libc.so", "sleep", 2)}catch(e){ SElib.dynamicLink("kernel32.dll", "Sleep", STDCALL, 2000)}
SBL-GEN-09402 Unable to load specified entry point for DLL or shared object librarySBL-GEN-09501 Unable to set parameter %1 to value "%2" for the component.
SBL-GEN-09501: Could not set subsystem parameter %1 to value "%2" (Doc ID 478496.1)
APPLIES TO:Error Message Area:Generic - GENVersion:Siebel 7.5.3PURPOSEThis document is intended to provide cause and corrective action information about Siebel Error Message SBL-GEN-09501: Could not set subsystem parameter %1 to value "%2"SCOPEThis document is informational and intended for any user.SBL-GEN-09501: COULD NOT SET SUBSYSTEM PARAMETER %1 TO VALUE "%2"ExplanationThe specified parameter does not exist for this component.Corrective ActionCheck the input arguments for the request and make sure the correct parameter name is being passed to the component.
SBL-GEN-09501: Unable to set parameter %1 to value "%2" for the component. (Doc ID 478828.1)
APPLIES TO:
Error Message Area:Generic - GENVersion:Siebel 7.8PURPOSEThis document is intended to provide cause and corrective action information about Siebel Error Message SBL-GEN-09501: Unable to set parameter %1 to value "%2" for the component.SCOPEThis document is informational and intended for any user.SBL-GEN-09501: UNABLE TO SET PARAMETER %1 TO VALUE "%2" FOR THE COMPONENT.ExplanationThe specified parameter does not exist for this component.Corrective ActionCheck the input arguments for the request and make sure the correct parameter name is being passed to the component.
Error SBL-GEN-09501 when invoking method 'ReloadServiceRegion' on business service 'Appointment Booking Service' in workflow process (Doc ID 565586.1)
APPLIES TO:
Siebel Scheduling - Version: 7.8.2 [19213] - Release: V7Information in this document applies to any platform.
SYMPTOMS
When invoking method 'ReloadServiceRegion' on business service 'Appointment Booking Service' in a workflow process step the following error is generated: GenericLog GenericWarn 2 0 2008-04-21 15:08:13 (ccfsvc.cpp (172) err=9501 sys=0) SBL-GEN-09501: Unable to set parameter SvcRegnId to value "1-11SCM" for the component.
CAUSE
The ReloadServiceRegion method in business service "Appointment Booking Engine" can only be invoked from the Siebel Server component "Appointment Booking Engine". This means that the workflow process step must invoke method 'SubmitRequest' on business service 'Server Requests' to generate a component request for the Siebel Server component "Appointment Booking Engine" in order to execute this method.
SOLUTION
The following MetaLink3 document explains in detail how to set up a workflow process that will generate the required component request: How to load and reload ABS automatically in the background without using the UI Load ABS button? Note 487455.1
The following section in the documentation explains the complete set of arguments that must be defined in Siebel version 7.8.2.x: Bookshelf v7.8: Reloading the Appointment Booking System Cache Using Workflows Siebel Field Service Guide v7.8 > Setting Up and Using Scheduling > Reloading the ABS and Optimizer Caches > Reloading the Appointment Booking System Cache Using Workflows
Note however that the syntax for the first input argument is not correct. It should read: | Appt.SvcRegnId | Literal | The required service region's ROW_ID |
The following Change Request has been created to have this documentation corrected in a future version of Siebel Bookshelf: Documentation Defect CR 10541116 - Incorrect documentation of parameter SvcRegnId in workflow step for ReloadServiceRegion.
For more information about configuring workflow process steps to start server components and about business service "Server Requests" you can also refer to the following sections in the documentation:
Siebel Business Process Designer Administration Guide > For Developers: Workflow Process Steps > About Business Service Steps Business services allow you to execute predefined or custom actions in a workflow process. Some examples of predefined business services include: : * Server tasks. You can run a server component task using the Asynchronous or Synchronous Server Requests business service.
Siebel Business Process Designer Administration Guide > Reference Materials for Siebel Workflow > Predefined Business Services > Server Requests Business Service
SBL-GEN-09502 Could not find parameter %2 for subsystem %1
SBL-GEN-09601 Unable to create named pipe.
SBL-GEN-09602 Unable to accept connections on named pipe.
SBL-GEN-09603 Unable to connect to named pipe.
Unable To Extract Local 8.x Database: Error SBL-GEN-09603: "Unable to connect to named pipe" (Doc ID 832813.1)
APPLIES TO:
Siebel Remote - Version 8.0.0.6 SIA [20423] to 8.1 [21039] [Release V8]Information in this document applies to any platform.***Checked for relevance on 30-Aug-2012*** SYMPTOMSWe are trying to run the Database Extract for our developers. It worked for two users but is not working for other users. It looks like it uses a lot of I/O on the DB server and finally crashed.
The following error messages are found:
GenericLog GenericError 1 000000054a0405f4:0 2009-05-08 14:35 :32 (scfmsgfac.cpp (805) err=9603 sys=0) SBL-GEN-09603: Unable to connect to named pipe.
ScfMsgFacLog SCFMsgFacError 1 000000054a0405f4:0 2009-05-08 14:35 :32 SBL-GEN-09603: Unable to connect to named pipe.
CAUSE
The cause of this issue is due to problems with database server
SOLUTION
The following are the steps to fix the issue:1. Run the Db statistics to keep the stats up-to-date. 2. Remove “dicdata.dat” from the Siebel server 3. Start the application and login as ‘SADMIN’ user 4. Run new database (GenNewDB) 5. Perform the extract for the developers
SBL-GEN-09604 Unable to read from named pipe.
SBL-GEN-09605 Unable to write to named pipe.
Meaning and Significance of the SBL-GEN-09605 Error Message (Doc ID 1315520.1)
APPLIES TO:
Siebel System Software - Version: 8.0.0.9 SIA[20433] and later [Release: V8 and later ]Information in this document applies to any platform.
GOAL
What is the meaning and significance of the below error message :- SBL-GEN-09605: Unable to write to named pipe.
SOLUTION
Usually this error will occur when the Process at the other end of the named pipe has died.As a corrective Action need to restart the offending component.
For example in a typical scenario where SSSE component is calling the FSMSrvr component and subsequently failed and the FSMSrvr component could no longer communicate with it's process. In these kind of scenarios the below message will be logged in FSMSrvr logs
SBL-GEN-09606 Unable to set timeout on named pipe.
SBL-GEN-09607 Unable to send socket on named pipe.
SBL-GEN-09608 Unable to receive socket from named pipe.
SBL-GEN-09609 I/O operation timed out on named pipe.
SBL-GEN-09610 Unable to shut down named pipe.
SBL-GEN-09611 Unable to close connection on named pipe.
SBL-GEN-09612 Unable to initialize named pipe.
| 
