SBL-DBC-00111: An error has occurred writing to a record. 

Please continue or ask your systems administrator to check your application configuration if the problem persists.

Explanation for Siebel SBL-DBC-00111

This error message can occur when a SQL statement, usually the UPDATE, INSERT, or DELETE statement, was not executed successfully against the database server. In order to troubleshoot the error and get to the root of the behavior, it is important to review the SQL statement that is causing the error. Below are the different ways to capture the SQL statement:

1. Start by spooling the SQL, using the /s option, to determine if the error is reproducible in the dedicated client or mobile client. This spools all the SQL being generated by the application client to a log file and allows the SQL statement causing the error to be identified and reviewed. See Technical Note 91 for more information.

2. If the error is reproducible only in the Siebel web client, you will need to raise the log levels for the different events. For example, ObjMgrSqlLog for the Application Object Manager to capture the SQL statements. See FAQ 2116 for more information.

3. Refer to FAQ 1322 for more information about setting up client side logging.

This error message can be encountered for a variety of different reasons ranging from errors in the configuration of a business component to permissions on a table at the database level.

Below are some common causes:

1. It may be related to a database specific defect. The database may not contain the latest patchset.

2. If you are using DB2 for your server database, check if the following error is generated after the SBL-DBC-00111 error in the log file created with tracing set on the client:

[IBM][CLI Driver][DB2/SUN] SQL0101N The statement is too long or too complex.

This error may occur when you create a new record and undo the record. This SQL0101N error is a DB2 specific error with the length of the SQL query. Although the sql is generated by the Siebel application, the limitation is coming from the DB2 database.

3. This error arises when there is discrepancy between the logical schema in the Siebel repository and physical schema in the actual database. There may be a difference in the field type and length at the business component field definition versus the table column definition.

4. A common cause is when deep copying a business component with Multi-Value Links (MVL) having No Copy set to False.

5. When you right-click and select Columns Displayed in the Quotes > Attachments view for a newly created attachment without entering any information for the new attachment, this error will appear instead of the error, “Name is a required field”.

6. When merging Account records from Site Map > Administration > Data Quality > Duplicate Account applet, this error may occur. The cause is if the source field of a join is a system field.

7. The database column length may not be sufficient to store a value of the field or the field value’s text length exceeds the supported database column length. The length of the Name field on a Dynamic Hierarchy is 30 and the GenerateHierarchy method defaults the User Id + time stamp into the Name field. The time stamp, including any spaces is 22, thus the user Id is not supposed to be longer than 8 characters. If you are updating a column of type DTYPE_CURRENCY with more than 22 digits, this may also occur.

Corrective Action

1. If you are encountering the “ORA-01843: not a valid month” error following this error message, this is an Oracle database defect 3138618, which has been fixed in the patchset 9.2.0.6.

If you are encountering the “ORA-02248: invalid option for ALTER SESSION” error following this error message, an option was used with ALTER SESSION that was not supported by the version of database used.

2. If the SQL0101N error occurs using the vanilla srf and only when connected to your server database, check if triggers are active in your server database. If triggers are active in your server database, more memory is needed by DB2 to process the statement because the trigger is effectively executed with the statement.

Ensure that the STMTHEAP is set to the value recommended by Siebel Bookshelf > Siebel Server Installation Guide for UNIX > Creating the DB2 Universal Database for Windows and UNIX > DB2 Database Configuration Guidelines. The suggested setting is at least 8192. You may need to continue increasing the STMTHEAP size up to 40960 to accommodate having triggers active in the server database.

3. This has occurred if the SQL statement refers to custom tables or custom extension columns which do not exist on the database the user is connecting to. To correct this:
a. Ensure that the user is connecting to the correct database
b. Ensure that schema changes have been applied to the database.

If there is a difference in the field type and length at the business component field definition versus the table column definition, refer to Technical Note 345.

4. Keep the No Copy property of the MVL to TRUE.

Read More »

Records not getting removed in S_ESCL_REQ.

The workmon is processing the record very slowly.

Cause : The performance may be the result of the inavailability of wfprocmgr/srbroker component. Need further investigation.

The facts is gathered from the workmon (Workflow Monitor) logs.

Solution

One suggestion to improve the processing time is to run the workflow process asynchronously. By doing this, it will cut short the processing time significantly.

The steps to achieve this are as follows :
- Based on the workflow policy action, determine the workflow program. The standard program is Run Workflow Process
- Launch the siebel tool, goto Workflow Policy Program : Run Workflow Process. Change the Submit Type to Async.
- No compilation is required but the change needs to be check into the server database.

Meanwhile, consider increasing the log level of wfprocmgr component as follows :
taskconfig = 4
prcexec = 4
stpexec = 4
enginv = 4

In this way, you could track any erroneous record from wfprocmgr component.

Read More »

The server you are accessing is either busy or experiencing difficulties. 

Please close the web browser, start a new one and try logging in again.This error message could occur when there are problems connecting to Resonate or the Web Server.

Cause
1. Web Server not responding, Siebel Server not running, or the eapps.cfg file has incorrect parameters.
2. No Responsibility associated with the Anonymous User as documented in the Authentication and Access Control Guide (7.0.3) or Security Guide for Siebel eBusiness Applications (7.0.4 and 7.5.x) on the Siebel Bookshelf.
3. In UNIX, user access permissions to the SWEApp folders must be set as indicated in the Siebel Installation Guide.
4. The ODBC data source may have incorrect values or drivers not inherited from the Siebel Server installation
5. The Anonymous User User ID posted in the eapps.cfg file was not valid in the corresponding database.
6. In the UNIX environment, users need to ensure that the latest Siebel certified runtime libraries and patches have been applied.

Diagnostic Steps

