SBL-EAI-05010: Class name incorrect or does not extend SiebelBusinessService

SBL-EAI-05010: Class name incorrect or does not extend SiebelBusinessService : %1 Applies to: Siebel Reports - Version: 8.1.1 [21112] and later [Release: V8 and later ]
Information in this document applies to any platform.
SymptomsThis error message can occur under different circumstances but this document deals with the appearance of this error during interaction with the Oracle BI Publisher Server as part of a Siebel reporting solution.

The error message is indicative that calls are being made to custom Siebel Java classes which are unavailable to the Java Subsystem. As the classes are unavailable the XMLPReportServer cannot execute calls to methods within the class in question and returns an error in the logs similar to that shown below :

ObjMgrBusServiceLog Error 1 000000024b500290:0 2010-01-15 10:15:05 (javabsvc.cpp (181)) SBL-EAI-05010: Class name incorrect or does not extend SiebelBusinessService : com/siebel/data/SiebelPropertySet -- JVM Exception:java.lang.NoClassDefFoundError: com/siebel/data/SiebelPropertySet
ObjMgrBusServiceLog Error 1 000000024b500290:0 2010-01-15 10:15:05 (xmlpadaptersvc.cpp (2055)) SBL-EAI-05010: Class name incorrect or does not extend SiebelBusinessService : <?>
ObjMgrBusServiceLog Error 1 000000024b500290:0 2010-01-15 10:15:05 (xmlpdriversvc.cpp (567)) SBL-EAI-05010: Class name incorrect or does not extend SiebelBusinessService : <?>
GenericLog GenericError 1 000000024b500290:0 2010-01-15 10:15:05 Object manager error: ([0] Class name incorrect or does not extend SiebelBusinessService : <?>(SBL-EAI-05010) (0x231392))
GenericLog GenericError 1 000000024b500290:0 2010-01-15 10:15:05 ( (0) err=2818155 sys=2298770) SBL-OMS-00107: Object manager error: ([0] Class name incorrect or does not extend SiebelBusinessService : <?>(SBL-EAI-05010) (0x231392))
GenericLog GenericError 1 000000024b500290:0 2010-01-15 10:15:05 (bsvcmgr.cpp (1384) err=2818251 sys=0) SBL-OMS-00203: Error 2298770 invoking method "GenerateReport" for Business Service "XMLP Driver Service"
CauseThere are 2 possible explanations for this behavior but both relate to the configuration of the CLASSPATH parameter on theincorrectly configured classpath. The configuration of the CLASSPATH is detailed in the Siebel Reports Administration Guide > Adding an Explicit Reference to JAR Files for the Oracle BI Publisher Server (P.38).

The first possible cause is that the classes are contained within .jar files which are not included in the CLASSPATH.

The second possible cause is that the format of the CLASSPATH is incorrect as this differs between operating systems.
SolutionIn order to resolve this error message it is necessary to validate the CLASSPATH and ensure that all of the .jar files from the %SIEBEL_SERVER_ROOT%/CLASSES folder are set and that the correct separator is used for the operating system in question.

In UNIX environments the CLASSPATH separator is a colon character ':' and in Windows environments the CLASSPATH separator is a ';' character.

For example :
When running in a Windows environment the CLASSPATH may look like this (assuming the Siebel Server is installed in the C:\sia81\siebsrvr folder) :
C:\sia81\siebsrvr\CLASSES\bicmn.jar;C:\sia81\siebsrvr\CLASSES\bipres.jar;C:\sia81\siebsrvr\CLASSES\collections.jar;C:\sia81\siebsrvr\CLASSES\fix6312772.jar;C:\sia81\siebsrvr\CLASSES\i18nAPI_v3.jar;C:\sia81\siebsrvr\CLASSES\jdbc12.jar;C:\sia81\siebsrvr\CLASSES\jewt4.jar;C:\sia81\siebsrvr\CLASSES\share.jar;C:\sia81\siebsrvr\CLASSES\Siebel.jar;C:\sia81\siebsrvr\CLASSES\SiebelCustomXMLP.jar;C:\sia81\siebsrvr\CLASSES\SiebelXMLP.jar;C:\sia81\siebsrvr\CLASSES\versioninfo.jar;C:\sia81\siebsrvr\CLASSES\xdocore.jar;C:\sia81\siebsrvr\CLASSES\xdoparser.jar;C:\sia81\siebsrvr\CLASSES\xmlparserv2-904.jar;C:\sia81\siebsrvr\CLASSES\XSLFunctions.jar

When running in a UNIX environment the CLASSPATH may look like this (assuming the Siebel Server is installed in the C:\sia81\siebsrvr folder) :
${SIEBEL_HOME}/classes/bicmn.jar:${SIEBEL_HOME}/classes/bipres.jar:${SIEBEL_HOME}/classes/collections.jar:${SIEBEL_HOME}/classes/fix6312772.jar:${SIEBEL_HOME}/classes/i18nAPI_v3.jar:${SIEBEL_HOME}/classes/jdbc12.jar:${SIEBEL_HOME}/classes/jewt4.jar:${SIEBEL_HOME}/classes/share.jar:${SIEBEL_HOME}/classes/Siebel.jar:${SIEBEL_HOME}/classes/SiebelCustomXMLP.jar:${SIEBEL_HOME}/classes/SiebelXMLP.jar:${SIEBEL_HOME}/classes/versioninfo.jar:${SIEBEL_HOME}/classes/xdocore.jar:${SIEBEL_HOME}/classes/xdoparser.jar:${SIEBEL_HOME}/classes/xmlparserv2-904.jar:${SIEBEL_HOME}/classes/XSLFunctions.jarwhere ${SIEBEL_HOME} is the actual path where the Siebel application is installed.
Important Notes :
1) In UNIX environments please take note of the case sensitivity of the Siebel.jar file in the CLASSPATH. Some documentation references show this as a lowercase filename (e.g. siebel.jar) which is incorrect. Please ensure that when setting the CLASSPATH parameter the filename is capitalized (e.g. Siebel.jar) as per the listing above.
2) If implementing the display of signatures within BI Publisher Reports then the following additional .jar files should be included in the CLASSPATH :

C:\sia81\siebsrvr\CLASSES\InkToolsLib.jar
C:\sia81\siebsrvr\CLASSES\iSignBmp.jar
3) In SIA environments the following additional .jar file will be found :

C:\sia81\siebsrvr\CLASSES\SiebelCustomXMLP_SIA.jar;
A Documentation Bug #12-1UW67TF has been raised to ensure that the Reports Administration Guide is updated with this information.
Related

--------------------------------------------------------------------------------


Products

--------------------------------------------------------------------------------


Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel Reports
Keywords

--------------------------------------------------------------------------------
 
JAVA.LANG.NOCLASSDEFFOUNDERROR; BI PUBLISHER; NOCLASSDEFFOUNDERROR; JAVA CLASSES; REPORT; CLASSPATH 
Errors
--------------------------------------------------------------------------------
 
SBL-EAI-05010; SBL-OMS-00203; SBL-OMS-00107; ERROR 229877; ERROR 1











Applies to: Siebel Reports - Version: 8.1.1 SIA [21111] and later [Release: V8 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Siebel 8.1.1.1 integrated with BI Publisher Server 10.1.3.4.1.
SymptomsWhen uploading any out-of-the-box BI Publisher report, the message below is displayed:

SBL-EAI-05010: Class name incorrect or does not extend SiebelBusinessService : com/siebel/data/SiebelPropertySet -- JVM Exception:java.lang.NoClassDefFoundError: com/siebel/data/SiebelPropertySetObjMgrBusServiceLog
Object manager error: ([0] Class name incorrect or does not extend SiebelBusinessService : <?>(SBL-EAI-05010)

CauseDocument 850954.1 indicates this error is usually caused by incorrect entries for CLASSPATH and/or DLL in the named subsystem.
SolutionSome of the possible causes are listed below. Please make sure the configuration is set correctly:

1) Set JAVA_HOME system variable to JDK installation path (i.e. C:\Program Files\Java\jdk1.5.0_15) for Siebel and BI Publisher servers.

2) Confirm that you have copied the following files from the SIEBSRVR_ROOT/CLASSES directory:
- XSLFunctions.JAR
- SiebelCustomXMLP.JAR
- SiebelCustomXMLP_SIA.JAR
and paste them to the following Oracle Application Server directory:
OracleAS_HOME/j2ee/home/applications/xmlpserver/xmlpserver/WEB-INF/lib

3) Set JAR files in JVM Classpath parameter for XMLPJvmSubsys Profile Configuration as below:

