SBL-DAT-00385: Multiple definitions exist for business component '%1'. Please ask your systems administrator to check your application configuration.

Date:

Applies to:

Siebel Tools - Version: 7.7.1 [18306] to 8.1.1.2 - Release: V7 to V8
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.7.1 [18306]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Sun Solaris 2.8

This document was previously published as Siebel SR 38-1380480982.
***Checked for relevance on 06-May-2010***

Symptoms

SBL-DAT-00385, SBL-DAT-00509

We are upgrading our Dev environment from 6.2.1.30 to 7.7.1. After completing all the Post Upgrade tasks, we compiled a custom SRF and tried logging using dedicated client. On some of the screens we seem to run into the following error message (screen shot attached):

Definition for table '' does not exist.(SBL-DAT-00509)

The siebel.log file shows errors about multiple definitions for various Business Comps such as:

ObjMgrSRFLog Error 1 0 2004-07-07 14:14:17 (objdef.cpp (559)) SBL-DAT-00385: Multiple definitions exist for business component 'Contact - Sales Rep - VisMvgSqlBCDef'.

siebel.log file is also attached. We have searched the Bookshelf and Support Web but did not find anything that would be helpful. Please review the files and let us know how to proceed further. Thanks.

Cause

Originally thought to be a product defect after this behaviour was reviewed by Siebel Engineering it was established that this was not the case

Solution


For the benefit of other readers:

After further research it has been determined that this error can be caused by an inactive business component referred to by one or more multi value links. The business component may have been manually inactivated or automatically inactivated by the upgrade process due to the fact it has now been made obsolete.

Run the Tools validate on the business components indicated in the error message to help you identify the links that need to be fixed.

Change Request 12-PKC6CT had been raised with Siebel Engineering to address this behaviour as a product defect but was reviewed and it was established that this was not the case

There is no error in the upgrade. If a business component is inactive by Siebel, it will be inactive after an upgrade. That's expected behavior for upgrade. If the inactive business component causes other objects(referring to the business component) to be invalid due to this inactive, a developer need to correct them during post merge. This is true for other object types too besides business components


Applies to:

Siebel Tools - Version: 7.7.1 [18306] - Release: V7
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.7.1 [18306] DEU
Database: IBM DB2 8.1 FixPack 3
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server

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

Symptoms

SBL-DAT-00556, SBL-DAT-00546, SBL-DAT-00560

Follow-up from SR 38-1453099441

1. Starting Siebel via web client fails. Please see the attached log-files for error messages.
(For translation see Siebel Error Messages > Siebel 7.7).
SBL-DAT-00560, SBL-DAT-00556, SBL-DAT-00546, SBL-SVC-00208, SBL-DAT-00385

2. Doing a full compile on the extracted local developer database fails:

Displayed error messages:
An error message has occured executing a Sql statement.
Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DBC-00105)

Internal database error *** ERROR *** Assertion failed: 102300 (8.0.2.4361)
File associated with given page id is invalid or not open -- transaction rolled back

According to SR 38-1371657223 we regenerate db template, extracted db again, initialize it, perform a full get but the error still remains.

Compiling a new SRF connected to the server succeded.

3. The error messages described in the attached log files do not appear using a standard SRF.
We are able to connect successfully via Web Client.

4. We are able to connect successfully using the Siebel Dedicated Web Client. The same error messages are logged in local siebel.log while using compiled new SRF.

5. We renamed the Siebel_Server/bin/diccache.dat, but errors still remain.

Thank you for your quick response.

Henrik

Cause

The cause for the assertion failed error message sometimes occurs when the local db needs to allocate temporary files and does not have enough space.

Solution

Message 1

DESCRIPTION:

Tools stops during full compile on local db.

SYMPTOMS:

Doing a full compile on the extracted local developer database fails:

Displayed error messages:
An error message has occured executing a Sql statement.
Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DBC-00105)

Internal database error *** ERROR *** Assertion failed: 102300 (8.0.2.4361)
File associated with given page id is invalid or not open -- transaction rolled back

When using the unfinished srf file the following errors are shown in the client log file:

SBL-DAT-00560
SBL-DAT-00556
SBL-DAT-00546
SBL-SVC-00208
SBL-DAT-00385

SOLUTION:

The assertion failed error message sometimes occurs when the local db needs to allocate temporary files. This files are usual stored in the path of the TEMP system variable which usual points to C:\temp. As the temporary files can grow up to 500 MB the C hard disk sometimes has no free space for the temporary files.

In this case the issue has been resolved by deleting the TEMP system variable and recreating it new.


Siebel Technical Support


Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3 [16157] DEU Fin Svcs
Database: IBM DB2/UDB 8.1 FixPack 1S
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: Microsoft Windows 2000 Advanced Server SP 3

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

Symptoms

SBL-DAT-00385, SBL-DAT-00398, SBL-DAT-00462

Hi, after setting up all developer environments and doing a full get/full compile without any problems, we are now experiencing problems with the check-in/check-out routines.
Whatever project we are trying to check out, the error message reads as follows:
"You have attempted to denormalize calculated field 'Done Flag' in business component 'Action' into column 'DONE_FLG'. Donormalized calculations are not allowed (SBL-DAT-00462)"

I then went ahead with Tools, connected to the Server and checked the properties of this field. It was in fact not correctly defined, as it had a column property attached to it. I then removed this property, so that it was a calculated field (the flag and the calculation expression set as it used to be in our V6 environment). Did another full compile server based, which completed without errors.

When trying to check-out projects after this modification, we are running into the same error message again. After this first error message, we are getting another one which points to a field called 'Audit Flag', which sits on a custom extension to S_EVT_ACT, claiming it to be defined twice (which, of course, is not correct).

Other symptoms, which we think are related to this problem are the unability to create sif-files locally.
Please advise, how we can fix this.
Kind regards,

Solution

Message 1

DESCRIPTION:

Problems during Check-Out of Siebel Projects

SYMPTOMS:

Whatever project we are trying to check out, the error message reads as follows:
"You have attempted to denormalize calculated field 'Done Flag' in business component 'Action' into column 'DONE_FLG'. Donormalized calculations are not allowed (SBL-DAT-00462)"


SOLUTION:

The properties of the directories where Siebel was installed have been checked and it turned out, that the user didn't had the right permissions to write files to that directory (write protection on the windows directories). After resetting these, the user could check in /out and create sif-files without any error messages.