1. Review ”FAQ 1773: What are the steps to troubleshoot the error message: ’The server you are accessing is either busy or experiencing difficultiees’ ” in a Siebel 7 Web client user browser?
2. Gather _.log and SWEAPP logs for review.
3. Check the validity of the AnonUser ID posted in the eapp*.cfg files.
4. If using Resonate, verify that the environment parameters HTTP_INACTIVE_CONN_TIMEOUT, SERVER_INACTIVE_CONN_TIMEOUT and RES_PERSIST_BLOCK_SIZE are set according to the Siebel Server Installation Guide on the Siebel Bookshelf.

Solution

1. Implement all of the steps indicated in ”FAQ 1773: What are the steps to troubleshoot the error message: ’The server you are accessing is either busy or experiencing difficulties……’ in a Siebel 7 Web client user browser?”
2. In Windows, give ”Everyone” permission to the SWEApps (Siebel Web server extension). On the SWEApps directory, right click and go to Properties. Navigate to the Security Tab and check if the permission is for ”Everyone”.
3. In UNIX, change the files permission of eApps/public directory using command ’chmod –R 777’.
Login failed for Login name: sadmin

Symptom or Error Message

”Login failed for Login name : SADMIN ”

”Login failed attempting to connect to”

This error usually accompanies the error: ”The server you are accessing is either busy or experiencing difficulties. Please close the web browser, start a new one and try logging in again. 

For further support, please copy and send the full message text to your system administrator.”

Cause
There was no responsibility associated with the Anonymous User as documented in the Authentication and Access Control Guide (7.0.3) or Security Guide for Siebel eBusiness Applications (7.0.4 and 7.5.x) on the Siebel Bookshelf.

Diagnostic Steps
Review the SWEApps log files.

Solution

Add a responsibility to the Anonymous User in the Application Administration screen of Siebel Client.
Your session timed out because you were idle for too long

Symptom or Error Message

”Your session timed out because you were idle for too long. Please log in again to resume.” or Web browser hanging.

Cause
1. In a Resonate environment, two environment variables HTTP_INACTIVE_CONN_TIMEOUT and SERVER_INACTIVE_CONN_TIMEOUT on each node need to be configured.2. Could be related to URL that is saved in the ’Favorites’ menu option of IE with a ’GetCachedFrame’ parameter.”
3. Firewalls deployed in the environment can also cause this error message on the Web Client user interface.

Diagnostic Steps

1. The normal occurrence is just a normal timeout. Verify whether the browser has been idle for too long.
2. In a Resonate environment, the user will need to configure the following two environment variables: HTTP_INACTIVE_CONN_TIMEOUT and SERVER_INACTIVE_CONN_TIMEOUT on each node. Ensure that the following environment variables are set. These should be set on all servers with Central Dispatch installed. These are not set by the installers.
o HTTP_INACTIVE_CONN_TIMEOUT=31536000
This controls individual TCP connections for a server
o SERVER_INACTIVE_CONN_TIMEOUT=31536000
This controls individual TCP connections for HTTP and Cookie Persistence services for a scheduler.

Solution
If applicable, users may need to delete the ’GetCachedframe’ parameter in the URL. A session cookie is created for each browser process, not window.
An error has occurred creating business component ’Enterprise Component Group’ used by business object ’Server Admin’

Symptom or Error Message

An error has occurred creating business component ’Enterprise Component Group’ used by business object ’Server Admin’. Please ask your systems administrator to check your application configuration.

Cause
1. Usually due to a Siebel Gateway Server or Siebel Server offline or unavailable when connecting via Dedicated Web Client, Browser or a network connectivity error.
2. Siebel Server or ConnectString incorrectly specified in the .cfg file.

Diagnostic Steps

1. Check the connectivity to the VIP Gateway port via: telnet 2320
2. Review the siebns.dat to verify the correct cluster virtual IP address are specified in both of the following locations:
o Enterprise Level -> Named SubSystems > GatewayDataSrc -> DSConnectString
o SrvrdataSrc-> Parameters > DSGateway Address
3. Check the eapps.cfg or associated *.cfg file.

Solution
1. A rebooting of all Enterprise Servers may clear this error.
2. Make sure to execute the Synchronize button in the Batch Component Admin screens in the Server Admin screen and re-start the Siebel Server Service.
3. List and double-check the configuration file parameters.

Read More »

Siebel Gateway Server is not running" during server configuration even though the Siebel gateway is started"

Installing the Siebel Enterprise Server (app server) 7.7.x on AIX 5L in console mode per 'Installation Guide for Unix - Rev. B' documentation: The installation has completed successfully, however when I run the configuration wizard the installer is unable to connect to the Gateway Server with the following error:

• Please enter the address of the Siebel Gateway Server. [gtwy] gtwy
• Please enter the port of the Siebel Gateway Server. [2320] 2320
• Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1] 1

Please read the information below.

Siebel Gateway Server is not running. If you want to continue, you need to start it now. Click "Back" to change the Gateway Port number or click "Next"after starting the Gateway Server.

Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1]

The gateway and enterprise servers are co- located in this instance.

I have verified the Siebel gateway is up and running; I am able to install a new enterprise server on another pre-existing machine (running Win2K) and successfully register it with the gateway on the new machine (running AIX).

Solution
For the benefit of other readers:

The customer was configuring the Siebel Server via the Console Mode configuration as a Siebel user with ‘root-like’ permissions with the command:

Server/Siebel_Enterprise_Server/siebsrvrcfg/setupaix -is:javaconsole -console -args StringTable=/siebel7/sia77/_uninst/ses/table.txt

The configuration script could not recognize the Siebel Gateway Server was running despite other Siebel Enterprises being able to connect to the Gateway specified. However, when the customer was logged on as root, the Siebel Console Server Configuration Wizard was able to connect to the Siebel Gateway Server. The configuration proceeded as root and ownership of all files modified were changed from root back to the Siebel user