a) Log in to the Server Manager command-line interface (srvrmgr program).

b) Execute the following command to change the CLASSPATH:
change param CLASSPATH=SIEBSRVR_ROOT\classes\SiebelXMLP.jar;SIEBSRVR_ROOT\classes\
xdoparser.jar;SIEBSRVR_ROOT\classes\fix6312772.jar;SIEBSRVR_ROOT\classes\
xdocore.jar;SIEBSRVR_ROOT\classes\xmlparserv2-904.jar;SIEBSRVR_ROOT\classes\
versioninfo.jar;SIEBSRVR_ROOT\classes\share.jar;SIEBSRVR_ROOT\classes\jewt4.jar;
SIEBSRVR_ROOT\classes\jdbc12.jar;SIEBSRVR_ROOT\classes\i18nAPI_v3.jar;
SIEBSRVR_ROOT\classesvcollections.jar;SIEBSRVR_ROOT\classes\bipres.jar;
SIEBSRVR_ROOT\classes\bicmn.jar;SIEBSRVR_ROOT\classes\Siebel.jar;
SIEBSRVR_ROOT\classes\XSLFunctions.jar;SIEBSRVR_ROOT\classes\SiebelCustomXMLP.jar
for named subsystem XMLPJvmSubsys

Restart Siebel Server machine.

4) Navigate to Administration - Server Configuration > Servers > select your server > select XMLPReportServer component > Parameters > select "JVM Subsystem Name" parameter. The default value is "JAVA". Please, change it to XMLPJvmSubsys.

For further information on this topic please review Document 989142.1 What are the possible causes for the 'Class name incorrect or does not extend SiebelBusinessService' error ?

SBL-DAT-60237: Error loading dictionary file diccache.dat

SBL-DAT-60237: Error loading dictionary file diccache.dat.

Cause

This behavior was caused by an Oracle database specific connectivity issue where the ODBC name must match the tnsnames.ora alias.  The KEYDBMGR utility reads the connect string out of the .cfg file specified on its command line and then attempts to create an ODBC connection.  With Oracle based Siebel implementations, however, the Siebel application normally uses Oracle native connectivity and therefore the connect string value is the tnsnames.ora alias name.

Solution

The suggested workaround is to create an ODBC data source with the same name as the Oracle TNS Names alias referenced in the .cfg file you specify on the keydbmgr.exe command line.

So assume that you have a standard Siebel generated ODBC data source named something like SiebSrvr_Siebel. Look at what the actual Oracle connect string is (for example siebeldb). Then create another ODBC datasource using the same driver but name the ODBC data source "siebeldb" (using my example).
After this is completed, try keydbmgr.exe again.

Symptoms


Keydbupgrade.exe utility was not working.
Verified this issue by reviewing the output of keydbupgrade execution as below:

D:\sba80\siebsrvr\BIN>keydbupgrade.exe /u SADMIN /p SADMIN /l enu /c .\enu\epharma.cfg
Error loading dictionary file diccache.dat.(SBL-DAT-60237)
Cleaning up... this may take a while.

Cause


Incorrect parameters in epharma.cfg file

Parameter ServerDbODBCDataSource in epharma.cfg file was set to %MASTER_DATASOURCE%.

Solution


1. Open epharma.cfg file
2. Locate parameter ServerDbODBCDataSource under [Siebel] section.
3. Change this parameter to the correct ODBC Data Source.
4. Save and close the file.
5. Execute keydbupgrade.exe utility and confirm if it works fine.

Applies to:

Product Release: V8 (Enterprise)
Version: 8.0 [20405] Fin Svcs
Database: Oracle 10.2.0.2
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Sun Solaris 9

This document was previously published as Siebel SR 38-3395346953.

Symptoms

SBL-DAT-60237I change the password on the Siebel databse for AVCI01S and was able to connect with SQL Programmer but I'm getting an error. The following error appears in the log file:
ProcessPluginRequest    ProcessPluginRequestError    1    0000000a468d214c:1    2007-07-05 16:51:27     5844: [SWSE] Failed to obtain a session ID. Error loading dictionary file diccache.dat.

ProcessPluginRequest    ProcessPluginRequestError    1    0000000a468d214c:1    2007-07-05 16:51:27     5844: [SWSE] Set Error Response (Session: Error: 07727949 Message: Error loading dictionary file diccache.dat.(SBL-DAT-60237))

I also renamed the diccache file so that it creates a new one and it still shows the same error. At what time are you available for another web conference? The earlier the better.

Thank You,
Troy

Solution

Message 1

For the benefit of other readers,


Customer was configuring Siebel ADSI Security Adapter (ADSISecAdpt) version 8.0. After all settings were performed, error message below was logged in Object Manager and Siebel Web Server Extension log files:

SBL-DAT-60237: Error loading dictionary file diccache.dat

After further investigation and testing, we were able to find that above error message was caused by shared database account. The shared database credentials are stored in the attribute defined by “Credentials Attribute Type” parameter of ADSI account defined by “Shared Credentials DN”parameter of ADSISecAdpt profile. The shared database credentials are stored in the format below:

username=<username> password=<password>

In previous Siebel versions, it was not required that the shared database accont to exist in Siebel Application as an employee. However, in Siebel version 8.0 this is required. Customer was using AVCI01S database account as shared database. After a new employee with same User ID as AVCI01S was created only in Siebel Application, ADSISecAdpt authentication worked fine and users were able to authenticate against ADSI Directory.

Change Request 12-1K81U2D has been opened to address this Product Defect and allow usage of shared database credentials of an account that does not exist in Siebel Application.

The workaround is to create a new Siebel user with same User ID as shared database account.

Applies to:

Siebel Tools - Version: 8.0.0.1 [20408] - Release: V8
Information in this document applies to any platform.
***Checked for relevance on 16-Feb-2010***

Symptoms

When opening the Check In / Check Out dialog box in Tools, this error occurs:

08001 (-816): [Siebel Database][ODBC Driver][Adaptive Server Anywhere]Specified database file already in use


In the corresponding log file you might also observe these related error messages:

DBCLog DBCLogError 1 00000002487415c8:0 2008-07-09 09:21:32 [Sybase][ODBC Driver][Adaptive Server Anywhere]Specified database file already in use
GenericLog GenericError 1 00000002487415c8:0 2008-07-09 09:21:32 08001: [Siebel Database][ODBC Driver][Adaptive Server Anywhere]Specified database file already in use
GenericLog GenericError 1 00000002487415c8:0 2008-07-09 09:21:32 (wraprmtcmn.cpp (63) err=1114276 sys=600) SBL-DCK-00164: Error connecting to datasource SEAW Local Db default instance (YYYT789).
GenericLog GenericError 1 00000002487415c8:0 2008-07-09 09:21:32 Error connecting to datasource %1 (%2).
ObjMgrLog Error 1 00000002487415c8:0 2008-07-09 09:21:32 (ctxtmgr.cpp (2334)) SBL-DCK-00164: Error connecting to datasource SEAW Local Db default instance (YYYT789).
ObjMgrLog Error 1 00000002487415c8:0 2008-07-09 09:21:32 (ctxtmgr.cpp (2355)) SBL-DAT-60237: Error loading dictionary file diccache.dat.
ObjMgrSessionLog Error 1 00000002487415c8:0 2008-07-09 09:21:32 (model.cpp (5886)) SBL-DAT-60237: Error loading dictionary file diccache.dat."

Cause

The error is caused by the ODBC data source settings for the local Tools database, which include a value in the "Server name" field by default. This causes a second connection to the local Tools database to fail.
Bug 12-1NCHPDP has been raised for this issue because the Server name field is filled by default by the Tools installation process.
After removing the "Server name" value, the error disappears.

Solution

  1. Open the ODBC Administrator.
  2. Select the System DSN tab. 
  3. Select the local Tools datasource (by default, "SSD Local Db default instance").
  4. Click the Configure button.
  5. In the configuration window, select the Database tab.
  6. Clear the field labeled "Server name".
  7. Close the configuration window and exit the ODBC Administrator.
This solution has been successfully tested with a standard Tools installation.

Note: This situation can also occur for dedicated Web clients. The same solution applies for this case.

References

BUG:12-1NCHPDP - "SPECIFIED DATABASE FILE ALREADY IN USE" ERROR WHEN DOING CHECK IN OR CHECK OUT

Applies to:

Siebel System Software - Version: 8.0 [20405] to 8.1.1 SIA [21111] - Release: V8 to V8
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V8 (Enterprise)
Version: 8.0 [20405]
Database: Microsoft SQL Server 2005
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Microsoft Windows 2003 Server SP1