Thank you
Siebel Technical Support

SBL-DAT-00254: The username you have entered is invalid. Please try to log on again or contact your system administrator for assistance.

Date:

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.4 [16180]
Database: Oracle 9.2.0.4
Application Server OS: HP-UX 11i
Database Server OS: HP-UX 11i

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

Symptoms

SBL-DAT-00254, SBL-DAT-00369

After installing the Siebel Industry Applications Sample Database the user accounts noted in the Siebel Release notes do not work for Siebel Communications, Media, and Energy.

eg. CCORWIN, PCARR, etc.

Only the sadmin account works. Other verticals seem to work fine.

Solution

Message 1

For the benefit of other readers:

The Customer was attempting to use the Siebel Version 7.5.3.4 SIA (Industry Apps - Comms / Media / Energy) client Application with Sample Database System which worked fine with 'SADMIN / SADMIN' User_ID and Password. However, when the Customer used these User_ID Login's "CCORWIN or PCARR" - then they would be presented with this error message instead : "The User ID or Password is not recognised"

This was similar error behavior to Service Request Number 38-1038794181 available out on SupportWeb. However, the workaround solution presented in this SR did not work as expected and this error message was presented instead :

"An Internal Error with the Connector DLL '<?>' has occurred, preventing one of the following export functions from being loaded: _SSACreateSqlObj@12 or SSASQLObjLogon@24. Please verify that the correct version of the runtime client specific to your database platform is installed on the machine where your Siebel Server is running. If this problem still persists, please verify that the Database Connectivity Settings are correct ? (SBL-DAT-00369)"

"The User Name you have entered is invalid or your user position is not defined. Please try and logon again or contact your systems adminstrator for assistance. (SBL-DAT-00254)"

Following on from my research and testing, I discovered that these User_ID's 'CCORWIN and PCARR' have been marked as inactive and are no longer required for the Siebel Version 7.5.3.x release.

Message 2

Continued...

The workaround solution this time was to use the other Login User_ID's such as TBALL (Tom Ball) or WBECKER (William Becker).

I have raised Product Defect Change Request Number 12-JZ7A1Z to have this new matter addressed.

Keywords: Siebel 7.5.3.x, CME - Comms / Media / Energy, User_ID, Login, Password, Sample, Database, System, Connector, DLL, SBL-DAT-00369, SBL-DAT-00254


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.

References

NOTE:551663.1 - Error loading dictionary file diccache.dat.(SBL-DAT-60237) when running KEYDBMGR

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.

References

NOTE:551663.1 - Error loading dictionary file diccache.dat.(SBL-DAT-60237) when running KEYDBMGR

SBL-DAT-00546: The user-context could not be established. Something is wrong with the assigned primary position or login related repository objects.

Date:

Applies to:

Siebel CRM - Version: 8.0.0.3 [20416] and later   [Release: V8 and later ]
Siebel System Software - Version: 8.0.0.3 [20416] and later    [Release: V8 and later]
Information in this document applies to any platform.
***Checked for relevance on 07-SEP-2010***

Symptoms


Customer was unable to run Siebel server service. 

They got the following error in SvrTblCleanup log:
ObjMgrLog Error 1 0000000449ae0760:0 2009-03-04 21:22:58 (oracon.cpp (3165)) SBL-DBC-00108: An error has occurred preparing a Sql statement.

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

ObjMgrSessionLog Error 1 0000000449ae0760:0 2009-03-04 21:22:58 (dmsessionusercontext.cpp (1163)) SBL-DAT-00552: An error occurred querying a SQL object for user information. See additional error messages for more information.

ObjMgrSessionLog Error 1 0000000449ae0760:0 2009-03-04 21:22:58 (dmsessionusercontext.cpp (640)) SBL-DAT-00546: 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.

Cause


Based on the error reported "Something is wrong with the assigned primary position or login related repository objects", it is suspected that the siebel application user (default SADMIN)  for this SrvrTblCleanup and other components may not have a position assigned or does not have responsibility "Siebel Administrator". Suggested customer to verify and restart the server.

Solution



Customer later found out that they were moving tables from the default tablespace to other tablespace as per their production setup, resulting in several table grants missing.

Restoring the table grants resolved the issue.

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.

References

NOTE:551663.1 - Error loading dictionary file diccache.dat.(SBL-DAT-60237) when running KEYDBMGR

Applies to:

Siebel Tools - Version: 7.7.1 [18306] - Release: V7
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.7.1 [18306] DEU
Database: IBM DB2 8.1 FixPack 3
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server

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

Symptoms

SBL-DAT-00556, SBL-DAT-00546, SBL-DAT-00560

Follow-up from SR 38-1453099441

1. Starting Siebel via web client fails. Please see the attached log-files for error messages.
(For translation see Siebel Error Messages > Siebel 7.7).
SBL-DAT-00560, SBL-DAT-00556, SBL-DAT-00546, SBL-SVC-00208, SBL-DAT-00385

2. Doing a full compile on the extracted local developer database fails:

Displayed error messages:
An error message has occured executing a Sql statement.
Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DBC-00105)

Internal database error *** ERROR *** Assertion failed: 102300 (8.0.2.4361)
File associated with given page id is invalid or not open -- transaction rolled back

According to SR 38-1371657223 we regenerate db template, extracted db again, initialize it, perform a full get but the error still remains.

Compiling a new SRF connected to the server succeded.

3. The error messages described in the attached log files do not appear using a standard SRF.
We are able to connect successfully via Web Client.

4. We are able to connect successfully using the Siebel Dedicated Web Client. The same error messages are logged in local siebel.log while using compiled new SRF.

5. We renamed the Siebel_Server/bin/diccache.dat, but errors still remain.

Thank you for your quick response.

Henrik

Cause

The cause for the assertion failed error message sometimes occurs when the local db needs to allocate temporary files and does not have enough space.

Solution

Message 1

DESCRIPTION:

Tools stops during full compile on local db.

SYMPTOMS:

Doing a full compile on the extracted local developer database fails:

Displayed error messages:
An error message has occured executing a Sql statement.
Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DBC-00105)

Internal database error *** ERROR *** Assertion failed: 102300 (8.0.2.4361)
File associated with given page id is invalid or not open -- transaction rolled back

When using the unfinished srf file the following errors are shown in the client log file:

SBL-DAT-00560
SBL-DAT-00556
SBL-DAT-00546
SBL-SVC-00208
SBL-DAT-00385

SOLUTION:

The assertion failed error message sometimes occurs when the local db needs to allocate temporary files. This files are usual stored in the path of the TEMP system variable which usual points to C:\temp. As the temporary files can grow up to 500 MB the C hard disk sometimes has no free space for the temporary files.

In this case the issue has been resolved by deleting the TEMP system variable and recreating it new.


Siebel Technical Support


Applies to:

Siebel Reports - Version: 7.7.2.6 SIA [18372] - Release: V7
Sun Solaris SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.7.2.6 [18372] Pub Sect
Database: Oracle 10.1.0.5
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 9

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

Symptoms

Between 20:00 and 20:52 our Actuate reports failed with the following error message

Starting...                            
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)
User error.                            
Status No: 1                            
Basic Error: 1000                        
Module: ssReport%BuildReport                    
Line: 111                            
User error.                            

The Object Managers were available during this time. Do you have any information on what could have caused this error.

Thanks

Cause

No access to data when executing a report

Solution

Message 1

Issue Description: Between 20:00 and 20:52 Actuate reports failed with the following error message

Starting...                            
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)
User error.                            
Status No: 1                            
Basic Error: 1000                        
Module: ssReport%BuildReport                    
Line: 111                            
User error.                            

The Object Managers were available during this time.


Resolution:

There was a problem with the SAN database storage at that time which caused the reports fail.

Also make sure that the SSE_ROLE is granted to the users as described in the Siebel Installation Guide.

Thanks and Regards
Oracle|Siebel Technical Support


Applies to:

Siebel Tools - Version: 8.0.0.5 [20420] - Release: V8
Information in this document applies to any platform.

Symptoms


Comments
--------
On : 8.0.0.5 [20420] version, Configuration - Dev Env

When attempting to log in as utkumar[devadmin_mktg], the following error occurs:

"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)"

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Login to Siebel Tools using utkumar[devadmin_mktg]

Note that customer is able to Login to Siebel Tools using utkumar as login and also using devadmin_mktg as login but not as utkumar[devadmin_mktg] which is the Data Proxy Authentication.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, user cannot login to Siebel Tools.

Cause


Comments
--------
Database Proxy Authentication is not supported for Siebel Tools.

Comments
--------
According to documentation there must be a userid as the same as Database Account.

Also according to following documentation:
"Siebel Security Guide Version 8.0" > Chapter 6, Security Adapter Authentication > Configuring Database Authentication:

If you do not use LDAP/ADSI authentication, then you must create a unique database account for each user. When an administrator adds a new user to the database, the User ID field must match the username for a database account. The user enters the database username and password when the user logs into a Siebel application.

Solution


Comments
--------
Enhancement Request #12-1VM84TB has been logged requesting support to use Siebel Tools with Database Proxy Authentication it is currently target for future version.

Oracle Customer Support

References

BUG:12-1VM84TB - CANNOT LOGIN TO SIEBEL TOOLS USING DATABASE PROXY AUTHENTICATION

Siebel CRM Master Error Catalog (Part 1): Fixing Data Layer & Database Access Errors (SBL-DAT-00144, SBL-DAT-00398, SBL-DAT-00500)

Date:

Part 1: Data Layer & Database Access Errors (SBL-DAT-*)

Enterprise Architecture Troubleshooting: Resolving Business Component Instantiation Failures, Unique Constraint Violations, Row-Level Locking Deadlocks, SQL Query Parsing Faults, and Mandatory Field Constraints.

SBL-DAT-00144: Could not find Business Component '%1' OBJECT INSTANTIATION
Root Cause Analysis
An SBL-DAT-00144 occurs when the Siebel Data Engine attempts to instantiate a Business Component (BC) within a Business Object (BO) context where that BC is either not registered in the repository, misspelled in eScript, or missing from the active Business Object layout. This frequently happens when custom eScript code uses Bo.GetBusComp("BC Name") without verifying that the link exists in Siebel Tools / Web Tools.
Diagnostic Object Execution Lifecycle
[eScript / Workflow] ---> Invoke Bo.GetBusComp("Custom BC") | v [Inspect BO Repository Definition] | +----------------------+----------------------+ | | [BusComp Belongs to BO?] [BusComp NOT Linked to BO] | | Instantiate C++ Pointer Throw SBL-DAT-00144 Error & Return BC Instance (Null Pointer Exception in eScript)
Tailored Environment Fixes
Fix A: Defensive eScript Instantiation & BO Verification

Issue: Scripts break during runtime when retrieving unlinked Business Components from a generic Business Object instance.

  1. Verify the exact casing and repository spelling of the target Business Component in Web Tools.
  2. In eScript, ensure the BC is instantiated via the correct Business Object or use TheApplication().GetBusObject() defensively.
  3. Explicitly destroy object references in finally blocks to prevent orphan memory handles.
// Defensive eScript Pattern for Business Object / BusComp Handling var boAccount = null; var bcContact = null; try { boAccount = TheApplication().GetBusObject("Account"); // Ensure "Contact" is explicitly defined under the "Account" BO in Web Tools bcContact = boAccount.GetBusComp("Contact"); with (bcContact) { SetViewMode(AllView); ClearToQuery(); SetSearchSpec("Account Id", sAccountId); ExecuteQuery(ForwardOnly); } } catch (e) { TheApplication().RaiseErrorText("SBL-DAT-00144 Prevented: " + e.toString()); } finally { bcContact = null; boAccount = null; // Prevent eScript memory leakage }
Fix B: Repository Compiled SRF / Workspace Migration Check

Issue: The BC is present in Web Tools but fails in runtime environments post-deployment due to an incomplete workspace publish.

  1. Query the Siebel Repository table directly via SQL to verify if the BO-to-BC link exists in the active workspace.
  2. Publish and deliver the workspace or compile an updated SRF depending on your Siebel version (IP17+ vs legacy).