Customers experiencing the same situation should review the permissions of the user performing the installation. The Siebel Installation Guide for UNIX states it is not recommended to install Siebel products as root.

Read More »

The page cannot be displayed Siebel.

Symptom or Error Message
The page cannot be displayed. Cannot find server or DNS Error Internet Explorer

Cause
1. Web server was running on an unsupported platform.
2. Microsoft Data Access Components (MDAC) and/or Microsoft Foundation Classes (MFC) not installed or incorrect version installed.
3. With introduction of MR 7.0.4.210, the new extension .swef is used and this extension was not added to the Application Mapping contained in the properties of the virtual directory during installation. This is only valid for virtual directories belonging to the Siebel Industry Product Line; others are configured correctly during installation.
4. When Windows 2000 resolves a name using DNS, it does not necessarily pick the first one in the list. If an external DNS server has been selected for name resolution, the error message appears.

Diagnostic Steps
1. Ensure the operating system is listed in the System Requirements and Supported Platforms guide.
2. Check the SESsetup.log log file in the dedicated client directory to ensure that the DLLs have all been registered successfully.
3. Check if the .swef extension is missing from the application Object Manager virtual directory properties in the Internet Services Manager.

Solution
1. Install the Web Server on a supported operating system.
2. If registration resulted in errors, install the following:

• Microsoft Data Access Components (MDAC)
• Microsoft Foundation Classes (MFC)

These components can be found under the ”ThirdParty\MDAC” and ”ThirdParty\MFC” directories of the Siebel Client installation CD. Afterwards, register the DLLs that failed or re-install Siebel Client.
3. Add the missing mapping by editing the properties of the relevant Object Manager’s virtual directory in the Internet Services Manager. Add a line containing the .swef extension with the same mapping as the .swe extension. Restart the Web server.
4. Disable any DNS Server not being used by the Siebel Applications on the Client machine as a temporary workaround. For information on the Microsoft fix for this behavior, review the Microsoft Knowledge Base Q286834, ”The DNS Client Service Does Not Revert to Using the First Server in the List”. Microsoft suggests permanently re-configuring the DNS Servers and clients.
5. Carry out the following steps:

• Uninstall Siebel Web Server Extension (SWSE).
• Back up and clean the registry, then reboot.
• Install the supported Microsoft Service Pack and reboot.
• Verify that IIS is running and working, then install the relevant updates.
• Reinstall Siebel Web Server Extensions (SWSE).

Can’t load sscdo80.dll or Can’t load sscdo90.dll

Symptom or Error Message
Can’t load sscdo80.dll or
Can’t load sscdo90.dll


Cause
1. Oracle Client installation was corrupted.
2. Incorrect version of Oracle client installed.


Diagnostic Steps
1. Check the version of the Oracle Client installed in the Siebel Dedicated Client machine.
2. Check the version of the Oracle Client installed in the Siebel Server machine.
3. From the client machine, connect to the database server using SQL*Plus and run both a tnsping and a ping.
4. Ensure the tnsnames.ora file has the correct ConnectString.
5. Ensure the Oracle Client installation directory is in the Windows PATH environment variable and that the ORACLE_HOME environment variable is set correctly.


Solution
Install the correct Oracle Client version (refer to Siebel Systems Requirements and Supported Platforms guide).
Unable to start the web browser for your session


Symptom or Error Message

Unable to start the web browser for your session.

Cause
1. Faulty installation of the Dedicated or Mobile Web Clients
2. Incorrect Internet Explorer settings


Diagnostic Steps
Not Applicable

Solution
Uninstall and re-Install the Client.
1. Return browser settings back to the default settings.
2. Re-install operating system or re-image machine.


Failed to install MDAC
Symptom or Error Message

Failed to install MDAC.

Cause
This error message is usually caused by either the presence of the wrong version of MDAC or the presence of software using a conflicting version of MDAC.


Diagnostic Steps
Confirm the installed version of MDAC and ensure that it matches the version listed in the Siebel System Requirements and Supported Platforms guide.


Solution
1. Reinstall the Siebel-supplied version of MDAC.
2. Back-up and delete the SQLSRV32.DLL file in the C:\WINNT\System32 directory. Re-run the Siebel installation. The installer should detect that no MDAC components are installed on the machine and successfully install MDAC.
3. If other solutions fail, re-image the system with the required MDAC version and updated system files.


Exited with error 5004
Symptom or Error Message

Completed Siebel Enterprise Configuration. Exited with error 5004.

Cause
1. Error message usually produced during the installation on AIX because of incorrect permissions on the installation files.
2. Missing required AIX runtime libraries (X11.base.common and X11.base.lib).


Diagnostic Steps
1. Ensure that the permissions on the ”siebctl” file are at least ’rwx r-x —’ (750).
2. Confirm that file ””libXext.a”” exists on the server. This file is part of the fileset X11.base.lib and physically resides in /usr/lpp/X11/lib/R6/ with a symbolic link in /usr/lib. Ensure the file ”libXext.a” is in the correct directories with permissions set to ’rw- r– r–’ (644).