This document was previously published as Siebel SR 38-3317466373.

""""Checked for relevance on 20-Oct-2010""""

Symptoms

Hi Support:

I cannot install Siebel 8.0 at all, I have tried using the standard setup procedure and also with the FastTrack Wizard.

With both procedures, it ends with these errors on the logs when trying to log on for example to http://mysibelserver/ecommunications_enu


ss070403_1412.log (SWE log)

SisnapiLayerLog Error   1       0000002646120eb0:0      2007-04-03 18:26:32       1756: [SISNAPI] Async Thread: connection (0x2e09e80), error (1180682) while reading message
ObjMgrSessionLog        Error   1       0000002646120eb0:0      2007-04-03 18:26:32     Login failed for Login name : HI_USER
ProcessPluginState      ProcessPluginStateError 1       0000002646120eb0:0      2007-04-03 18:26:32       3052: [SWSE] Open Session failed (0x75eb4d) after      0.0661 seconds.
ProcessPluginRequest    ProcessPluginRequestError       1       0000002646120eb0:0      2007-04-03 18:26:32       3052: [SWSE] Failed to obtain a session ID. Error loading dictionary file diccache.dat.
ProcessPluginRequest    ProcessPluginRequestError       1       0000002646120eb0:0      2007-04-03 18:26:32       3052: [SWSE] Set Error Response (Session: Error: 07727949 Message: Error loading dictionary file diccache.dat.(SBL-DAT-60237))

Cause

You have installed Siebel version 8.0 but when trying to login to the application you received an error message:

Login failed for Login name : HI_USER
3052: [SWSE] Set Error Response (Session: Error: 07727949 Message: Error loading dictionary file diccache.dat.(SBL-DAT-60237))

We concluded that the object manager failed to open an anonymous session for user “HI_USER”. This user is not created by default when running the grantusr.sql script, and is also not available as an employee in the standard application.

Solution

The Installation Guide > Installing and Configuring the Siebel Web Server Extension > Configuring the SWSE > Creating the SWSE Logical Profile > Parameters for Creating the SWSE Logical Profile advises that the anonymous user should be created as an Employee:

"The Siebel user ID for a valid employee. Used to start the anonymous session from which the user is shown the login page for an employee application.”

There are two possible workarounds:

1) Temporarily use ‘sadmin’ as the anonymous user, and later modify the eapps.cfg manually

2) Install a separate machine with Windows XP; install the Dedicated Web Client; create the Employee under ‘Administration – User’ screen; and then continue with SWSE installation

I have created Change Request 12-1J5GID3 to make it clear in the Installation Guide that the user provided when configuring the SWSE Logical Profile should be created first in the application as an employee.

Applies to:

Siebel System Software - Version: 8.1 SIA [21039] - Release: V8

Information in this document applies to any platform.

Symptoms


Customer was upgrading from 7.8 to 8.1 and when they try to connect with Tools 8.1.1 to run Repository Merge the following errors appear in siebdev.log:
Error loading dictionary file diccache.dat (SBL-DAT-60237)
Error loading dictionary (SBL-DCK-00163)
You are not currently licensed to use Siebel Tools (SBL-DEV-00133)
Also, Additional Message: Repository 'Siebel Repository' does not exist in database.

Cause


The issue is caused by the incorrect Repository name set in the tools.cfg-
they had DockRepositoryName=Siebel Repository, where they have only "New Siebel Repository" in the database.

Solution


To resolve the issue, in tools.cfg change parameter DockRepositoryName to the name of the repository you have, in this case "New Siebel Repository.
Change request #12-1SW8MZP has been logged asking for this to be documented in the Upgrade Guide.

References

BUG:12-1SW8MZP - REPOSITORY 'SIEBEL REPOSITORY' DOES NOT EXIST IN DATABASE.

Applies to:

Siebel Sales - Version: 7.7 [18026] BETA to 8.1.1 [21112] - Release: V7 to V8

Information in this document applies to any platform.

Symptoms

User is encountering the following error when trying to run the encryptupg utility:

The user-context could not be established. Something is wrong with the assigned primary position or login related repository objects. See additional error messages for more information.(SBL-DAT-00546)The username you have entered is invalid. Please try to log on again or contact your system administrator for assistance.(SBL-DAT-00254)

Cleaning up... this may take a while.

Cause

This behavior is most likely caused by the tableowner database userID not having a corresponding Siebel account and/or that account not having adequate responsibilities / positions.
The error messages are actually pretty self-explanatory:
The user-context could not be established. Something is wrong with the assigned primary position or login related repository objects. See additional error messages for more information.(SBL-DAT-00546)The username you have entered is invalid. Please try to log on again or contact your system administrator for assistance.(SBL-DAT-00254)
The presence of the second message leads us to believe that the tableowner does not have a matching record in the OLTP's S_USER table. This is not uncommon since, by default, the tableowner is not created as a Siebel userID.

Solution

The most likely cause of the behavior you are seeing is that the user you are using to run the encryptupg.exe is the tableowner for your Siebel on-line transactional processing (OLTP) database. While that is actually a good way of running the encryptupg.exe utility (in Oracle it actually is required), there is an issue that the tableowner database account is not by default a Siebel application login. This is why you are seeing the SBL-DAT-00546 and SBL-DAT-00254 errors.

The solution for this is to create a Siebel login for the tableowner account (the default tableowner is SIEBEL). The easiest way to do this and get adequate permissions is to simply copy the SADMIN user.

1. Log into an employee facing, high interactivity Siebel application such as Sales or Call Center using an administrator ID such as SADMIN.

2. Navigate to Site Map > Administration - Users > Employees.