-- SQL Query to Check BO to BC Bus Object Component Mapping SELECT bo.NAME AS BO_NAME, boc.BUSCOMP_NAME AS BC_NAME FROM S_BUSOBJ bo JOIN S_BUSOBJ_COMP boc ON bo.ROW_ID = boc.BUSOBJ_ID WHERE bo.NAME = 'Account' AND boc.BUSCOMP_NAME = 'Your_Custom_BusComp';
SBL-DAT-00398: Could not insert record into database UNIQUE CONSTRAINT / ORA-00001
Root Cause Analysis
An SBL-DAT-00398 indicates that an InsertRecord() or WriteRecord() operation was rejected by the underlying database management system (RDBMS). This is almost always caused by a unique index violation on the base table (e.g., Oracle ORA-00001, MS SQL Server 2627), a corrupt system sequence (S_SEQUENCE), or duplicate ROW_ID generation in high-concurrency batch updates.
Database Insertion Flow & Sequence Generation
[eScript / User Action] ---> WriteRecord() | v [Siebel Data Layer Requests ROW_ID] | [Fetches Prefix + Base36 S_SEQUENCE Value] | v [Generates Insert SQL Statement] | [Executes SQL against RDBMS] | +-------------------+-------------------+ | | (Database Insert OK) (Unique Index Violation) | | Commit Transaction Return SBL-DAT-00398 + ORA-00001 in Siebel Log
Tailored Environment Fixes
Fix A: Identify & Resolve RDBMS Unique Index Collisions

Issue: Custom user keys or system fields collide with pre-existing records on target base tables (e.g., S_PARTY, S_ORG_EXT).

  1. Open the active component log file (e.g., CallCenterObjMgr_enu_*.log) and locate the exact SQL statement failing prior to SBL-DAT-00398.
  2. Run the SQL statement in an SQL client to identify the exact constraint name being violated.
  3. Ensure search specs verify record non-existence before executing NewRecord().
// Defensive Upsert Logic in eScript to Prevent Insertion Collisions bcAcc.ClearToQuery(); bcAcc.SetSearchSpec("Main Phone Number", sPhone); bcAcc.ExecuteQuery(ForwardOnly); if (bcAcc.FirstRecord()) { // Record exists: Perform Update instead of Insert bcAcc.SetFieldValue("Name", sNewName); bcAcc.WriteRecord(); } else { // Safe to Insert bcAcc.NewRecord(NewAfter); bcAcc.SetFieldValue("Main Phone Number", sPhone); bcAcc.SetFieldValue("Name", sNewName); bcAcc.WriteRecord(); }
Fix B: Resynchronize `S_SEQUENCE` for Corrupted Row IDs

Issue: Parallel EIM loads or direct database inserts skipped the sequence counter, causing Siebel to generate duplicate `ROW_ID` values.

  1. Identify the affected table's sequence prefix from the DB log.
  2. Execute the `S_SEQUENCE` adjustment script to bump the generator counter past the highest existing ID.
-- Adjust S_SEQUENCE Counter for a Target Table (Oracle Syntax) UPDATE S_SEQUENCE SET SQ_VAL = (SELECT MAX(TO_NUMBER(SUBSTR(ROW_ID, 3))) + 100 FROM S_ORG_EXT WHERE ROW_ID LIKE '1-%') WHERE TBL_NAME = 'S_ORG_EXT'; COMMIT;
SBL-DAT-00500: An error has occurred writing to record LOCKING CONTENTION / ORA-00054
Root Cause Analysis
An SBL-DAT-00500 error occurs during a database write operation when the targeted database record is locked by another concurrent session, thread, or asynchronous background job (such as Assignment Manager or Workflow Process Manager). In Oracle databases, this manifests as ORA-00054: resource busy and acquire with NOWAIT specified or ORA-00060: deadlock detected.
Row-Locking Contention Flow
[User Session A] ---> SELECT ... FOR UPDATE (Locks Row 1-ABC) | [User Session B] ---> Tries to Write to Row 1-ABC | [RDBMS NOWAIT Timer Expires] | Throws ORA-00054 / ORA-00060 | Siebel Data Layer Catches & Wraps Return SBL-DAT-00500 to User UI
Tailored Environment Fixes
Fix A: Optimizing eScript Lock Duration & Transaction Scope

Issue: Scripts hold explicit locks on records during slow external web service calls or loops.

  1. Never perform external web service calls (EAI HTTP Endpoints) while holding an active record in edit mode.
  2. Query, modify, and call WriteRecord() immediately to release row-level DB locks.
// Anti-Pattern (Causes SBL-DAT-00500): // bc.SetFieldValue(...); // callSlowWebService(); // <-- Holds DB row lock during network IO! // bc.WriteRecord(); // Correct Pattern: var sResponse = callSlowWebService(); // Execute IO outside of DB transaction bc.ClearToQuery(); bc.SetSearchSpec("Id", sRecId); bc.ExecuteQuery(ForwardOnly); if (bc.FirstRecord()) { bc.SetFieldValue("Integration Status", sResponse); bc.WriteRecord(); // Lock held for only milliseconds }
Fix B: Parameter Tuning via `srvrmgr` for Row Lock Retry

Issue: High-concurrency object managers drop operations immediately instead of retrying transient row locks.

  1. Connect to `srvrmgr` CLI and configure database retry options for your Application Object Manager.
// Enable DB Lock Retry Parameters in srvrmgr srvrmgr> change param DBLockTimeout=30 for comp CallCenterObjMgr_enu srvrmgr> change param DBRetryCount=3 for comp CallCenterObjMgr_enu
SBL-DAT-00215: Invalid Search Specification QUERY SYNTAX FAULT
Root Cause Analysis
An SBL-DAT-00215 error is raised when a search specification string passed to SetSearchSpec(), SetNamedSearch(), or configured on an Applet / BC repository property contains invalid expression syntax, unescaped single quotes, mismatched brackets, or references non-existent BC field names.
Tailored Environment Fixes
Fix A: Escaping Quotation Marks and Dynamic Values in eScript

Issue: String variables containing apostrophes (e.g., "O'Connor") break Siebel Query Language parsing.

  1. Sanitize string variables using double-single quotes (`''`) before appending them to search specs.
  2. Ensure field names inside search spec strings match exact BC field names, not base table column names.