Solution
1. Set the correct permissions on the siebctl file. Prior to setting the server configuration during the install_server process, open a new shell and set the permissions on /bin/siebctl to ’rwx r-x r-x’ (755), then continue with the server configuration. Do not set the sticky bit.
Change Request # 12-4K12M7 addresses the problem with the sticky bit set.
2. Install the AIX runtime libraries (X11.base.common and X11.base.lib.
3. Use the Server Configuration Utility to reconfigure the Siebel server
4. Change following parameter :
setenv LDR_CNTRL=LOADPUBLIC@MAXDATA=0×60000000
Refer to Alert 471 on SupportWeb for more information.


Object expected
Symptom or Error Message
… Object Expected …


Cause
1. Mixed maintenance release versions on components
2. Incorrect permissions on the /home/siebel/SWSE/public directory, often for the Web server Administrator (IWAM__)
3. Missing JavaScript (.js) files from the \SWEApp\PUBLIC\SCRIPTS directory


Diagnostic Steps
1. Verify the maintenance release versions of each Siebel component in the enu.txt file in the root directory e.g. Siebel Server: \siebesrvr\enu.txt.
2. Refer to ”Alert 388: Additional permissions required with Siebel Web Server Extensions on Siebel 7 eBusiness applications”.


Solution
1. Install the same maintenance release version on each component.
2. Copy the JavaScript (.js) files in the \SWEApp\PUBLIC\SCRIPTS folder from another similar environment. Stop and re-start the Siebel Gateway, Server and Web Server Services.


HTTP 500 – Internal Server error
Symptom or Error Message 

HTTP 500 – Internal Server error.

Cause1. Incorrect permissions on the /home/siebel/SWSE/public directory, often for the Web server Administrator (IWAM__)
2. Cannot find the eapps.cfg file.


Diagnostic Steps and Solution
Refer to ”Alert 388 on SupportWeb: ’Additional permissions required with Siebel Web Server Extensions on Siebel 7 eBusiness applications’ ”.

Read More »

Using odbcsql utility, ODBC connection fails with "Segmentation fault".

During a fresh install of a Siebel CRM environment on Linux OS, while running the Siebel Database Configuration Wizard for Siebel database installation, the screen disappears after entering Database user name and password (SADMIN/SADMIN).

Cause

ORACLE_HOME environment variable is not set to full pathname of the Oracle system home directory.

Solution
Trace odbcsql utility with "strace" Linux to see which libraries are loaded.
$ strace –fo

odbcsql

In the generated trace file last "open" command is:

open("./oracore/zoneinfo/timezlrg.dat", O_RDONLY) = -1 ENOENT (No such file or directory)--- SIGSEGV (Segmentation fault) @ 0 (0) ---The correct location for timezlrg.dat file is: “$ORACLE_HOME/oracore/zoneinfo/”

To set ORACLE_HOME variable use the following commands depending on the Unix shell you are using:

sh:
$ ORACLE_HOME=; export ORACLE_HOME
csh:
$ setenv ORACLE_HOME
bash/ksh:
$ export ORACLE_HOME=

Make sure the values are set:

$ env | grep ORACLE_HOME

Read More »

Siebel CRM gateway server installation incomplete.

TEMP and TMP Windows environment variables are not set correctly.

SBL-ICF-00003

Customer was installing the Siebel gateway server and found out that the installer is not copying all the required program files into the gtwsrvr installation directory.

For instance, the ENU (English-US) language pack is being installed during the initial set-up. However, neither the [gateway]/bin or [gateway]/bin/enu folders contain the expected enu.txt file. Customer was also missing several files from the gateway\locale directory and encountered errors of the type:

“NSC - ErrCode 5009 SysErr 0”

.. in the sw_cfg_util.log or sw_cfg_util(001).log files.

Solution

For the benefit of other readers:
Upon investigation it could be determined that the root cause for the missing files was the Temp environment variable set at Microsoft Windows OS level, for instance:

D:\\Server\windows_server_ses_base\ses\enu\setup.exe -is:javahome C:\DOCUME~1\SADMIN\Local Settings\Temp\LRE7.tmp -is:tempdir C:\DOCUME~1\SADMIN\Local Settings\Temp -args SS_SETUP_INI=C:\DOCUME~1\SADMIN\Local Settings\Temp\enu\siebel.ini StringTable=H:\Siebel\sea752\_uninst\table.txt

From the above example, "Document and Settings" was replaced by "DOCUME~1". But "Local Settings" was not.

In order to fix this, please navigate to Control Panel > System > Advanced > Environment Variables, under User variables for xxx, change

TEMP to c:\temp
TMP to c:\temp

Next log in to Command Prompt, issue set and confirm that the above two environment variables have been set correctly in preparation of the Siebel CRM software installation process.


Check All Siebel Administration Tutorials

Read More »

Siebel Workflow Records Stuck in S_ESCL_REQ.

Goal
Records are not picked up from the S_ESCL_REQ table after the policy violations. Customer has defined a Workflow Policy Program with custom SQL as a policy action.

Solution
When Workflow Policy Programs are defined as actions for any Workflow Policies, care must be taken to make sure any custom SQL added in the Policy Programs have all the column lengths with-in acceptable range, typically 30 characters (depends on the ODBC connection as well), and if it exceeds that, customers need to put aliases in place for those columns. Ignoring that would to a situation where all violated policies remain in the E_ESCL_REQ table.

Typical error noticed in the Workflow Monitor Agent log files when this issue happens:
ProcReq GenericFatal 0 000000024d7e0948:0 2011-03-14 23:50:24 Column Name Length exceeded max limit in OutputBindColumns

GenericLog GenericError 1 000000024d7e0948:0 2011-03-14 23:50:24 Message: ESCL-19,
Additional Message: Column Name Length exceeded max limit

Making sure that all columns in the custom SQL are of appropriate length will resolve this issue and the records will be picked up properly from the S_ESCL_REQ table.

Read More »

Tutorial about TraceOn, Trace, and TraceOff in Siebel.

The methods of TraceOn, Trace, and TraceOff are often useful for developers to troubleshoot and track a script during run time. These methods, however, should be used judiciously.

Summary

Developers should note the following key items when using the TraceOn, Trace, and TraceOff methods.

1. Always use TraceOff with TraceOn in Siebel

TraceOn will activate the tracing for the behavior of the application according to the parameters specified in the TraceOn method. However, the tracing will not be automatically turned off when the script completes or aborts. The trace will continuously log the SQL, allocation information, or both until the application is shut down. This will make the analysis of the log file more difficult due to the amount of unrelated information that may be included. Refer to the example in Siebel Visual Basic (VB) code below:

Sub … TheApplication.TraceOn ”C:\trace.txt”, ”SQL”, ”” … if … then TheApplication.TraceOff exit sub end if … TheApplication.TraceOff End Sub

The above code demonstrates that once a TraceOn is issued in a procedure, TraceOff must be called before every exit of this procedure.

2. Isolate the issue

If the issue is known to be happening in specific lines of code of, it is a good practice to use TraceOn and TraceOff around the specific issue point. This allows the information gathered in trace file to be focused on the issue and reduces the amount of unrelated information in the trace file.
For example, if it is known that a script’s query cannot find the desired record, the requirement is to analyze the SQL that is generated in the script. The focus should be on the script that sends the query. In Siebel VB, this may appear as:

TheApplication.TraceOn ”C:\trace.txt”, ”SQL”, ”” oBC.ExecuteQuery TheApplication.TraceOff

Here TraceOn and Traceoff log only for the one suspect line “oBC.ExecuteQuery”.
Thus only the SQL that is generated in this script will be recorded, streamlining the analysis.

3. The trace file is overwritten in each round of testing

If the FileName parameter specified in the TraceOn method is not found on the specific drive, a new file is created. However, if the file already exists then the TraceOn method will overwrite the existing one. Therefore, if the result of a previous test needs to be referenced later, rename the trace file to avoid it being overwritten.

4. Important: The trace file is generated in different locations

The trace file is generated in different locations depending on which script interface is used. The general rule is that for interfaces that do not rely on the Siebel Server, the trace file is generated in the local machine. For interfaces that have to connect to Siebel Server, the trace file is generated on the Siebel Server machine.
 
a. The Interfaces that generate a trace on the local machine

• Server Script when using Dedicated Client or Mobile Web Client
• COM Data Server
• COM Data Control in Local mode
• Mobile or Dedicated Web Client Automation Server

b. The Interfaces that generate a trace on the Server machine

• Server Script when using Web Client or Standard Interactive Client
• COM Data Control in Server mode
• Siebel Java Data Bean
• Siebel CORBA Object Manager

Read More »

GEN-05009: Unable to connect to gateway server

Symptom or Error Message

SBL-GEN-05009: Unable to connect to gateway server

Cause
1. Refer to item 1 in this section as the same causes apply.
2. Siebel Server incorrectly specified in the .cfg file or the incorrectly set ConnectString in the .cfg file.

Diagnostic Steps
1. Check that the Gateway is online and running.
2. Check whether the Web Server can ping the Siebel Gateway.
3. Review ”FAQ 1773: What are the steps to troubleshoot the error message: ’The server you are accessing is either busy or experiencing difficulties……’ in a Siebel 7 Web client user browser?”

Solution
Accurately post the correct Siebel Server parameters, etc. in the .cfg files.

Display Help
Symptom or Error Message
Display Help for clicked on buttons, menus and windows Help. The error occurs when trying to launch the Call Center Icon.

Cause
Applicable when running a new instance of Microsoft Internet Explorer.

Diagnostic Steps
1. Check Microsoft operating system Service Pack levels.
2. Check Microsoft Critical Updates and Security Updates.
3. Check custom level security settings.
4. Check system requirements and versions of Microsoft Virtual Machine, ActiveX Controls and Plug-Ins.
Make sure the Internet browser complies with the system requirements documented in the System Requirements and Supported Platforms document found on SupportWeb.

Solution
Resolve by restoring the original settings for IE in Tools > Internet Options > Advanced Tab and click on the Restore Defaults button.
The Siebel Server [xxx] service terminated with service-specific error

Symptom or Error Message

In the Windows NT Event Viewer, the error message is displayed: ” The Siebel Server [xxx] service terminated with service-specific error.”

Cause
1. Installing a new NIC may cause IP configuration mismatch or incorrect binding orders.
2. Resonate is not installed properly on the node. Install all Resonate components as documented in Siebel Bookshelf. Missing CDAction.exe can cause this behavior.

Diagnostic Steps
1. Use ODBCSQL to check database connectivity. Re-install MDAC.
2. Check User Rights: ’Log on as a Service’ and ’Act as Part of Operating System’ must be set. The Siebel Server installation guide explains this in detail.

Solution
See above.
The type of user agent is not found

Symptom or Error Message

”The type of user agent is not found”. This error may occur on the Mobile Web Client or from the browser via the Web Server after typing in the User Name and Password.

Cause
1. Most likely the invalid entry of License Keys; the base key was not installed first.
2. Correct login missing from S_USER table.
3. Compiling a java script or running genbscript with invalid code
4. Compilation of a custom .srf file

Diagnostic Steps
1. Check the Configuration Context from Tools. From the ”Target Browser Config”, ensure the supported version of IE is selected and that there is a value for User-Agent set in the capability names section.
2. Check that all license keys are inserted and working properly.
3. Check whether the user is logging into the Local, Sample or Server data source; using the standard SRF or customized; and using Call Center or CTI.

Solution
In most of cases, clearing Internet Explorer cache on the Mobile Client and ensuring enough free disk space will resolve the behavior.

54008 Error on DB2
Symptom or Error Message
54008:[IBM][CLI Driver][DB2/6000] SQL20075 The index or index extension ”S_DD_HIERATRVAL_M2” cannot be created or altered because the length of ”PCODE” is more than 255 bytes.

Cause
DB2 parameters and sizing are not set correctly for index length and table space

Diagnostic Steps
1. Verify that the Db2set environment parameter DB2_INDEX_2BYTEVARLEN (also known as a DB2 Registry variable) has been set to ’ON’.
2. Ensure proper table space sizing before running a new installation.
3. Check the ddl_ctl.log and dataimp.log files for errors regarding space problems.

Solution
1. Review the proper sizing parameters.
2. Make sure that the database version complies with system requirements documented in the System Requirements and Supported Platforms document.
[SWSE] Login failed. SVR-03005: No server connect string for Siebel Component

Symptom or Error Message

[SWSE] Login failed. SBL-SVR-03005: No server connect string for Siebel Component %3 in Siebel Enterprise %1, Siebel Server %2

Cause
1. Usually occurs on the Client browser when logging into application and caused by an Object Manager component not being ”enabled”. This occurs most frequently with the eService ObjMgr which should be automatically enabled when launching the Call Center ObjMgr.
2. In a UNIX environment, incorrect file permissions could disable communications between the Web and Siebel Servers.

Diagnostic Steps
1. Review the SWEApp log files generated from the Web Server: the Gateway Name Server may not be enabled or may not have the proper parameters for the Siebel Server, Object Manager.
2. As a post-installation step, make sure to execute the ”Synchronization” button in the Batch Component Admin Screen.
3. Run the srvrmgr utility to see if all server components are running properly.

Solution
1. Make sure the Siebel Server components are enabled.
2. Make sure the Web Server has proper file permissions in a UNIX environment.

REPIMEXP-ERR-1124
Symptom or Error Message

REPIMEXP-ERR-1124: Unable to import table \”%s\” (%s).A common server error that occurs when using dev2prod.

Cause
1. Due to some Data Model changes in column names, table names, etc. from version 6.x to v7.x, new data imports may fail.
2. Running a Full Get for a local database could cause similar errors.
3. In UNIX, limits to memory allocation segment space may cause the upgrade or install to fail and generate similar errors.

Diagnostic Steps
1. Check the log files generated by the dev2prod process.
2. Check the dataimp logs for a new database installation or the upgrep logs generated during an upgrade.
3. The REPIMEXP-ERR-1124 error is usually posted in conjunction with ”Invalid Column or Table name” errors.

Solution
Review log files to identify the columns or tables in question and make corrections to sizing and length. Follow System Requirements and Supported Platforms Guide.

Read More »

Siebel server not starting after SADMIN password change.

After installing Siebel version 8.1.1. successfully on Red Hat Linux Advanced Server 4.0 running against an Oracle 10g server database, changes to the Siebel Administrator account password for SADMIN caused the Siebel server startup to fail.

Cause
The Siebel Server service definition also defines the SADMIN password and therefore must be changed accordingly.

Solution
Run the SIEBCTL utility to generate a new Siebel Server service definition file (.SVC) and apply the new SADMIN password into the SVC
1. Shutdown the Siebel server

2. Use Siebel Server Manager to change the SADMIN password at the enterprise level:

srvrmgr-> enterprise param Password=

3. Change the password in the database.

4. Change the password in the Siebel Service definition file (SVC) under ./siebsrvr/sys
* Backup the SVC file with the format svc.siebsrvr.siebel:
* Run the following command to recreate the SVC file with the new Siebel administrator password:
linux> siebctl -r ''$Siebsrvr'' -S siebsrvr -i enterprisename:siebsrvrname -a -g "-g GTW_HOST:gtwyport -e enterprisename -s siebsrvrname -u sadmin" -e newpassword -L ENU where:
''$Siebsrvr'' = the installation directory of the Siebel Server
siebsrvrname = the name of the Siebel Server
gtwyport = the port number of the Gateway Name Server
enterprisename = the name of your Siebel Enterprise
newpassword = the new Siebel administrator password (in plaintext). The siebctl utility encrypts the password.

5. Stop and restart the Siebel Gateway Name Server followed by the Siebel Server(s)

6. Connect to the Siebel Server Manager and verify the password change was successful

Read More »

How to delete a Siebel Server or Enterprise from the Gateway.

Solution
Installing multiple Siebel Enterprises in the same Siebel Gateway is not recommended, except in special circumstances. In the event that a Siebel Server or Siebel Enterprise needs to be removed, please follow the uninstall directions in Siebel Installation Guide for your application version.

Possible Causes
One reason to use the srvredit command to delete a Siebel Server or Enterprise definition from the Siebel Gateway Name Server is when the Siebel Server is uninstalled with the Enterprise Server still running, as the Siebel Server name will be still present in the siebns.dat file.

Troubleshoot
Each Siebel application version is listed below that has the syntax for deleting a server or enterprise from the Gateway. Please take a backup of the \admin directory and use caution when using these commands. The srvredit command can be found under the \bin directory and \bin directories.

After running the srvredit command to delete a Siebel Server or Enterprise Server you must restart the Siebel Gateway Name Server service for the changes to take effect.

Siebel version 8.0 (Windows and UNIX)
The srvredit command is no longer supported.

For Siebel Enterprise Server and Siebel Server components, the uninstallation wizard includes a step for removing configuration data for the products you are uninstalling:

_ When you uninstall a Siebel Server, the Siebel Configuration Wizard includes an option to remove an existing configuration which safely removes Siebel Server configuration data from the Gateway Name Server.

_ When you uninstall an entire Siebel Enterprise Server, the Siebel Configuration Wizard includes an option to remove a Siebel Enterprise Server configuration data from the Gateway Name Server.

For more information, see Siebel Bookshelf version 8.0 > Siebel Installation Guide (for Windows/UNIX) > Uninstalling Siebel Business Applications

Siebel version 7.x (Windows and Unix)
The srvredit command is no longer supported. However, customers may still find the following documentation references:

Siebel Bookshelf version 7.8 > Siebel Installation Guide for Microsoft Windows: Servers, Mobile Web Clients, Tools > Uninstalling Siebel Applications > Uninstalling Siebel Servers or the Siebel Enterprise, Using srvredit.

Siebel Bookshelf version 7.8 > Siebel Installation Guide for UNIX: Servers, Mobile Web Clients, Tools > Uninstalling Siebel Applications > Uninstalling Siebel Servers or the Siebel Enterprise, Using srvredit.

The recommended procedure is to completely uninstall and reinstall the Siebel environment. Customers may still use srvredit command at their own discretion, taking in consideration that any unexpected behaviors that may occur as a result from running srvredit cannot be supported.

Additionally for UNIX platforms, a Siebel Server can also be deleted by running the $SIEBEL_ROOT/bin/config_server script and selecting the ”Delete an existing Siebel Server” option. In the background, this script invokes the srvredit command.

Read More »

"The selected record has been modified by another user since it was retrieved. Please continue. (SBL-DAT-00523)”

Possible Case 1

• The record in the context of current memory on a query output is updated by another memory context of same record.
• A workflow process in Siebel attempted to update a record that another user or task updated since the application initially retrieved the workflow process.

Solution

• Try to use the methods RefreshBusComp() method or RefreshRecord() method depending on your requirement.
• Use spooling or logging to check if error is due to modification number or not. You can extract the driving query and check. If that is the problem then you can resolve it by doing refresh records.

Possible Case 2
Symptoms
In a Task Based UI (TBUI) task which associates contact records to a parent record (such as Activities) for some contact records the following error occurs:

Cause
When contact records are imported via EIM, there are sometimes contacts records with some missing foreign key values. This is not an issue in regular UI, as these are updated as soon as the record is accessed in the UI.

In regular UI, a hidden, behind-the-scenes save is performed and these missing values are populated. However in TBUI when these records are accessed in TBUI, the record is saved and the record that TBUI has in temporary storage is out of sync with the record in the Siebel base tables, and this issue occurs. This issue is likely t occur anywhere there is an Auto Primary property set to Default/Select and the field has no value.

One example of this is the S_CONTACT.PR_SYNC_USER_ID column.
In one case where this issue was documented to happen it was found in the log file for the Contact records, if the S_CONTACT.PR_SYNC_USER_ID = NULL, then associating the Contact to the Activity will trigger TBUI to populate S_TU_LOG for unnecessary "Update" operations on S_CONTACT & S_PARTY. This resulted in the error being shown in the task. If S_CONTACT.PR_SYNC_USER_ID = "No Match Row Id" or some other value, then everything worked fine.

Solution
There are three workarounds for this issue:

#1
1) Query/Select Contact BC
2) Select MultiValueLink "PIM Sync Owner"
3) Change the Auto Primary Value to "None"