3. On the Employees screen do a query for the login SADMIN (or whatever your administrator user's login is).

4. Click the little Menu button on the list applet and select Copy Record.

5. Fill in the required fields making sure you use the tableowner (SIEBEL in a default implementation) as the login / userID.

6. Save the record.

After doing this, please retest the use of the encryptupg.exe utility.

Also, although not directly related to this behavior, I would like to proactively call your attention to Note 551663.1 on Metalink 3. This discusses a specific issue when using encryption with Oracle databases.

SBL-DAT-60227: User name %1 does not match

SBL-DAT-60227: User name %1 does not match either the current Me user name or the You user name.


Explanation

The error occurs when User Profile Service is invoked to unload user attributes for a specific user who is not currently loaded.

Corrective Action

You can first invoke User Profile Service to find out the current loaded users and then choose one to unload.

SBL-DAT-60217: Can't write data without validation

Symptoms:

When task transaction has been disabled, setting DeferWrite=True for Siebel Operation Insert Step causes the task to give the following errors:
SBL-BPR-00187, SBL-BPR-00100, SBL-DAT-60217
The specific error message is:
[1] Error updating business component at step '<step name>'. (SBL-BPR-00187)
[2] This error is returned when the workflow/task is executing the Siebel Operation business service.(SBL-BPR-00100)
[3] Can't write data without validation.(SBL-DAT-60217)
Note that <step name> shown above is a placeholder for the step where the error occurs.
These errors occur in the task when the Siebel Operation step with DeferWrite=True in the task is reached.


Cause

DeferWrite =True is not supported when task transaction has been disabled. 
When task transaction has been disabled, DeferWrite=True should not be used. 
Note that there are two cases for this, as task transaction can be disabled in two ways:
  1. Task Transaction disabled for the entire Task.
    When task transaction has been disabled at task level, by setting theTransactional task property to FALSE, then DeferWrite=True should NOT be used in any Siebel Operation INSERT steps in that specific task.
  2. Task Transaction disabled at the Business Component Level.
    When task transaction has been disabled at Business Component level, by setting Immediate Commit In Task user property to TRUE for a specific Business Component, then DeferWrite=True should NOT be used in any Siebel Operation INSERT steps which are based on that specific Business Component in any Task.
A new documentation change request Bug 12-1X47EZR  has been submitted to request that this information be added to bookshelf.
Disabling Task Transaction should be done only when needed and thoroughly tested, as noted in the Siebel Bookshelf, Business Process Framework: Task UI Guide.
Task transaction is a mechanism that allows you to keep data associated with a task instance separate from the Siebel Business Component tables until the task data is explicitly committed to the database. The default behavior for tasks is to have task transaction enabled. Disabling task transaction can result in unpredictable behavior and must be thoroughly tested before use in production.

Solution

When task transaction has been disabled, then DeferWrite=True should not be used. 

Workaround:
When Task Transaction needs to be disabled, DeferWrite can be set to False on the Siebel Operation INSERT step which is affected by this. Please reference the two cases described above in the Cause section of this document.
When DeferWrite = False, then all of the required fields for that Business Component must be provided some values inside the Siebel Operation step. These values can then be updated by the user in the subsequent Task Views. As mentioned above, this will need to be thoroughly tested.


Symptoms

Customer has set Task Transaction property False and also Derfer Write property - False. Customer trying to pause the task by the pause button - getting following error.
Customer getting error in task that Can't write data without validation.(SBL-DAT-60217)

Cause


These errors occur in the task when the Siebel Operation step with DeferWrite=True in the task is reached.
But it was set to False.
Steps -

Created Task based in Action BO

Start -> Siebel Operation --> view -->End

Siebel Operation with Defer Write - false and Task - Transaction Property - False

If you modify the some field on applet and pause the task by pause button - giving error - Can't write data without validation

If you hit out side also - it is giving error - Can't write data without validation

This is a Product Defect.

Solution

This is a product Defect. CR #12-1Z6VWWC has been raised to address this issue.
Code fix requires a low level change which may require lot to be compiled. This is going to fix in next fix pack. This can not be provide as Quick fix in current version.

SBL-DAT-60236-Expression does not match


SBL-DAT-60236: Expression does not match any Siebel query language grammar rules. Unexpected token '%1' found at or near location %2.


In this Document

Using Siebel SIA 8.0.0.5 [20420] Universal Customer Master application with third party Trillium product for real-time data quality.

When attempting to match records with fields that contain a special character in them, for example, the apostrophe, ', the following error occurs:

ERROR
-----------------------
SBL-DAT-00354: The query could not be run because the criteria for field '' contained an invalid arithmetic expression. Please ensure that the search criteria is correctly formatted.

This error is often caused by a missing operator (e.g. = or <) or missing quotes. If you aren't sure what may have caused this please contact your systems administrator.

SBL-DAT-60236: Expression does not match any Siebel query language grammar rules.

STEPS
-----------------------
By following these steps the issue can be reproduced:
1. Set up the Universal Connector for data quality matching and set client/object manager to use the appropriate type
2. Set the real-time data matching settings in Administration - Data Quality > Data Quality Settings:
3. Amend the Account Token Expression and Account Query Expression to allow you to capture a suitable number of characters from the address
4. Logout and in again for changes to take effect
5. Enter two accounts e.g. Test Account with site 1 and Test Account with site 2
6. After the second account has been saved, the deduplication popup should show the first as a match
7. Check S_DQ_ORG_KEY table to make sure that Universal Connector is being used - there should be  two records with KEY_VALUE = _____T_____
8. Now add an address to one of them and save it, e.g.
      Street Address = A Place in the Sun
      City = Redwood Shores
      State = CA
      Zip Code = 11111
      Country = USA
9. Check the S_DQ_ORG_KEY table. The key should now be '11111TA PLA'
10. Now add an address with an apostrophe (') to the other account and save it, e.g.
      Street Address = A'Place in the Sun
      City = Redwood Shores
      State = CA
      Zip Code = 11111
      Country = USA
11. Receive the following error message:

[1] Invalid search specification '[DQ System Id] = '1-AIZ3' AND [Parent Id] LIKE '1-CF1T' AND [Key Value] NOT LIKE '11111TA'PLA''.
Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00501)

[2] Expression does not match any Siebel query language grammar rules. Unexpected token 'PLA' found at or near location 90.(SBL-DAT-60236)

EXPECTED BEHAVIOR
-----------------------
The customer expects that Siebel can handle special characters when performing data matching with third party products via the Universal Connector.

Cause

The cause was determined to be a new product defect.

The following two change requests were logged for this issue:

Bug 12-1V418BZ - SBL-DAT-60236 error message when using Universal Connector with an apostrophe
Bug 12-1V9U44R - UCM dedup token generation expression is causing BDM workflow to fail in 'CDM Match' step

The first (Bug 12-1V418BZ) addresses the real-time user interface scenario and the second (Bug 12-1V9U44R) addresses the integration scenario. The cause is that neither the search specification for the 'Key' business component (e.g. Account Key, Contact Key, Prospect Key) nor the 'Dedup Token' field in the Account, Contact or List Mgmt Prospective Contact business components can handle special characters.

Solution

The problem has been fixed in the following fix packs:

- 8.0.0.9 fix pack and higher

Alternatively, if you are unable to apply 8.0.0.9 fix pack or higher, the following quick fixes were built although they may not be available for all supported languages/operating systems:

- 8.0.0.7 QF0745
- 8.0.0.2 QF02C6/8.0.0.2 QF02D2 (both are needed)

References

BUG:12-1V418BZ - SBL-DAT-60236 ERROR MESSAGE WHEN USING UNIVERSAL CONNECTOR WITH AN APOSTROPHE
BUG:12-1V9U44R - UCM DEDUP TOKEN GENERATION EXPRESSION IS CAUSING BDM WORKFLOW TO FAIL IN 'CDM MATCH' STEP
NOTE:476946.1 - How Can You Implement a Replace String Function in eScript?

Applies to:

Siebel CRM - Version: 8.0 [20405] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Whilst querying with an apostrophe in the user interface in the Name field the following errors were seen:
The query could not be run because there is an invalid character in the field 'Name'. Please ensure that the value in the field is formatted correctly with only valid characters.

Missing quotes around the search criteria or unnecessary punctuation will often cause an error.(SBL-DAT-00403). 
Normally if querying for Jack's for example, one would expect to receive an error. The normal way to accommodate such queries including special characters is to surround the query within speech marks, for example "Jack's". However this did not work either.

Cause

The issue related to some custom eScript that was being used to ensure that users populated certain fields in the user interface.

An example exhibiting the same behaviour is shown below. This was used on the Account business component.

function BusComp_PreQuery ()
{
  var sName = GetSearchSpec("Name");
}

Through testing, it was found that the only special character that would not work in the query was the apostrophe. Other characters such as the following worked fine:

; , . @ # \ | + - = [ ] & *

The same behaviour was also seen in 7.7.2.6, so it is likely widespread across the application versions.

Bug 12-1LG178H: "GetSearchSpec on field in BusComp_PreQuery Event with UI query including apostrophe causes error" was raised as a product defect to address this problem for a future product release.

Solution

The following workarounds were suggested to the customer:

1. Instead of querying for "Jack's", try querying for "'Jack''s'". e.g. double quote, single quote, Jack, single quote, single quote, s, single quote, double quote.

2. Take the GetSearchSpec method off the field and utilise it on alternative fields.

3. Use a Try-Catch-Finally statement to catch the error. More details can be found here:
- Siebel eScript Language Reference > Siebel eScript Language Overview > Siebel eScript Statements > try Statement

4. Alternatively, use the GetSearchExpr() function and do string manipulation to check that relevant fields are populated. More details of this function can be found here:
- Siebel Object Interfaces Reference > Interfaces Reference > Business Component Methods > GetSearchExpr Method

The customer decided to use an alternative instead by basically reconstructing the string and replacing the ' with an * on the PreQuery event.

Keywords: SBL-DAT-60236, SBL-DAT-00354, SBL-DAT-00501, SBL-DAT-00403


Applies to:

Siebel CTI - Version: 8.1.1 [21112] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

After upgrading to Gplus adapter to 7.5.000.51 the customer no longer received screen pops for inbound calls.

Even though all the EventHandler FilterSpec criteria were being met in the Scomm log file we would see the following:

DPATEL_37748770[07/09/2010 15:10:54:922]:DEBUG:Found no matching EventHandler

Cause


=== ODM Cause Determination ===

In the Scomm log file when the configuration was loaded we could see the following:

SADMIN_10485773[07/19/2010 12:46:07:968]:DEBUG:BuildPreProcessData begin
SADMIN_10485773[07/19/2010 12:46:07:968]:DEBUG:BuildPreProcessData end
SADMIN_10485773[07/19/2010 12:46:07:968]:DEBUG:BuildAgentCfg_New begin
SADMIN_10485773[07/19/2010 12:46:07:968]:DEBUG:GetAgentCfg end

"BuildAgentCfg_New begin" but there is no "BuildAgentCfg_New end".

Also, in the OM log file we could see the following error message:

ObjMgrQueryLog Warning 2 000000024c3f0d48:0 2010-07-15 20:56:11 (query.cpp (13952)) SBL-DAT-60236: Expression does not match any Siebel query language grammar rules. Unexpected token '{' found at or near location 59.

ObjMgrLog Warning 2 000000024c3f0d48:0 2010-07-15 20:56:11 (query.cpp (2634)) SBL-DAT-00501: Invalid search specification 'NOT [$GetCommandStatus(IsInteractionView)] = 'Enabled' and {@Phone:PhoneTypeLookup}'.

In the .def file we had the following Command defined:

[Command:MakeCallToPhone]
Description = "Make Call to "{@Phone}""
DeviceCommand = "MakeCall"
FilterSpec = "NOT [$GetCommandStatus(IsInteractionView)] = 'Enabled' and {@Phone:PhoneTypeLookup}"
Hidden = "TRUE"
OnEditControl = "TRUE"
Profile = "Gplus Voice"
CmdData = "MakeCallToPhone"

If the same change is made in a standard environment then the same behavior is seen.

The issue is caused by the {} brackets around the @Phone:PhoneTypeLookup in the Command FilterSpec

NOT [$GetCommandStatus(IsInteractionView)] = 'Enabled' and {@Phone:PhoneTypeLookup}

This behavior was deemed to be a product defect and CR# 12-1Z1L7WJ was raised for this matter.

Solution


=== ODM Solution / Action Plan ===

To solve the issue in the command MakeCallToPhone change the FilterSpec as follows:

NOT [$GetCommandStatus(IsInteractionView)] = 'Enabled' and {@Phone:PhoneTypeLookup}

It should be something like:

NOT [$GetCommandStatus(IsInteractionView)] = 'Enabled' and [@Phone:PhoneTypeLookup] IS NOT NULL



Applies to:

Siebel Tools - Version: 8.0.0.1 [20408] to 8.0.0.3 [20416] - Release: V8 to V8
Information in this document applies to any platform.
Product Release: V8 (Enterprise)
Version: 8.0 [20405] NLD Com/Med
Database: Oracle 10.2.0.3
Application Server OS: Microsoft Windows 2003 Server SP2
Database Server OS: Red Hat Linux 4.0

This document was previously published as Siebel SR 38-3455974081.

Symptoms

SBL-DAT-60236
We encountered a problem when setting all LOV entries for the COUNTRY LOV to Multilingual.
The values that contain a single quote in the displayvalue or in the Language Independent Code, can not be set to Multilingual. When you try to change anything to these records they give an error.

We now removed all single quotes from the COUNTRY LOV, so we could set them to Multilingual.

Cote D'ivoire
Korea, Democratic People's Rep
Lao People's Democratic Republ

Bahama's (NLD)

Please let us know if this is the expected behaviour.
Is there a workaround to be able to use single quote's in multilingual LOV's.

Cause

Product defect - change request 12-1K5DYEJ

Solution

The customer noticed that in Siebel 8 a validation error meesage occurs when trying to save a List of Values (LOV) record that contains an apostrophe (single quote) character in either the Display Value or Language Independent Code field.

The error encountered on trying to saving the LOV record in the LOV administration screen was:

Invalid search specification '[Type] = 'AAG_ACCOUNT_TYPE' AND [Language] = 'ENU' AND (([Name] = 'Banking'' AND [Value] <> 'Banking' OR ([Value] = 'Banking' AND [Name] <> 'Banking'')) AND [Id] <> 'OVF-1L699"

Expression does not match any Siebel query language grammar rules. Unexpected token 'Banking' found at or near location 93. SBL-DAT-60236

This error occurs due to the second quote character appearing in the search specification expression that was generated by Siebel 8 as part of new validation logic. For example [Name] = 'Banking''

In previous versions of Siebel it was possible to enter and store LOV records that including the single quote character.

Issue was addressed by change request 12-1K5DYEJ which was fixed in Siebel 8.0.0.3 Fix Pack and is not present in Siebel 8.1.

The only workaround is to not enter single quote characters in to either the Display Value or LIC field of LOV records.

Keywords: WriteRecord; Write; Record; LOV; List; Values; Display; Value; Language; Independent; Code; Validate; search; spec; specification; quote; apostrophe.

Applies to:

Siebel Tools - Version: 8.1.1.1 [21211] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Goal


When doing a full compile, I end up with an SRF that is smaller than it should be and is not usable by the server or client. I am connected directly to the server database. This problem is intermittent - sometimes it produces a usable SRF, sometimes it doesn't - with no changes to anything.
This intermittent behavior is happening on a Windows 2003 PC.


Solution


This incorrect behavior was happening for one Siebel Tools client on a windows 2003 box.

Siebel client side logging was enabled for the Siebel Tools client using the Siebel_Log_Events environment variable.  The client side logging for Siebel Tools generated a siebdev.log file with the following types of errors.

ObjMgrQueryLog Warning 2 000000024c400300:0 2010-07-16 13:06:32 (query.cpp (13952)) SBL-DAT-60236: Expression does not match any Siebel query language grammar rules. Unexpected token '(' found at or near location 21.

ObjMgrLog Warning 2 000000024c400300:0 2010-07-16 13:06:32 (query.cpp (456)) SBL-DAT-00403: The query could not be run because there is an invalid character in the field 'Name'. Please ensure that the value in the field is formatted correctly with only valid characters.

After reviewing the Siebel Tools installation and environment, it was determined that the operating system of windows 2003 is not a supported operating system for the Siebel Developer Client per the
Siebel System Requirements and Supported Platforms documentation.

See the Siebel System Requirements and Supported Platforms > Client Environment Requirements >
Requirements for Employee Applications
Software Requirements for the Siebel Developer Web Client

But, it is not very clear that Employee Applications would include Siebel Tools.

Therefore a documentation defect was raised to address this unclear documentation.

Siebel Tools Product Management confirmed that the following operating systems are the supported platform for Tools/Dclient as per Siebel System Requirements and Supported Platforms documentation.

WinXP

Win7

Vista

Win2000

Note that Win2003 and Win2008 are not supported clients for Tools/Dedicated client.

Change Request CR 12-1Z9S19D is a documentation defect noting that the
System Required and Supported Platforms should be much clearer for Siebel Tools

SUMMARY
The system platforms discusses the environment requirements for Employee applications.
But it is not obvious that Siebel Tools is considered an Employee Application like a Siebel thin client running Siebel Call Center.

Siebel Tools is a considered a different application than a Siebel client application.

DESIRED DOCUMENTATION
The documentation should have a separate listing for Siebel Tools clients.

Siebel
System Requirements and Supported Platforms > Client Environment
Requirements >

Requirements for Employee Applications

Add a separate section for Siebel Tools.

Siebel System Requirements and Supported Platforms > Client
Environment Requirements >

Requirements for Siebel Tools

The recommendation was given to use a different PC with a supported platform for the Siebel Tools client.

Oracle Siebel Support

References

BUG:12-1Z9S19D - SYSTEM REQ SUPPORTED PLATFORMS SHOULD BE MUCH CLEARER FOR SIEBEL TOOLS

Applies to:

Siebel Reports - Version: 8.1.1 [21112] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms


Siebel Tools displays an error when generating Actuate Reports that include fields associated with Multivalue Links that have brackets in their names. The following error message appears:

The query could not be run because there is an invalid character in the field 'Name'. Please ensure that the value in the field is formatted correctly with only valid characters. Missing quotes around the search criteria or unnecessary punctuation will ofthen cause an error." "Expression does not match any Siebel query language grammar rules. Unexpected token '(' found at or near location 21" (see screen shots).

ObjMgrQueryLog Warning 2 000000024b85100c:0 2010-02-25 09:50:24 (query.cpp (14029)) SBL-DAT-60236: Expression does not match any Siebel query language grammar rules. Unexpected token '(' found at or near location 21.

ObjMgrLog Warning 2 000000024b85100c:0 2010-02-25 09:50:24 (query.cpp (456)) SBL-DAT-00403: The query could not be run because there is an invalid character in the field 'Name'. Please ensure that the value in the field is formatted correctly with only valid characters. Missing quotes around the search criteria or unnecessary punctuation will often cause an error.


STEPS TO REPRODUCE THE ISSUE
1. Install Siebel CRM 8.1.1.2 Fix Pack on Siebel Tools.

2. Launch Siebel Tools.

3. Create a Report object that contains a 'Sub Report' which has fields coming from a Multi Value Link. Make sure that the 'Name' property of the Multi Value Link object under the Business Component  contains parenthesis.

4. Try to 'Generate Actuate Report' using Tools menu > Utilities > Generate Actuate Report option.The generation of ROL fails with above mentioned error.

Cause

The issue has been caused due to the following:

1. The parenthesis character in the 'Name' property of a Multi Value Link are being parsed during the generation of Actuate ROL file.

2. Siebel's internal code fails to generate the ROL when the '(' character is found in the 'Name' property.

Solution

A Product Defect CR# 12-1XLAKV5 (SIEBEL TOOLS - GENERATE ACTUATE ROL FAILS WHEN REPORT FIELD USES A MULTI-VALUE FIELD) has been logged to address this issue in a future Siebel release.

WORKAROUND

The issue can be resolved by NOT using parenthesis in 'Name' property. This way it will not impact the ROL Generation.

References

BUG:12-1XLAKV5 - SIEBEL TOOLS - GENERATE ACTUATE ROL FAILS WHEN REPORT FIELD USES A MULTI-VALUE FIELD

Applies to:

Siebel Tools
Information in this document applies to any platform.
Product Release: V8 (Enterprise)
Version: 8.0 [20405] ESN Fin Svcs
Database: Microsoft SQL Server 2005
Application Server OS: Microsoft Windows 2003 Server SP2
Database Server OS: Microsoft Windows 2003 Server SP2

This document was previously published as Siebel SR 38-3461315051.
""""Checked for relevance on 03-Mar-2010""""

Symptoms

We are adjusting ours LOV after the Upgrade and we are founding a problem when activating or changing LOVs with ' in Display Value, Languange Idependent Code, etc.

Example: LOV TYpe: FINCORP_DEAL_LOAN_TYPE
for value: I don't know

Try to inactivate or activate.

I get this error:

[1] Invalid search specification '[Type] = 'FINCORP_DEAL_LOAN_TYPE' AND [Language] = 'ENU' AND (([Name] = 'I don't know' AND
[Value] <> 'I don't know') OR ([Value] = 'I don't know' AND [Name] <> 'I don't know')) AND [Id] <> '0VF-RG2D''.

Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00501)
[2] Expression does not match any Siebel query language grammar rules. Unexpected token 't' found at or near location
79.(SBL-DAT-60236)

Cause

This behavior was due to known bug

Solution

Message 1

This is a known issue please see the following item on supportweb:

Service Request #: 38-3455974081
Version: 8.0 [20405] NLD Com/Med
Abstract: Setting LOV's to Multilingual

Change request 12-1L7O0S1 has been raised to address this issue.

Message 2

The workaround suggested in the referenced service request really only applied to creating new LOV's. At this time I do not think it would be appropriate to remove all the single quotes from existing LOV records, as for referential integrity this would mean updating all existing records in the database with the new LOV values. And as you mention it would also mean changing an configuration that includes the values.

A colleague has advised that a possible workaround could be to modify the class property of the List Of Values buscomp from CSSBCListOfValues to CSSBCBase (as it is in version 7.8). I have tested this and it does seem to work but I cannot advise what could be the impact on other areas of the application. Therefore maybe as a temporary workaround you should build a special SRF where the class change had been applied and only use it for LOV admin and then leave the orginal SRF unchanged.
***Update***
The CR: 12-1L7O0S1 and other CRs were opened to have this behaviour addressed.
The parent CR: 12-1K5DYEJ “Unable to activate LOV's in Data Administration with apostrophe in the Language-Independent Code” was addressed in the 8.0.0.3 Fix Pack 

References

BUG:12-1K5DYEJ - UNABLE TO ACTIVATE LOV'S IN DATA ADMINISTRATION WITH APOSTROPHE IN THE LANGUAGE-INDEPENDENT CODE

Applies to:

Siebel Tools

Information in this document applies to any platform.
Product Release: V8 (Enterprise)
Version: 8.0 [20405] Fin Svcs
Database: Oracle 10.2.0.2
Application Server OS: Microsoft Windows 2003 Server SP2
Database Server OS: IBM AIX 5L 5.1

This document was previously published as Siebel SR 38-3485132211.

Symptoms

SBL-EXL-00145, SBL-DAT-60236
Hi,

We seem to be having issues with some of our PDQs on Service Request List View.
FYI, we have 5 applet toggles on Service Request Detail Applet meaning to say that the bottom form applet toggles based on the Service Request Type that is chosen.
We have couple of PDQs on the Service Request List View, one that returns no records and the other that returns all SRs.
But when we tend to choose any of the PDQs, we end up getting a Microsoft Internet Explorer Error throwing us out of the application.
Do note that we tried to spool but we could not get anything in the spool.
An example of the PDQ that we are trying to execute is as follows:
'Service Request'.Search = "[Id] = ""X""" 'Service Request'.Sort = ""
This example is the one that is expected to returns no records.

Please help in resolving the issue.

Thanks,
Raghu
Emailc
Mob#+61-40-750-5222 

Cause

This incorrect behavior is a product defect.

Solution

Message 1

For the benefit of other users.

The behavior that the customer experienced with the toggle applets was reproduced in version 8.x of the Siebel application. Change Request 12-1LXMIR2 has been logged for this behavior so that the product defect gets addressed in future versions of the Siebel application.
Note that product defect 12-1LXMIR2 has been addressed with Siebel 8.0.0.3.

Thank you,
Siebel Technical Support

SBL-DAT-60236: Expression does not match any Siebel query


SBL-DAT-60236: Expression does not match any Siebel query language grammar rules. Unexpected token '%1' found at or near location %2.

In this Document

Using Siebel SIA 8.0.0.5 [20420] Universal Customer Master application with third party Trillium product for real-time data quality.

When attempting to match records with fields that contain a special character in them, for example, the apostrophe, ', the following error occurs:

ERROR
-----------------------
SBL-DAT-00354: The query could not be run because the criteria for field '' contained an invalid arithmetic expression. Please ensure that the search criteria is correctly formatted.

This error is often caused by a missing operator (e.g. = or <) or missing quotes. If you aren't sure what may have caused this please contact your systems administrator.

SBL-DAT-60236: Expression does not match any Siebel query language grammar rules.

STEPS
-----------------------
By following these steps the issue can be reproduced:
1. Set up the Universal Connector for data quality matching and set client/object manager to use the appropriate type
2. Set the real-time data matching settings in Administration - Data Quality > Data Quality Settings:
3. Amend the Account Token Expression and Account Query Expression to allow you to capture a suitable number of characters from the address
4. Logout and in again for changes to take effect
5. Enter two accounts e.g. Test Account with site 1 and Test Account with site 2
6. After the second account has been saved, the deduplication popup should show the first as a match
7. Check S_DQ_ORG_KEY table to make sure that Universal Connector is being used - there should be  two records with KEY_VALUE = _____T_____
8. Now add an address to one of them and save it, e.g.
      Street Address = A Place in the Sun
      City = Redwood Shores
      State = CA
      Zip Code = 11111
      Country = USA
9. Check the S_DQ_ORG_KEY table. The key should now be '11111TA PLA'
10. Now add an address with an apostrophe (') to the other account and save it, e.g.
      Street Address = A'Place in the Sun
      City = Redwood Shores
      State = CA
      Zip Code = 11111
      Country = USA
11. Receive the following error message:

[1] Invalid search specification '[DQ System Id] = '1-AIZ3' AND [Parent Id] LIKE '1-CF1T' AND [Key Value] NOT LIKE '11111TA'PLA''.
Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00501)

[2] Expression does not match any Siebel query language grammar rules. Unexpected token 'PLA' found at or near location 90.(SBL-DAT-60236)

EXPECTED BEHAVIOR
-----------------------
The customer expects that Siebel can handle special characters when performing data matching with third party products via the Universal Connector.

Cause

The cause was determined to be a new product defect.

The following two change requests were logged for this issue:

Bug 12-1V418BZ - SBL-DAT-60236 error message when using Universal Connector with an apostrophe
Bug 12-1V9U44R - UCM dedup token generation expression is causing BDM workflow to fail in 'CDM Match' step

The first (Bug 12-1V418BZ) addresses the real-time user interface scenario and the second (Bug 12-1V9U44R) addresses the integration scenario. The cause is that neither the search specification for the 'Key' business component (e.g. Account Key, Contact Key, Prospect Key) nor the 'Dedup Token' field in the Account, Contact or List Mgmt Prospective Contact business components can handle special characters.

Solution

The problem has been fixed in the following fix packs:

- 8.0.0.9 fix pack and higher

Alternatively, if you are unable to apply 8.0.0.9 fix pack or higher, the following quick fixes were built although they may not be available for all supported languages/operating systems:

- 8.0.0.7 QF0745
- 8.0.0.2 QF02C6/8.0.0.2 QF02D2 (both are needed)

References

BUG:12-1V418BZ - SBL-DAT-60236 ERROR MESSAGE WHEN USING UNIVERSAL CONNECTOR WITH AN APOSTROPHE
BUG:12-1V9U44R - UCM DEDUP TOKEN GENERATION EXPRESSION IS CAUSING BDM WORKFLOW TO FAIL IN 'CDM MATCH' STEP
NOTE:476946.1 - How Can You Implement a Replace String Function in eScript?

Applies to:

Siebel CRM - Version: 8.0 [20405] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Whilst querying with an apostrophe in the user interface in the Name field the following errors were seen:
The query could not be run because there is an invalid character in the field 'Name'. Please ensure that the value in the field is formatted correctly with only valid characters.

Missing quotes around the search criteria or unnecessary punctuation will often cause an error.(SBL-DAT-00403). 
Normally if querying for Jack's for example, one would expect to receive an error. The normal way to accommodate such queries including special characters is to surround the query within speech marks, for example "Jack's". However this did not work either.

Cause

The issue related to some custom eScript that was being used to ensure that users populated certain fields in the user interface.

An example exhibiting the same behaviour is shown below. This was used on the Account business component.

function BusComp_PreQuery ()
{
  var sName = GetSearchSpec("Name");
}

Through testing, it was found that the only special character that would not work in the query was the apostrophe. Other characters such as the following worked fine:

; , . @ # \ | + - = [ ] & *

The same behaviour was also seen in 7.7.2.6, so it is likely widespread across the application versions.

Bug 12-1LG178H: "GetSearchSpec on field in BusComp_PreQuery Event with UI query including apostrophe causes error" was raised as a product defect to address this problem for a future product release.

Solution

The following workarounds were suggested to the customer:

1. Instead of querying for "Jack's", try querying for "'Jack''s'". e.g. double quote, single quote, Jack, single quote, single quote, s, single quote, double quote.

2. Take the GetSearchSpec method off the field and utilise it on alternative fields.

3. Use a Try-Catch-Finally statement to catch the error. More details can be found here:
- Siebel eScript Language Reference > Siebel eScript Language Overview > Siebel eScript Statements > try Statement

4. Alternatively, use the GetSearchExpr() function and do string manipulation to check that relevant fields are populated. More details of this function can be found here:
- Siebel Object Interfaces Reference > Interfaces Reference > Business Component Methods > GetSearchExpr Method

The customer decided to use an alternative instead by basically reconstructing the string and replacing the ' with an * on the PreQuery event.

Keywords: SBL-DAT-60236, SBL-DAT-00354, SBL-DAT-00501, SBL-DAT-00403


Applies to:

Siebel CTI - Version: 8.1.1 [21112] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

After upgrading to Gplus adapter to 7.5.000.51 the customer no longer received screen pops for inbound calls.

Even though all the EventHandler FilterSpec criteria were being met in the Scomm log file we would see the following:

DPATEL_37748770[07/09/2010 15:10:54:922]:DEBUG:Found no matching EventHandler

Cause


=== ODM Cause Determination ===

In the Scomm log file when the configuration was loaded we could see the following:

SADMIN_10485773[07/19/2010 12:46:07:968]:DEBUG:BuildPreProcessData begin
SADMIN_10485773[07/19/2010 12:46:07:968]:DEBUG:BuildPreProcessData end
SADMIN_10485773[07/19/2010 12:46:07:968]:DEBUG:BuildAgentCfg_New begin
SADMIN_10485773[07/19/2010 12:46:07:968]:DEBUG:GetAgentCfg end

"BuildAgentCfg_New begin" but there is no "BuildAgentCfg_New end".

Also, in the OM log file we could see the following error message:

ObjMgrQueryLog Warning 2 000000024c3f0d48:0 2010-07-15 20:56:11 (query.cpp (13952)) SBL-DAT-60236: Expression does not match any Siebel query language grammar rules. Unexpected token '{' found at or near location 59.

ObjMgrLog Warning 2 000000024c3f0d48:0 2010-07-15 20:56:11 (query.cpp (2634)) SBL-DAT-00501: Invalid search specification 'NOT [$GetCommandStatus(IsInteractionView)] = 'Enabled' and {@Phone:PhoneTypeLookup}'.

In the .def file we had the following Command defined:

[Command:MakeCallToPhone]
Description = "Make Call to "{@Phone}""
DeviceCommand = "MakeCall"
FilterSpec = "NOT [$GetCommandStatus(IsInteractionView)] = 'Enabled' and {@Phone:PhoneTypeLookup}"
Hidden = "TRUE"
OnEditControl = "TRUE"
Profile = "Gplus Voice"
CmdData = "MakeCallToPhone"

If the same change is made in a standard environment then the same behavior is seen.

The issue is caused by the {} brackets around the @Phone:PhoneTypeLookup in the Command FilterSpec

NOT [$GetCommandStatus(IsInteractionView)] = 'Enabled' and {@Phone:PhoneTypeLookup}

This behavior was deemed to be a product defect and CR# 12-1Z1L7WJ was raised for this matter.

Solution


=== ODM Solution / Action Plan ===

To solve the issue in the command MakeCallToPhone change the FilterSpec as follows:

NOT [$GetCommandStatus(IsInteractionView)] = 'Enabled' and {@Phone:PhoneTypeLookup}

It should be something like:

NOT [$GetCommandStatus(IsInteractionView)] = 'Enabled' and [@Phone:PhoneTypeLookup] IS NOT NULL



Applies to:

Siebel Tools - Version: 8.0.0.1 [20408] to 8.0.0.3 [20416] - Release: V8 to V8
Information in this document applies to any platform.
Product Release: V8 (Enterprise)
Version: 8.0 [20405] NLD Com/Med
Database: Oracle 10.2.0.3
Application Server OS: Microsoft Windows 2003 Server SP2
Database Server OS: Red Hat Linux 4.0

This document was previously published as Siebel SR 38-3455974081.

Symptoms

SBL-DAT-60236
We encountered a problem when setting all LOV entries for the COUNTRY LOV to Multilingual.
The values that contain a single quote in the displayvalue or in the Language Independent Code, can not be set to Multilingual. When you try to change anything to these records they give an error.

We now removed all single quotes from the COUNTRY LOV, so we could set them to Multilingual.

Cote D'ivoire
Korea, Democratic People's Rep
Lao People's Democratic Republ

Bahama's (NLD)

Please let us know if this is the expected behaviour.
Is there a workaround to be able to use single quote's in multilingual LOV's.

Cause

Product defect - change request 12-1K5DYEJ

Solution

The customer noticed that in Siebel 8 a validation error meesage occurs when trying to save a List of Values (LOV) record that contains an apostrophe (single quote) character in either the Display Value or Language Independent Code field.

The error encountered on trying to saving the LOV record in the LOV administration screen was:

Invalid search specification '[Type] = 'AAG_ACCOUNT_TYPE' AND [Language] = 'ENU' AND (([Name] = 'Banking'' AND [Value] <> 'Banking' OR ([Value] = 'Banking' AND [Name] <> 'Banking'')) AND [Id] <> 'OVF-1L699"

Expression does not match any Siebel query language grammar rules. Unexpected token 'Banking' found at or near location 93. SBL-DAT-60236

This error occurs due to the second quote character appearing in the search specification expression that was generated by Siebel 8 as part of new validation logic. For example [Name] = 'Banking''

In previous versions of Siebel it was possible to enter and store LOV records that including the single quote character.

Issue was addressed by change request 12-1K5DYEJ which was fixed in Siebel 8.0.0.3 Fix Pack and is not present in Siebel 8.1.

The only workaround is to not enter single quote characters in to either the Display Value or LIC field of LOV records.

Keywords: WriteRecord; Write; Record; LOV; List; Values; Display; Value; Language; Independent; Code; Validate; search; spec; specification; quote; apostrophe.

Applies to:

Siebel Tools - Version: 8.1.1.1 [21211] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Goal


When doing a full compile, I end up with an SRF that is smaller than it should be and is not usable by the server or client. I am connected directly to the server database. This problem is intermittent - sometimes it produces a usable SRF, sometimes it doesn't - with no changes to anything.
This intermittent behavior is happening on a Windows 2003 PC.


Solution


This incorrect behavior was happening for one Siebel Tools client on a windows 2003 box.

Siebel client side logging was enabled for the Siebel Tools client using the Siebel_Log_Events environment variable.  The client side logging for Siebel Tools generated a siebdev.log file with the following types of errors.

ObjMgrQueryLog Warning 2 000000024c400300:0 2010-07-16 13:06:32 (query.cpp (13952)) SBL-DAT-60236: Expression does not match any Siebel query language grammar rules. Unexpected token '(' found at or near location 21.

ObjMgrLog Warning 2 000000024c400300:0 2010-07-16 13:06:32 (query.cpp (456)) SBL-DAT-00403: The query could not be run because there is an invalid character in the field 'Name'. Please ensure that the value in the field is formatted correctly with only valid characters.

After reviewing the Siebel Tools installation and environment, it was determined that the operating system of windows 2003 is not a supported operating system for the Siebel Developer Client per the
Siebel System Requirements and Supported Platforms documentation.

See the Siebel System Requirements and Supported Platforms > Client Environment Requirements >
Requirements for Employee Applications
Software Requirements for the Siebel Developer Web Client

But, it is not very clear that Employee Applications would include Siebel Tools.

Therefore a documentation defect was raised to address this unclear documentation.

Siebel Tools Product Management confirmed that the following operating systems are the supported platform for Tools/Dclient as per Siebel System Requirements and Supported Platforms documentation.

WinXP

Win7

Vista

Win2000

Note that Win2003 and Win2008 are not supported clients for Tools/Dedicated client.

Change Request CR 12-1Z9S19D is a documentation defect noting that the
System Required and Supported Platforms should be much clearer for Siebel Tools

SUMMARY
The system platforms discusses the environment requirements for Employee applications.
But it is not obvious that Siebel Tools is considered an Employee Application like a Siebel thin client running Siebel Call Center.

Siebel Tools is a considered a different application than a Siebel client application.

DESIRED DOCUMENTATION
The documentation should have a separate listing for Siebel Tools clients.

Siebel
System Requirements and Supported Platforms > Client Environment
Requirements >

Requirements for Employee Applications

Add a separate section for Siebel Tools.

Siebel System Requirements and Supported Platforms > Client
Environment Requirements >

Requirements for Siebel Tools

The recommendation was given to use a different PC with a supported platform for the Siebel Tools client.

Oracle Siebel Support

References

BUG:12-1Z9S19D - SYSTEM REQ SUPPORTED PLATFORMS SHOULD BE MUCH CLEARER FOR SIEBEL TOOLS

Applies to:

Siebel Reports - Version: 8.1.1 [21112] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms


Siebel Tools displays an error when generating Actuate Reports that include fields associated with Multivalue Links that have brackets in their names. The following error message appears:

The query could not be run because there is an invalid character in the field 'Name'. Please ensure that the value in the field is formatted correctly with only valid characters. Missing quotes around the search criteria or unnecessary punctuation will ofthen cause an error." "Expression does not match any Siebel query language grammar rules. Unexpected token '(' found at or near location 21" (see screen shots).

ObjMgrQueryLog Warning 2 000000024b85100c:0 2010-02-25 09:50:24 (query.cpp (14029)) SBL-DAT-60236: Expression does not match any Siebel query language grammar rules. Unexpected token '(' found at or near location 21.

ObjMgrLog Warning 2 000000024b85100c:0 2010-02-25 09:50:24 (query.cpp (456)) SBL-DAT-00403: The query could not be run because there is an invalid character in the field 'Name'. Please ensure that the value in the field is formatted correctly with only valid characters. Missing quotes around the search criteria or unnecessary punctuation will often cause an error.


STEPS TO REPRODUCE THE ISSUE
1. Install Siebel CRM 8.1.1.2 Fix Pack on Siebel Tools.

2. Launch Siebel Tools.

3. Create a Report object that contains a 'Sub Report' which has fields coming from a Multi Value Link. Make sure that the 'Name' property of the Multi Value Link object under the Business Component  contains parenthesis.

4. Try to 'Generate Actuate Report' using Tools menu > Utilities > Generate Actuate Report option.The generation of ROL fails with above mentioned error.

Cause

The issue has been caused due to the following:

1. The parenthesis character in the 'Name' property of a Multi Value Link are being parsed during the generation of Actuate ROL file.

2. Siebel's internal code fails to generate the ROL when the '(' character is found in the 'Name' property.

Solution

A Product Defect CR# 12-1XLAKV5 (SIEBEL TOOLS - GENERATE ACTUATE ROL FAILS WHEN REPORT FIELD USES A MULTI-VALUE FIELD) has been logged to address this issue in a future Siebel release.

WORKAROUND

The issue can be resolved by NOT using parenthesis in 'Name' property. This way it will not impact the ROL Generation.

References

BUG:12-1XLAKV5 - SIEBEL TOOLS - GENERATE ACTUATE ROL FAILS WHEN REPORT FIELD USES A MULTI-VALUE FIELD

Applies to:

Siebel Tools
Information in this document applies to any platform.
Product Release: V8 (Enterprise)
Version: 8.0 [20405] ESN Fin Svcs
Database: Microsoft SQL Server 2005
Application Server OS: Microsoft Windows 2003 Server SP2
Database Server OS: Microsoft Windows 2003 Server SP2

This document was previously published as Siebel SR 38-3461315051.
""""Checked for relevance on 03-Mar-2010""""

Symptoms

We are adjusting ours LOV after the Upgrade and we are founding a problem when activating or changing LOVs with ' in Display Value, Languange Idependent Code, etc.

Example: LOV TYpe: FINCORP_DEAL_LOAN_TYPE
for value: I don't know

Try to inactivate or activate.

I get this error:

[1] Invalid search specification '[Type] = 'FINCORP_DEAL_LOAN_TYPE' AND [Language] = 'ENU' AND (([Name] = 'I don't know' AND
[Value] <> 'I don't know') OR ([Value] = 'I don't know' AND [Name] <> 'I don't know')) AND [Id] <> '0VF-RG2D''.

Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00501)
[2] Expression does not match any Siebel query language grammar rules. Unexpected token 't' found at or near location
79.(SBL-DAT-60236)

Cause

This behavior was due to known bug

Solution

Message 1

This is a known issue please see the following item on supportweb:

Service Request #: 38-3455974081
Version: 8.0 [20405] NLD Com/Med
Abstract: Setting LOV's to Multilingual

Change request 12-1L7O0S1 has been raised to address this issue.

Message 2

The workaround suggested in the referenced service request really only applied to creating new LOV's. At this time I do not think it would be appropriate to remove all the single quotes from existing LOV records, as for referential integrity this would mean updating all existing records in the database with the new LOV values. And as you mention it would also mean changing an configuration that includes the values.

A colleague has advised that a possible workaround could be to modify the class property of the List Of Values buscomp from CSSBCListOfValues to CSSBCBase (as it is in version 7.8). I have tested this and it does seem to work but I cannot advise what could be the impact on other areas of the application. Therefore maybe as a temporary workaround you should build a special SRF where the class change had been applied and only use it for LOV admin and then leave the orginal SRF unchanged.
***Update***
The CR: 12-1L7O0S1 and other CRs were opened to have this behaviour addressed.
The parent CR: 12-1K5DYEJ “Unable to activate LOV's in Data Administration with apostrophe in the Language-Independent Code” was addressed in the 8.0.0.3 Fix Pack

References

BUG:12-1K5DYEJ - UNABLE TO ACTIVATE LOV'S IN DATA ADMINISTRATION WITH APOSTROPHE IN THE LANGUAGE-INDEPENDENT CODE

Applies to:

Siebel Tools

Information in this document applies to any platform.
Product Release: V8 (Enterprise)
Version: 8.0 [20405] Fin Svcs
Database: Oracle 10.2.0.2
Application Server OS: Microsoft Windows 2003 Server SP2
Database Server OS: IBM AIX 5L 5.1

This document was previously published as Siebel SR 38-3485132211.

Symptoms

SBL-EXL-00145, SBL-DAT-60236Hi,

We seem to be having issues with some of our PDQs on Service Request List View.
FYI, we have 5 applet toggles on Service Request Detail Applet meaning to say that the bottom form applet toggles based on the Service Request Type that is chosen.
We have couple of PDQs on the Service Request List View, one that returns no records and the other that returns all SRs.
But when we tend to choose any of the PDQs, we end up getting a Microsoft Internet Explorer Error throwing us out of the application.
Do note that we tried to spool but we could not get anything in the spool.
An example of the PDQ that we are trying to execute is as follows:
'Service Request'.Search = "[Id] = ""X""" 'Service Request'.Sort = ""
This example is the one that is expected to returns no records.

Please help in resolving the issue.

Thanks,
Raghu
Emailc
Mob#+61-40-750-5222

Cause

This incorrect behavior is a product defect.

Solution

Message 1

For the benefit of other users.

The behavior that the customer experienced with the toggle applets was reproduced in version 8.x of the Siebel application. Change Request 12-1LXMIR2 has been logged for this behavior so that the product defect gets addressed in future versions of the Siebel application.
Note that product defect 12-1LXMIR2 has been addressed with Siebel 8.0.0.3.

Thank you,
Siebel Technical Support