// Helper Function to Sanitize Search Specs in eScript function SafeSearchSpec(sValue) { if (sValue == null) return ""; return sValue.replace(/'/g, "''"); // Replace ' with '' } // Example Usage var sLastName = "O'Connor"; bcContact.ClearToQuery(); // Correct: Escaped quote evaluates to [Last Name] = 'O''Connor' bcContact.SetSearchSpec("Last Name", "'" + SafeSearchSpec(sLastName) + "'"); bcContact.ExecuteQuery(ForwardOnly);
SBL-DAT-00401: Field '%1' is required MANDATORY VALIDATION
Root Cause Analysis
An SBL-DAT-00401 error is triggered when WriteRecord() is invoked on a Business Component, but one or more fields marked as **Required = TRUE** in Web Tools (or enforced via User Properties / Table Column constraints) contain null or blank values.
Tailored Environment Fixes
Fix A: Pre-Write Record Validation in eScript

Issue: Programmatic inserts omit required fields, interrupting automated background interfaces.

  1. In script or workflow data transformations, validate that all mandatory fields contain non-null values prior to committing.
  2. Check the Business Component Field User Properties (e.g., Required, Required If) for conditional mandatory rules.
// Ensure Mandatory Fields are Populated Before WriteRecord bcOppty.NewRecord(NewAfter); // Validate mandatory fields var sName = "Enterprise Cloud Upgrade"; var sSalesStage = "1-Qualification"; if (sName && sSalesStage) { bcOppty.SetFieldValue("Name", sName); bcOppty.SetFieldValue("Sales Stage", sSalesStage); bcOppty.WriteRecord(); } else { TheApplication().RaiseErrorText("SBL-DAT-00401 Guard: Mandatory fields (Name, Sales Stage) must not be null."); }

SBL-DAT-00170: The DLL '%1'

Date:

Applies to:

Siebel System Software - Version: 8.0.0.3 [20416] - Release: V8
IBM AIX5L Based Systems (32-bit)

Symptoms


"The DLL 'sscsoabc.dll' could not be loaded.(SBL-DAT-00170)" accessing the product administration view.

Cause


A non-supported release of the C++ runtime library is in use for the Siebel server running the IBM AIX 5.3 OS.

Solution


Please verify the AIX OS release for the machines where the Siebel components are running.

Similar occurrances of the reported error ("The DLL 'sscsoabc.dll' could not be loaded.(SBL-DAT-00170)") could be addressed upgrading the OS for the Siebel server to AIX 5.3 ML03 (or higher). Please refer to the System Requirements and Supported Platforms, Version 8.0 for details about the supported OS level for Siebel version 8.0.

For Siebel version 8.0, please also check that the required C++ Runtime version 7.0.0.1 or above is in use on the AIX box where the Siebel server for the affected object manager is running. This can be verified reviewing the output of the following command executed on the Siebel server machine running on IBM AIX 5.3:

lslpp -hc | grep xlC


Applies to:

Siebel CRM - Version: 7.7.1 SIA [18306] and later    [Release: V7 and later]
Information in this document applies to any platform.
Error Message Area:Data Manager - DAT
Version:Siebel 7.7

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-00170: The DLL '%1' could not be loaded.

Scope

This document is informational and intended for any user.

SBL-DAT-00170: The DLL '%1' could not be loaded.

Explanation

1. Incorrect installation or corruption during installation may cause this error. For example, the SWSE is installed to the same directory as the SES. Or Siebel component(s) were not updated correctly because they were in use during the upgrade.

2. The SBL-DAT-00170 error occurs when accessing third-party software, for example, MQ Series, C++, IBM LDAP Client, and so forth.

3. In Siebel Industry Applications, when the Validate button is used in the Product Administration screen, the following error displays: The DLL 'swcsctwb.dll' could not be loaded.(SBL-DAT-00170). This occurs when the Siebel Server is on Unix operating system, for example, Sun Solaris.

4. The following error appears in the object manager log files: ObjMgrLog Error (SBL-DAT-00170) The DLL 'SWCAPRMFR.DLL' could not be loaded.

Corrective Action

1. Identify which component(s) were incorrectly installed or updated. Re-install the component(s) following the parameters in the appropriate Siebel Bookshelf installation guide.

2. Verify that the third-party software version is supported by your Siebel application version. For more information, refer to SupportWeb > Product Documentation > Siebel System Requirements and Supported Platforms & Miscellaneous Documentation.

For supported the C++ Runtime Library versions, refer to Alert 851 on SupportWeb.

For required IBM LDAP Client version when using LDAP authentication, refer to Alert 943 on SupportWeb.

3. Change Requests 12-GIR7L7 and 12-JK5VVP were logged and resolved in Siebel Industry Application version 7.5.3.6.

4. This is a benign error. It is displayed because details are in the standard repository (i.e. inactive) but this does not affect application functionality.

Change Request 12-G3BT9B has been logged.

Applies to:

Error Message Area:Data Manager - DAT
Version:Siebel 7.8

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-00170: The DLL '%1' could not be loaded.

Scope

This document is informational and intended for any user.

SBL-DAT-00170: The DLL '%1' could not be loaded.

Explanation

1. Incorrect installation or corruption during installation may cause this error. For example, the SWSE is installed to the same directory as the SES. Or Siebel component(s) were not updated correctly because they were in use during the upgrade.

2. The SBL-DAT-00170 error occurs when accessing third-party software, for example, MQ Series, C++, IBM LDAP Client, and so forth.

3. The following error appears in the object manager log files: ObjMgrLog Error (SBL-DAT-00170) The DLL 'SWCAPRMFR.DLL' could not be loaded.

Corrective Action

1. Identify which component(s) were incorrectly installed or updated. Re-install the component(s) following the parameters in the appropriate Siebel Bookshelf installation guide.

2. Verify that the third-party software version is supported by your Siebel application version. For more information, refer to SupportWeb > Product Documentation > Siebel System Requirements and Supported Platforms & Miscellaneous Documentation.

For supported the C++ Runtime Library versions, refer to Alert 851 on SupportWeb.

For required IBM LDAP Client version when using LDAP authentication, refer to Alert 943 on SupportWeb.

3. This is a benign error. It is displayed because details are in the standard repository (i.e. inactive) but this does not affect application functionality.

Change Request 12-G3BT9B has been logged.

Applies to:

Error Message Area:Data Manager - DAT
Version:Siebel 7.5.3

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-00170: The DLL '%1' could not be loaded.

Scope

This document is informational and intended for any user.

SBL-DAT-00170: The DLL '%1' could not be loaded.

Explanation

1. Incorrect installation or corruption during installation may cause this error. For example, the SWSE is installed to the same directory as the SES. Or Siebel component(s) were not updated correctly because they were in use during the upgrade.