#2
Pre-Default the value for Primary PIM Sync Owner Id to "No Match Row Id"

#3
Set Business Component User Property “Immediate Commit In Task” = TRUE for the Contact BC.
This will force the Contact BC to be non-transactional in TBUI, and all changes to the Contact BC to made directly to the Siebel tables. This will prevent the error from happening, but entire task will need to be thoroughly tested to ensure that this does not adversely affect where contacts are reference in other parts of the task.

If need be, the Contact BC can be copied and the Business Component User Property “Immediate Commit In Task” = TRUE for the copy of the contact BC. This will allow the one place in the task to use the non-transactional Contact BC and the rest of the task use the regular Contact BC. This too would need thorough testing, as Bookshelf notes any changes to transactional nature of TBUI requires additional testing.

Read More »

Siebel Error SBL-SMI-00049: 

Internal: There is no connection to the gateway server.

Explanation

The connection to Siebel Gateway Server has been lost. This can be caused by the Siebel Gateway Server process being stopped, the machine hosting the Siebel Gateway Server being shutdown, or a network problem between the Siebel Gateway Server machine and the machine that hosts the component that throws this error message.

Corrective Action

Verify that the machine where the error appears can connect to the Siebel Gateway Server machine over the network by pinging it. Also verify that the Siebel Gateway Server process is running and that each part of the infrastructure is using the same build and version of the application software.

This error may be expected if the Siebel Server and Siebel Gateway Server are stopped in rapid succession where some components on the Siebel Server are not stopped before the Siebel Gateway Server is stopped. In this case, no action is required.

Read More »

Siebel Server Down and Not Coming Up When Gateway Shifts Node In Cluster Environment.

Symptoms
One of Siebel server was not getting failover to other node if gateway was getting failover.
Below were scenarios observed in Customer's environment.

For Scenario1:
Gateway and Siebel Server1 is running on Node1
Siebel Server2 is running on Node2
Customer is able to start both siebel servers and fail over is happening properly.

For Scenario2:
Gateway and Siebel Server2 is running on Node2
Siebel Server1 is running on Node1
Customer is able to start both Siebel servers but fail over for siebel server2 is not happening.

So problem was with Siebel server2 when gateway is running on Node2

Cause
There were separate data sources in each cluster node for each server i.e. for Siebel Server1, Siebel Server2 and for Gateway Server. In case of second scenario, Siebel Server2 was not coming up giving below error: (listener.cpp (172) err=2555922 sys=0) SBL-SCM-00018: Could not open connection to Siebel Gateway configuration store

On further investigation Siebel servers service entry showed incorrect gateway server entry for second siebel server.

Solution
Updating registry for second siebel server 'service entry' with proper gateway entry followed by reboot of cluster box solved the issue.