2. The SBL-DAT-00170 error occurs when accessing third-party software, for example, MQ Series, C++, IBM LDAP Client, and so forth.

3. The following error appears in the object manager log files: ObjMgrLog Error (SBL-DAT-00170) The DLL 'SWCAPRMFR.DLL' could not be loaded.

4. In Siebel Industry Applications, when the Validate button is used in the Product Administration screen, the following error displays: The DLL 'swcsctwb.dll' could not be loaded.(SBL-DAT-00170). This occurs when the Siebel Server is on Unix operating system, for example, Sun Solaris.

Corrective Action

1. Identify which component(s) were incorrectly installed or updated. Re-install the component(s) following the parameters in the appropriate Siebel Bookshelf installation guide.

2. Verify that the third-party software version is supported by your Siebel application version. For more information, refer to SupportWeb > Product Documentation > Siebel System Requirements and Supported Platforms & Miscellaneous Documentation.

For supported the C++ Runtime Library versions, refer to Alert 851 on SupportWeb.

For required IBM LDAP Client version when using LDAP authentication, refer to Alert 943 on SupportWeb.

3. This is a benign error. It is displayed because details are in the standard repository (i.e. inactive) but this does not affect application functionality.

Change Request 12-G3BT9B has been logged.

4. Change Requests 12-GIR7L7 and 12-JK5VVP were logged and resolved in Siebel Industry Application version 7.5.3.6.

SBL-DAT-00560: An error occurred preparing a SQL object for employee information. See additional error messages for more information

Date:

Applies to:

Siebel Tools - Version: 7.7.1 [18306] - Release: V7
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.7.1 [18306] DEU
Database: IBM DB2 8.1 FixPack 3
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server

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

Symptoms

SBL-DAT-00556, SBL-DAT-00546, SBL-DAT-00560

Follow-up from SR 38-1453099441

1. Starting Siebel via web client fails. Please see the attached log-files for error messages.
(For translation see Siebel Error Messages > Siebel 7.7).
SBL-DAT-00560, SBL-DAT-00556, SBL-DAT-00546, SBL-SVC-00208, SBL-DAT-00385

2. Doing a full compile on the extracted local developer database fails:

Displayed error messages:
An error message has occured executing a Sql statement.
Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DBC-00105)

Internal database error *** ERROR *** Assertion failed: 102300 (8.0.2.4361)
File associated with given page id is invalid or not open -- transaction rolled back

According to SR 38-1371657223 we regenerate db template, extracted db again, initialize it, perform a full get but the error still remains.

Compiling a new SRF connected to the server succeded.

3. The error messages described in the attached log files do not appear using a standard SRF.
We are able to connect successfully via Web Client.

4. We are able to connect successfully using the Siebel Dedicated Web Client. The same error messages are logged in local siebel.log while using compiled new SRF.

5. We renamed the Siebel_Server/bin/diccache.dat, but errors still remain.

Thank you for your quick response.

Henrik

Cause

The cause for the assertion failed error message sometimes occurs when the local db needs to allocate temporary files and does not have enough space.

Solution

Message 1

DESCRIPTION:

Tools stops during full compile on local db.

SYMPTOMS:

Doing a full compile on the extracted local developer database fails:

Displayed error messages:
An error message has occured executing a Sql statement.
Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DBC-00105)

Internal database error *** ERROR *** Assertion failed: 102300 (8.0.2.4361)
File associated with given page id is invalid or not open -- transaction rolled back

When using the unfinished srf file the following errors are shown in the client log file:

SBL-DAT-00560
SBL-DAT-00556
SBL-DAT-00546
SBL-SVC-00208
SBL-DAT-00385

SOLUTION:

The assertion failed error message sometimes occurs when the local db needs to allocate temporary files. This files are usual stored in the path of the TEMP system variable which usual points to C:\temp. As the temporary files can grow up to 500 MB the C hard disk sometimes has no free space for the temporary files.

In this case the issue has been resolved by deleting the TEMP system variable and recreating it new.


Siebel Technical Support


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

Date:

Applies to:

Siebel System Software - Version: 7.7 [18026] BETA to 8.1.1 [21112] - Release: V7 to V8
Information in this document applies to any platform.

Symptoms

Note:  This solution only applies to enterprises running their OLTP database on an Oracle database.

When attempting to run KEYDBMGR (keydbmgr.exe), the following error is presented:

Error loading dictionary file diccache.dat.(SBL-DAT-60237)
Cleaning up... this may take a while.

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.


Applies to:

Siebel Sales - Version: 8.0.0.2 [20412] - Release: V8
Information in this document applies to any platform.

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-60237

I 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.



Thank you,


Siebel Technical Support


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.

References

NOTE:551663.1 - Error loading dictionary file diccache.dat.(SBL-DAT-60237) when running KEYDBMGR

SBL-DAT-00144: Could not find '%1' named '%2'. This object is inactive or nonexistent.

Date:

Applies to:

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

Symptoms

The customer reported that the 8.0.0.2 Public Sector application standard Solutions find object returns an error.  The other Find objects worked fine without any errors.  In this case, only the Solutions Find object returned this error in the Public Sector application.

If you are getting this error for all of the find objects with a Siebel 8.0.0.2 client with the configuration steps documented for ACR 367, verify that you have added the Search Find Results View to the application and that the view is in the user's responsibilities

Another possible cause for a similar error is if the user is entering a find condition in the Search for: control which should be used only for Siebel Search indexes not find objects.  In that case, the following error is returned. 

The view <?> cannot be displayed.  Please contact your System Administrator (SBL-SRH-50043).

If you are getting this error, then try doing the find search using the find fields and not the Search For field.

 

Cause

This incorrect behavior is due to change request 12-1013BID which was raised as a product defect.
The standard 8.0.0.2 SIA Public Sector Application Find configuration uses the Solution - SHCEService Find object and not the Solutions Find object.
Note that the Solution-SHCEService and the Solutions Find objects both have the display name of Solutions.
The Solution-SHCEService Find object had the following two views..
SHCE Service Solution Find View
SHCE Service Async Query Results Solution List View

These views are in the seed data Field Technician - Handheld Responsibility which most seed data users do not have access to.
Product Defect 12-1013BID notes that the 8.0.0.2 Public Sector application should use the Solutions Find object, which displays the All Solution List View. This view is included in most of the seed data responsibilities.