Read More »

Business Component Not In Cached Update Mode.

Symptoms Customer is getting an error when clicking on "Verify" menu item under Sales Orders, view "Order Entry - Line Items Detail View (Sales)":

Errort Message
1) (SBL-BPR-00162)(SBL-DAT-00469)||Error invoking service 'Context Service', method 'SyncRowSetData' at step 'Sync Row Set'.(SBL-BPR-00162)
2) Business component 'Order Entry - Line Items' is not in cached update mode.(SBL-DAT-00469)


Reproducible Steps
1. Create an order using a customer product and customize it
2. Click on the "Verify" menu time on the Order Header. It directly throws the above mentioned error.

Expected Behaviour:
Clicking on "Verify" should provide the eligibility related status and comments and error if applicable.

Actual Behaviour:
Clicking on "Verify" is throwing the above mentioned error message for all the users. Because of the error above eligibility workflow does not synchronize successfully, eligibility status is not written to the DB

Environment Details:
Customer is having this issue in their custom environment of 7.8.2.10.

Business Impact:
Customer is not able to proceed further with their business requirement due to this issue.

Cause
The error happens when the underlying eligibility workflow tries to synchronize all changes to the DB. Method name = SyncRowSetData
BS name = Context Service
Error = Error invoking service 'Context Service', method 'SyncRowSetData' at step 'Sync Row Set'.(SBL-BPR-00162)
--
Unable to load message 0xffff(SBL-GEN-00000)