This behavior is also related to how Siebel Search Find with Siebel 8 works with Responsibilities.

See this document too.

Siebel 8 - Search Center - All Users, Except Siebel Administrator, Get Error SBL-DAT-00144 <Doc: 563439.1> .


Solution

The workaround for this behavior is to modify the SIA application to use the Solutions Find object.
This modification needs to be done in the srf file and in the Siebel applications server database Repository Tables. This is because the following sql is executed to find the application's find objects.
SELECT
T1.CONFLICT_ID,
T1.LAST_UPD,
T1.CREATED,
T1.LAST_UPD_BY,
T1.CREATED_BY,
T1.MODIFICATION_NUM,
T1.ROW_ID,
T1.NAME,
T2.OBJ_LOCKED_LANG,
T2.OBJ_LOCKED_FLG,
T2.OBJ_LOCKED_BY,
T1.APPLICATION_ID,
T2.NAME,
T2.PROJECT_ID,
T3.LOCKED_FLG,
T3.LOCKED_BY,
T3.NAME,
T3.UIFREEZE_FLG,
T3.UIFREEZE_BY,
T1.REPOSITORY_ID,
T1.FIND_NAME,
T2.MODULE_NAME,
T1.INACTIVE_FLG,
T2.ROW_ID,
T3.ROW_ID
FROM
SIEBEL.S_APPL_FIND T1
INNER JOIN SIEBEL.S_APPLICATION T2 ON T1.APPLICATION_ID = T2.ROW_ID
LEFT OUTER JOIN SIEBEL.S_PROJECT T3 ON T2.PROJECT_ID = T3.ROW_ID
WHERE
(T2.NAME = ? AND T1.INACTIVE_FLG != ?)
ORDER BY
T1.NAME

ObjMgrSqlLog Detail 4 00000002480306a0:0 2008-04-14 18:25:45 Bind variable 1: Siebel Public Sector

ObjMgrSqlLog Detail 4 00000002480306a0:0 2008-04-14 18:25:45 Bind variable 2: Y
In summary the workaround is the following steps:

1. Modify the Siebel Public Sector to not use the Solution-SHCEService find object.
But instead have it use the Solutions find object.
2. Due to the architecture change with Search/Find with Siebel 8.0, you have to make sure that the server RDBMS also has this change for the Siebel Repository.

Oracle Siebel Support


References

NOTE:563439.1 - Siebel 8 - Search Center - All Users, Except Siebel Administrator, Get Error SBL-DAT-00144

Show Related Information Related

Products
  • Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel Tools
Keywords
CONFIGURATION; SIEBEL APPLICATION
Errors
SBL-DAT-00144; SBL-SRH-50043

Applies to:

Siebel Reports - Version: 8.1.1.3 SIA[21219] and later   [Release: V8 and later ]
Information in this document applies to any platform.
Siebel 8.1.1.3 Fix Pack, BI Publisher 10.1.3.4.1

Symptoms

When attempting to run BIP reports by clicking Reports menu icon, the following error occurs:

ERROR
-----------------------
"SBL-DAT-00144: Could not find 'Business Component' named 'Report Template Position BC'. This object is inactive or nonexistent."

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. In Siebel application (Thin or Thick client), you click Reports menu icon
2. The error above is displayed.

Changes

This happens after installing Siebel 8.1.1.3 Fix Pack.

Cause

The error can occur when you have not complete all configuration steps to integrate BI Publisher with Siebel 8.1.1.3 Fix Pack.

You should follow all steps from Bookshelf 8.1: Siebel Reports Guide, Rev. C (June 2010).

Solution

Please note that after installing 8.1.1.3 Fix Pack you should follow all steps from Bookshelf 8.1: Siebel Reports Guide, Rev. C (June 2010), under Chapter 4. Integrating Oracle BI Publisher with Siebel Business Applications > Process of Configuring the Siebel Application for Integration with Oracle BI Publisher, which includes import BIP_8113FP.sif file and Apply DDL.

Bookshelf 8.1: Siebel Reports Guide, Rev. C (June 2010) can be downloaded from:
http://download.oracle.com/docs/cd/E14004_01/books/Reports/ReportsTOC.html



Show Related Information Related

Products
  • Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel Reports
Keywords
REPORT; INSTALL; BI PUBLISHER
Errors
SBL-DAT-00144; 00144 ERROR

Applies to:

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

Symptoms

Data is being processed from an external system into UCM using "UCM Account Batch Data Management Workflow" in batch mode.

Some data was left was an incomplete status. The failure occurred when the Account details were the same, but the Country in the Address was different. Exact Match is being used, and for these cases, it should have updated the existing master.

For example: the master record in UCM has 1689 Ingleton Avenue,Burnaby, BC, V5C 4L8, USA and the record processed is 1689 Ingleton Avenue,Burnaby, BC, V5C 4L8, CANADA. This record goes to incomplete status. The records corresponding S_UCM_ADDR_PER record stays in "Batch" status. UCM_TYPE_CD = 'Batch' is the status used for records imported into UCM_ORG_EXT using EIM.

The error seen in the failure log is :-

Error invoking service 'UCM Batch Manager', method 'HandleMatchCase' at step 'Process AutoMatch'.(SBL-BPR-00162)
--
Could not find '<?>' named '<?>'. This object is inactive or nonexistent.(SBL-DAT-00144)

Also noticed was the following :-

SBL-DAT-00144: Could not find 'Business Object' named 'CIF StatusObject Reference'. This object is inactive or nonexistent.

Cause

The problem is due to reported behaviour in the following change request :-

Bug 12-1MBPPSX - Could not find 'Business Object' named 'CIF StatusObject Reference'

There is a SQL select statement on S_PARTY which will not work. It has a criteria including a WHERE clause on LAST_UPD, for which 0 rows will be returned (leading to above error). This is because S_PARTY.LAST_UPD has already been updated in a previous UPDATE. Because 0 rows are returned, the error above occurs.

Solution

After making the following changes, the error could be avoided, and the address update processed ok :-

1. Find the 'CIFAccountUpdate' Integration Object in Tools.
2. For the 'Account' Integration Component, review the Integration Compenent Keys. For the key named 'Status Key', inactivate the 'Updated' Integration Component Key Field.
3. Compile to SRF, and re-test scenario where an incoming Account / Address matches existing data, but with a different Country.

References

BUG:12-1MBPPSX - COULD NOT FIND 'BUSINESS OBJECT' NAMED 'CIF STATUSOBJECT REFERENCE'

Show Related Information Related

Products
  • Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel Universal Customer Master
Keywords
BATCH MANAGER; STATUS KEY; WHERE CLAUSE; INCOMPLETE STATUS; ACCOUNT DETAILS; SCENARIO; UNIVERSAL CUSTOMER MASTER
Errors
SBL-BPR-00162; SBL-DAT-00144

Applies to:

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

Symptoms

Data is being processed from an external system into UCM using "UCM Account Batch Data Management Workflow" in batch mode.

Some data was left was an incomplete status. The failure occurred when the Account details were the same, but the Country in the Address was different. Exact Match is being used, and for these cases, it should have updated the existing master.

For example: the master record in UCM has 1689 Ingleton Avenue,Burnaby, BC, V5C 4L8, USA and the record processed is 1689 Ingleton Avenue,Burnaby, BC, V5C 4L8, CANADA. This record goes to incomplete status. The records corresponding S_UCM_ADDR_PER record stays in "Batch" status. UCM_TYPE_CD = 'Batch' is the status used for records imported into UCM_ORG_EXT using EIM.

The error seen in the failure log is :-

Error invoking service 'UCM Batch Manager', method 'HandleMatchCase' at step 'Process AutoMatch'.(SBL-BPR-00162)
--
Could not find '<?>' named '<?>'. This object is inactive or nonexistent.(SBL-DAT-00144)

Also noticed was the following :-

SBL-DAT-00144: Could not find 'Business Object' named 'CIF StatusObject Reference'. This object is inactive or nonexistent.

Cause

The problem is due to reported behaviour in the following change request :-

Bug 12-1MBPPSX - Could not find 'Business Object' named 'CIF StatusObject Reference'

There is a SQL select statement on S_PARTY which will not work. It has a criteria including a WHERE clause on LAST_UPD, for which 0 rows will be returned (leading to above error). This is because S_PARTY.LAST_UPD has already been updated in a previous UPDATE. Because 0 rows are returned, the error above occurs.

Solution

After making the following changes, the error could be avoided, and the address update processed ok :-

1. Find the 'CIFAccountUpdate' Integration Object in Tools.
2. For the 'Account' Integration Component, review the Integration Compenent Keys. For the key named 'Status Key', inactivate the 'Updated' Integration Component Key Field.
3. Compile to SRF, and re-test scenario where an incoming Account / Address matches existing data, but with a different Country.

References

BUG:12-1MBPPSX - COULD NOT FIND 'BUSINESS OBJECT' NAMED 'CIF STATUSOBJECT REFERENCE'

Show Related Information Related

Products
  • Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel Universal Customer Master
Keywords
BATCH MANAGER; STATUS KEY; WHERE CLAUSE; INCOMPLETE STATUS; ACCOUNT DETAILS; SCENARIO; UNIVERSAL CUSTOMER MASTER
Errors
SBL-BPR-00162; SBL-DAT-00144

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.4 [16180] DAN
Database: Oracle 9.2.0.2
Application Server OS: Microsoft Windows NT Enterprise 4.0 SP 6a
Database Server OS: Microsoft Windows NT Enterprise 4.0 SP 6a

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

Symptoms

SBL-DAT-00144, SBL-DAT-00192, SBL-DAT-00227

Please assign this SR to an engineer with high skills of both Siebel Marketing, Workflow Processes and Business Services.

We have upgraded from 6.3 to 7.5.3.4 DAN and still need to use a customized WF for campaign launch (previously campaign execution).

The customized campaign launch WF includes a custom BS step and it worked fine in Siebel 6.3.

In 7.5.3 we have tried both of the following:

1. Exporting the Campaign Execution WF from 6.3 and then Importing it to 7.5.3, change name to Campaign Launch and then activate.

2. Manually revise the existing Campaign Launch WF in 7.5.3 to include our customizations from 6.3.

When creating snapshots and loading campaign (populating campaign in 6.3) no errors occur.
However, when launching campaign manually the following error displays (no matter which of the above two methods was used):

SBL-OMS-00203: Error 32956 invoking method "RunProcess" for Business Service "Workflow Process Manager"

From looking into the log file (attached) the following two errors turn up:
SBL-DAT-00144 and SBL-DAT-00192.

I've found only one SR in Support Web including the above SBL-DAT errors (SR # 38-1224781281) but this is not related to our problem.

The custom BS in question - Nyk Modify List Output - is included in the SWE section of the cfg file (attached to this SR).

The WF component group is only installed on a single server in accordance with the instructions for SME configuration as specified in the Siebel Marketing Initialization Checklist in the Siebel Marketing Guide. This component installation should be correct as the WF runs OK when loading campaign.

The custom BS is included in the compiled SRF file on the servers.

So basically we need answers to the following questions:
1. Why do we see the SBL-DAT-00144 and SBL-DAT-00192 errors when BS is included in both the siebel.cfg file on the server and the compiled srf file on the server?
2. How do we proceed?

Looking forward to your answer.
...

Solution

Message 1

For the benefits of the other readers:
The customer customized the Campaign Execution workflow in Siebel Marketing 6.3.
After upgrading to Siebel Marketing 7.5.3 they included their customization into Campaign Launch Workflow and launched their campaign. However the Campaign Launch failed with the following error:

(SBL-DAT-00192) Unable to find the definition of Business Service 'Nyk Modify List Output' in either the repository or run-time tables.
(SBL-DAT-00144) Could not find 'Class' named 'Nyk Modify List Output'. This object is inactive or nonexistent.
(SBL-DAT-00227) Unable to create the Business Service 'Nyk Modify List Output'

The customer run Siebel Marketing 7.5.3 in Danish and the default language of the Workflow Process Component was ENU.
They compiled only the Danish Repository and put into SiebSrvr\Object\Dan folder. However the Campaign Launch workflow was run in ENU and their customization were not compiled in the ENU repository located in SiebSrvr\Object\ENU folder.
Changing the default language of the Worflow Process component to DAN resolved the error.

The customer noticed that when launching a custom workflow using button or even the workflow was then defaulted to the Language of the corresponding component used to launch it.

Change Request 12-KWLOVN has been raised to address this Enhancement Request (select a campaign Launch on DAN client should not launch an ENU Workflow)

Magali Barreau-Combeau
Siebel Technical Support