Business component 'Order Entry - Line Items' is not in cached update mode.(SBL-DAT-00469) 

This will stop writing the message into the DB

In order to improve performance of mass updates to the DB a new BC mode was introduced: 

Cache Update Mode. This allows Siebel to write updates in one block into the DB.

When Verify button is clicked it raises the QuotesAndOrdersValidate signal which first does a reprice. During the reprice "Context Service" BS is called and when it tries to synchronize the information  BeginCachedUpdates is called for the parent BC. In BeginCachedUpdates Siebel loops through all of the child BCs and set them into cached update mode.
This is where the error occurs. Customer has added a custom VBC and has made it a child BC of the "Order Entry – Line Items" BC in the "Order Entry (Sales)" BO. When upper loop reaches the custom VBC and tries to set cached update mode it errors out since VBCs are not supported in cached update mode.

Solution

Bug#10605225 was created to address this in the Siebel code and to offer a solution without the need of further configuration changes on customer side.

Following Siebel versions are offered for fixing this issue:

• 7.8.2.14QF
• 7.8.2.16QF
• 8.2.2
• 8.0.0.14FP
• 8.1.1.6FP
• 8.1.1.3QF
• 8.1.1.4QF

Please note that usually additional Siebel Tools changes are necessary to activate the fix for custom VBC's:

• 1. Start Siebel Tools
• 2. Under Class, create a new record
• 3. Add the following information to the new class:

• Name: CSSBCOrderMgmtBaseVBC
• Super Class: CSSBCVExtern
• Dll: SSCAOMBC
• Object Type: Business Component

• 4. Under Business Component, search for your custom VBC
• 5. Change the class for this VBC to CSSBCOrderMgmtBaseVBC
• 6. Compile all objects that have been changed
• 7. Apply the new srf to the environment

You may need to repeat steps 4-5 for any future VBC where you plan on using it as a child of the Quote Item or Order Entry - Line Items BC.

Please review exact additional configuration steps by reviewing appropriate Maintenance Release Guide.

Read More »

Gateway server was starting but Siebel server was not coming up. 

SRBroker and SCBroker components were not coming up. 

Following errors got reported from SRBroker log file:

DBCLog DBCLogError 1 000016d44e640f10:0 2011-09-05 13:51:15 [DataDirect][ODBC Oracle driver][Oracle]ORA-01017: invalid username/password; logon denied
GenericLog GenericError 1 000016d44e640f10:0 2011-09-05 13:51:15 (srbthrd.cpp (4022) err=2097168 sys=0) SBL-SRM-00016: Unable to initialize the Database environment -- Unable to connect to DB (data ops)

Changes
Newly configured Enterprise.

Cause
Here as following enteries shows, siebel service entry was created by 'sadmin' user whereas enterprise was configured with 'siebel' user.

Siebel Service Entry:

C:\sba81\ses\siebsrvr\BIN\siebsvc -s siebsrvr -i _ -a "-g localhost:2320 -e -s -l enu -u sadmin -ep 1ltEcMU/4eSB5A==" -t 120 -h C:\sba81\ses\siebsrvr

Siebns.dat entry on enterprise username:
[/enterprises/SBA_81/parameters/Username]
Persistence=full
Type=string
Value="siebel"
Length=12

Solution
1) Start gateway server.
2) Navigate to and connect to 'srvrmgr'
3) Execute following command:
change ent param username=sadmin
Verify same by following command:
list ent param "username"
4) Restart gateway followed with siebel server and verify the results.

Read More »

Servers won't start; gateway throws error: "Fatal error (2555922): 

Could not open connection to Siebel Gateway configuration store (%1:%2)., exiting..."

Customer was not able to Start the Siebel Server and connect to the gateway, which was returning this error message:

In NameSrvr.log, this error message was found:SBL-SEC-10018:GenericLog GenericError 1 000000024b4371f4:0 2010-01-05 20:57:26 (secmgr.cpp (2735) err=4597527 sys=0) SBL-SEC-10007: The password you have entered is not correct. Please enter your password again,=.

Cause The issue was caused by an incorrect entry in .odbc.ini file.

The customer may have modified the entry while restored the disk, since hard disk space capacity problems were a consideration in this environment.

In the gateway server name file, siebns.dat, the parameters for the server data source connect string were set as follows:

[/enterprises/SiebelProd/named subsystems/ServerDataSrc/parameters/DSConnectString]
Persistence=full
Type=string
Value="PFFA"
Length=

In the $SIEBEL_ROOT/gtwysrvr/sys/.odbc.ini, file, the parameter "ServerName" contained a different value than that of the corresponding "ServerDataSrc-DSConnectString" parameter in the siebns.dat file.

Solution 

After setting the ServerName parameter in the .odbc.ini file to the corresponding value of the "ServerDataSrv-DSConnectString" value in the siebns.dat file, the gateway and siebel servers were restarted and the issue was resolved. Customers were able to access the application in the usual manner.

Siebel Interview Question	Siebel Certifications
Siebel Admin Tutorials	Siebel Troubleshooting
Siebel Best Practices	Siebel Tutorials

Read More »