Siebel EIM-Errors: SBL-EIM-00101, SBL-EIM-00103, SBL-EIM-00105, SBL-EIM-00107, SBL-EIM-00108, SBL-EIM-00201,SBL-EIM-00204,SBL-EIM-00205, SBL-EIM-00206 and SBL-EIM-00207

Siebel Articles Python Perl 5 Documentation Manuel PHP7 français

Java Das PHP7 Handbuch PHP7 Manual English Linux and Unix News

Siebel EIM > Errors: SBL-EIM-00101, SBL-EIM-00103, SBL-EIM-00105, SBL-EIM-00107, SBL-EIM-00108, SBL-EIM-00201,SBL-EIM-00204,SBL-EIM-00205, SBL-EIM-00206 and SBL-EIM-00207

SBL-GEN-10204 Error attempting to release O/S mutex

No Information

SBL-GEN-10205 Error deleting O/S mutex

No Information

SBL-GEN-10301 Process enumeration has failed

No Information

SBL-GEN-10302 Interface initialization has failed

No Information

SBL-GEN-10303 Data update or counter query has failed

No Information

SBL-GEN-10304 Process query has failed.

No Information

SBL-GEN-10305 Caller has supplied an invalid argument to the API

No Information

SBL-GEN-10306 Physical disk enumeration has failed

No Information

SBL-GEN-10307 Physical Disk Stat query has failed

No Information

SBL-GEN-10308 Process does not exist.

No Information

SBL-GEN-10309 Update interval is too short

No Information

SBL-GEN-10310 Timer query has failed

No Information

SBL-GEN-10311 CPU Stat query failed

No Information

SBL-GEN-10312 Access to specified process is denied

No Information

SBL-GEN-10313 Process has exited

No Information

SBL-GEN-10314 Memory statistics failed

No Information

SBL-GEN-10315 Could not get the host name.

No Information

SBL-EIM-00101 Invalid arguments passed to EIM.
"SBL-EIM-00101: Invalid arguments passed to EIM" when exporting attachments
Exporting Attachments via EIM_CON_DTL leads to the following error messages seen for example in the Server Manager Command line window:

SBL-ADM-60070: Error reported on server 'srvr1' follows:
SBL-SVR-01042: Internal: Communication protocol error while instantiating new task
SBL-EIM-00101: Invalid arguments passed to EIM.
SBL-EIM-00101: Invalid arguments passed to EIM.

Check the SQL in the Log file. If you are using the same column more than once to update/delete or insert data, this could be the result.
Usually this will come with a database error.

Check the status of the job, it may still be completed. This has been identified as a Siebel Bug.

This can also mean that the values provided may be wrong. e.g. You may have provided a Date Time that is out of range

GenericLog GenericError 1 2004-09-24 20:46:33 [IBM][CLI Driver][DB2] SQL0181N The string representation of a datetime value is out of range. SQLSTATE=22007

In DB2 Database, this can be a temporary error with Date Time values

Error Error 1 2004-06-08 10:15:20 SQL Warning, SQL State 22007, -181, [IBM][CLI Driver][DB2] SQL0181N The string representation of a datetime value is out of range. SQLSTATE=22007

When The sql is run independently or the eim job is re run, then the error does not appear again.

SBL-EIM-00102 Too little memory to perform operation.
Supposed to be a Database or OS error. No information available in Internet now (20 March 2018)

SBL-EIM-00103 Name is not a valid identifier.

Cannot Run EIM "SBL-EIM-00206: Failed to run initial process.

APPLIES TO:
Siebel Enterprise Integration Manager - Version 8.0.0.5 SIA [20420] and later

SYMPTOMS

When EIM task run, it is exiting with following error:

SBL-ADM-60070: Error reported on server 'usolsrvr' follows:
SBL-SVR-01042: Internal: Communication protocol error while instantiating new task SBL-EIM-00206: Failed to run initial process.
SBL-EIM-00206: Failed to run initial process.

Steps:

1. Prepare any EIM table for EIM load.
2. Create ifb file and add IGNORE BASE COLUMN parameter to ignore certain columns from populating:
3. Run EIM task.

CAUSE
The error is caused by the use of "IGNORE BASE COLUMN" parameter in the ifb file.

Has been observer that “IGNORE BASE COLUMN” is an incorrect parameter.

EIM_0038_39845891.log shows the following error message:

"Error SBL-EIM-00103, in "AccountsInterface.ifb" line 180: Invalid parameter IGNORE BASE COLUMN."

SOLUTION
It was observed that removing parameter IGNORE BASE COLUMN from the ifb file resolved the issue.

The correct syntax of this parameter is IGNORE BASE COLUMNS with an S. This parameter is an optional one and you can use it to Specify base table columns to be ignored by the import process. Please note that required and user key columns cannot be ignored. For further details about this parameter please refer to Bookshelf: Siebel Enterprise Integration Manager Administration Guide > Importing Data > Editing the Configuration File for Import Processing > Process Section Parameters Used for Imports.

SBL-EIM-00104 Requested entry not found.

No Information

SBL-EIM-00105 Operating system error.

EIM Task Using .IFB File on Different Machine, Box, Fails with SBL-EIM-00105: Operating system error and Error SBL-EIM-00204: Failed to load configuration file

APPLIES TO:
Siebel Enterprise Integration Manager - Version 7.0.4.15 FINS [14078] to 16.0 [IP2016] [Release V7 to V16]

Database: MS SQL Server 8 (2000)

Application Server OS: Microsoft Windows 2000 Advanced Server SP 2

Database Server OS: Microsoft Windows 2000 Advanced Server SP 2

SYMPTOMS
We are currently trying to run EIM processes in our integration environment. This environment consists of 3 machines (1 database server, 1 application server and one web server).
We are trying to run EIM processes having all files resident in the Database Server (including the server manager exec.).
We've a problem while running the processes that consists in server manager reporting the following errors:

GenericLog GenericError 1 2002-10-25 08:39:35 EIM: Integration Manager v7.0.4.15 [14078] LANG_INDEPENDENT failure log (pid 2484).
GenericLog GenericError 1 2002-10-25 08:39:35
GenericLog GenericError 1 2002-10-25 08:39:35 Error 105: Operating system error.
GenericLog GenericError 1 2002-10-25 08:39:35
GenericLog GenericError 1 2002-10-25 08:39:35 Error 204: Failed to load configuration file
GenericLog GenericError 1 2002-10-25 08:39:35 "\\egcintsql\Interfaces\scripts\CONTACT\V02\ifb\CONTACT.ifb".
GenericLog GenericError 1 2002-10-25 08:39:35 (compmain.cpp 16(1552) err=100204 sys=0) EIM-00204: Invalid configuration file to load initially.
GenericLog GenericError 1 2002-10-25 08:39:35 (smisched.cpp 17(791) err=100204 sys=0) EIM-00204: Invalid configuration file to load initially.
GenericLog GenericError 1 2002-10-25 08:39:35
GenericLog GenericError 1 2002-10-25 08:39:35 Recorded 2 errors (no failure information)

This happens whenever the ifb file is on a server other than the application server, although if you are on the application server you can "see" the file using explorer or a command prompt.
We've already tried mapping a drive, using the default share, sharing to everyone, etc.
FYI : the servers are not on a domain but on the same workgroup, and have the same user/password configuration.

CAUSE
EIM .ifb file is not on the same machine as the Siebel Server.

SOLUTION
Message 1

The .ifb file for any given EIM job has to be located on the computer where the Siebel Application Server is installed as well.

EIM can't resolve an operating system path to a remote system.

Documentation enhancement request 12-DYOA98 was logged asking to document this fact.

Bug 10456571 - [CR#12-DYOA98][FR#12-DYOA98+F] DOCUMENT THAT AN .IFB FILE HAS TO BE ON THE SAME BOX WHERE THE SIEBEL SERVER IS INSTALLED

How to Reproduce: At times customers try to store .ifb files for EIM on other computers than the one where the Siebel Application Server is installed by making use of mapped netweork drives, shares etc.

Please document that the .ifb files have to be located on the box where theSiebel Application Server is installed as EIM is not able to resolve a path to a remote shared drive.

Note, another customer reported the same behavior with a later Siebel version and his restriction was not found in the 2016 Siebel Bookshelf's Enterprise Integration Manager Guide.

SBL-EIM-00106 Functionality not yet implemented.

No Information

SBL-EIM-00107 ODBC (SQL) error

SBL-EIM-00107: ODBC (SQL) ERROR WHEN RUNNING EIM JOB BY DUPLICATED RECORDS

APPLIES TO:
Siebel Enterprise Integration Manager - Version 7.8.2 SIA [19213] and later
Information in this document applies to any platform.

SYMPTOMS

Comments
--------
Environment
=========

Siebel/Database:V7.8.2.1/Oracle

Steps
=======

1) You have run an EIM job with 1 million records and the job initially failed.

2) Divided the records into 8 batches and started parallel EIM execution.

3) The job fails with the same error

Error message
===========

DBC error 23000: [DataDirect][ODBC Oracle driver][Oracle]ORA-00001: unique constraint (SIEBEL.S_ASSET_U1) violated
This low-level failure caused all processing to halt for the specified interface table. Check the error messages for more information.
< Importing EIM_ASSET 3:07m
Import EIM_ASSET 800008 3:07m
SBL-EIM-00107: ODBC (SQL) error
SBL-EIM-00107: ODBC (SQL) error

CAUSE

The issue has been caused by having duplicate records in the EIM table that were used in parallel EIM execution

The duplicate data was returned by running the following query:

SELECT
AST_ASSET_NUM,
AST_BU,
AST_REV_NUM,
AST_PROD_BU,
AST_PROD_NAME,
AST_PROD_VEN_BU,
AST_PROD_VEN_LOC,
AST_PROD_VEN_NAME,
COUNT(*)
FROM EIM_ASSET GROUP BY
AST_ASSET_NUM,
AST_BU,
AST_REV_NUM,
AST_PROD_BU,
AST_PROD_NAME,
AST_PROD_VEN_BU,
AST_PROD_VEN_LOC,
AST_PROD_VEN_NAME HAVING COUNT (*) > 1;

The above query is based on user keys (corresponding EIM columns) on S_ASSET table. This would cause the error "Unique Constraint Violated".

Customer was able to recreate the error on Test environment with duplicates being introduced.

SOLUTION

The issue has been caused by introducing duplicate records in EIM table that violate unique index on S_ASSET table. Although they were separated with different batch numbers due to parallel processing the duplicate records did interfere with EIM processing. We used following query specifically to find the S_ASSET duplicate records with it's unique index. In this case, we will need to query on corresponding EIM columns.

To resolve this issue:

1) Based on the data generated in the above query, update the EIM table to reflect unique records

2) or delete the duplicates that could possibly violate the unique index.

3) Run EIM job.

SBL-EIM-00108 Internal error in retrieving scf parameter

SBL-EIM-00108: Internal error in retrieving scf parameter, but same EIM Job at Command Line Finishes without Error.

APPLIES TO:
Siebel CRM - Version 15.10 [IP2015] and later
Information in this document applies to any platform.

SYMPTOMS
On : 15.10 [IP2015] version, EIM

Running any EIM job from the UI fails with the error SBL-EIM-00108: Internal error in retrieving scf parameter, but running the same EIM job from the srvrmgr command line works fine.

This error in the UI EIM log file only happens for jobs submitted in the view. The Siebel environment was recently upgraded to IP2015 from IP2013.

ERROR
-----------------------
SBL-EIM-00108

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Try to submit an EIM job from the GUI.

CHANGES
Siebel was recently upgraded to IP2015 from 8.1.1.11.

CAUSE
EIM will give this error "SBL-EIM-00108: Internal error in retrieving scf parameter" when it is having a problem with the EIM server component parameters for Username and Password.

If your user submitted the eim job and explicitly filled in the EIM component parameter for Username and Password, that will work.

There is an issue with the Siebel Server siebns.dat file and how it stores encrypted passwords post upgrade.
If there is an EIM component that has a default user name and password component parameter like EIM, the component parameters need to be manually reset after upgrading to IP2015.

SOLUTION
In Siebel CRM Innovation Pack 2015, passwords in the siebns.dat file are encrypted using AES encryption. When upgrading to the current release, you must reset encrypted passwords in the siebns.dat file so that they now use AES encryption.

When upgrading to the current release, the Siebel Server system service password, which is required to connect the Siebel Server to the Gateway Name Server, is automatically reencrypted using AES encryption. The Gateway Name Server Password parameter, which is set at the Siebel Enterprise level, is also automatically reencrypted. You do not have to reencrypt these passwords manually.

For more information please see the following :https://docs.oracle.com/cd/E63029_01/books/Secur/secur_dataencrypt020.htm

srvrmgr command syntext to check EIM component parameters for username and password and to reset the component parameters:

list parameters for component EIM

change parameter parameter_alias_name1=value1, parameter_alias_name2=value2 for component component_alias_name server siebel_server_name

SBL-EIM-00201 Invalid command line arguments.

APPLIES TO:
Siebel Energy - Version 15.0 [IP2015] and later
Information in this document applies to any platform.
SYMPTOMS
EIM fails to execute using the same ifb-file from a previous Siebel version (or patch level) when comments are included in the ifb-file.

Example:

;------This is the start of the comment section in the EIM ifb-file---------------
;
; Name: Name of ifb-file
;
; Filetype: Siebel Enterprise Integration Manager Configuration file
;
; Purpose: Loading records into Siebel Base table(s)
;
; Created: 03.09.2015
;
;------This is the end of the comment section in the EIM ifb-file---------------

[Siebel Interface Manager]

...

The EIM-log file may contain error messages as shown below:

2015-08-06 09:11:25 EIM TASK with TaskNum=57671683, Pid=7904, Tid=3340 started by Request Manager

2015-08-06 09:11:25 8/6/15 9:11 Status: Integration Manager v8.2.2.14 [23044] LANG_INDEPENDENT starting up (pid 7904)

2015-08-06 09:11:25 8/6/15 9:11 Status: Loading initial configuration file "SAMPLE.ifb".

2015-08-06 09:11:25 8/6/15 9:11 Error SBL-EIM-00201: No process specified to run.

06 09:11:25 (compmain.cpp (1565) err=65737 sys=126) SBL-EIM-00201: Invalid command line arguments.

06 09:11:25 (smisched.cpp (923) err=65737 sys=0) SBL-EIM-00201: Invalid command line arguments.

2015-08-06 09:11:25 8/6/15 9:11 Status: Exiting (status 65737).

CAUSE
This behaviour is caused by saving the ifb-file using a non-Unicode codepage such as the ANSI codepage.

SOLUTION
Saving the ifb-file using a unicode encoding (e.g. via the Windows Notepad application) resolved the matter.

Bug 22117720 has been raised to address the matter.

A fix is available as of Siebel 8.1.1.14 / 8.2.2.14 patchset 10 which can be downloaded using the following patch number:

For 8.1.1.14.10 --> Patch number: 21869406

For 8.2.2.14.10 --> Patch number: 21869408

SBL-EIM-00202 Invalid SIEBELHOME directory.

No Information

SBL-EIM-00203 Invalid file to log to.

No Information

SBL-EIM-00204 Invalid configuration file (ifb) name.

EIM Unable to load data error SBL-EIM-00204

APPLIES TO:
Siebel Enterprise Integration Manager - Version 7.5.3.6 [16186] to 8.2.2 SIA[22320] [Release V7 to V8]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3.6 [16186]
Database: IBM DB2/UDB 7.2
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: IBM AIX 5L 5.1

SYMPTOMS
SBL-EIM-00204, SBL-GEN-09103

I am getting an error that the configuration file is invalid after upgrade to Siebel 7.5.3.6. This error occured on the TEST server but not the DEV server.

here is the IFB

;Trial for Loading Order Items for Siebel 7.53 DWB
;
;Loading of orders is done with srvrmgr
;password in this file is invalid and
;overidden by parms passed to srvrmgr

[Siebel Interface Manager]
USER NAME = "SADMIN"
PASSWORD = "***"
PROCESS = Import Order Items

[Import Order Items]
TYPE = IMPORT
BATCH = 1
TABLE = EIM_ORDER_ITEM
UPDATE STATISTICS = FALSE

FIXED COLUMN = ALW_PART_SHIP_FLG, "N"
FIXED COLUMN = ORDER_REV_NUM, 1
FIXED COLUMN = BILLABLE_FLG, "Y"
FIXED COLUMN = LOANER_FLG, "N"
FIXED COLUMN = ROLLUP_FLG, "N"
FIXED COLUMN = WRNTY_RCVR_FLG, "N"
FIXED COLUMN = AUTO_RECV_FLG, "Y"
FIXED COLUMN = DISCNT_SRC_CD, "Manual"
FIXED COLUMN = EXCL_PRICING_FLG, "N"
FIXED COLUMN = HOLD_FLG, "N"
FIXED COLUMN = LATE_FLG, "N"
FIXED COLUMN = PROCESSED_FLG, "N"
FIXED COLUMN = PROMO_ITEM_FLG, "N"
FIXED COLUMN = ROLLUP_FLG, "N"
FIXED COLUMN = SHIP_COMPLETE_FLG, "N"
FIXED COLUMN = SHIP_TOGETHER_FLG, "N"
FIXED COLUMN = SINGLE_SRC_FLG, "N"

ONLY BASE TABLES = S_ORDER_ITEM
ONLY BASE COLUMNS = ORDER_ID, \
LN_NUM, \
PAR_ORDER_ITEM_ID, \
PROD_ID, \
QTY_REQ, \
DESC_TEXT, \
UNIT_PRI, \
X_TOTAL_BILLED, \
X_START_DATE, \
X_ACCESS_LEVEL, \
X_ISSN, \
X_PUBLISHER, \
X_END_DT

CAUSE
The issue has been caused due to the wrong location of ifb file.

SOLUTION
When customer run EIM import job, the following error occurred :

Trace Trace 3 2004-07-29 11:35:23 7/29/04 11:35 Error 204: Failed to load configuration file "orditmlc.ifb". GenericLog GenericError 1 2004-07-29 11:35:23 GenericLog GenericError 1 2004-07-29 11:35:23 Error 204: Failed to load configuration file "orditmlc.ifb". GenericLog GenericError 1 2004-07-29 11:35:23 (compmain.cpp 16(1555) err=100204 sys=0) SBL-EIM-00204: Invalid configuration file to load initially. GenericLog GenericError 1 2004-07-29 11:35:23 (smisched.cpp 17(821) err=100204 sys=0) SBL-EIM-00204: Invalid configuration file to load initially.

The error message “SBL-EIM-00204: Invalid configuration file to load initially” could be caused due to the configuration .ifb file name is invalid and the path to the file is not correct. For more details about defining ifb file requirements and location, please review EIM documentation.

It was found by the customer that the corresponding configuration file (orditmlc.ifb) was not in the folder specified when running the EIM import job and it caused the reported error.

EIM Task Using .IFB File on Different Machine, Box, Fails with SBL-EIM-00105: Operating system error and Error SBL-EIM-00204: Failed to load configuration file

APPLIES TO:
Siebel Enterprise Integration Manager - Version 7.0.4.15 FINS [14078] to 16.0 [IP2016] [Release V7 to V16]
z*OBSOLETE: Microsoft Windows 2000
Version: 7.0.4.15 [14078] Fin Svcs

Database: MS SQL Server 8 (2000)

Application Server OS: Microsoft Windows 2000 Advanced Server SP 2

Database Server OS: Microsoft Windows 2000 Advanced Server SP 2

CAUSE
EIM .ifb file is not on the same machine as the Siebel Server.

SOLUTION
Message 1
For the benefit of the reader:

The .ifb file for any given EIM job has to be located on the computer where the Siebel Application Server is installed as well.

EIM can't resolve an operating system path to a remote system.

Please document that the .ifb files have to be located on the box where theSiebel Application Server is installed as EIM is not able to resolve a path to a remote shared drive.

Note, another customer reported the same behavior with a later Siebel version and his restriction was not found in the 2016 Siebel Bookshelf's Enterprise Integration Manager Guide.

SBL-EIM-00205 Failed to load the application dictionary.

EIM Task Fails with SBL-EIM-00205: Failed To Load The Application Dictionary

APPLIES TO:
Siebel Enterprise Integration Manager - Version 7.7.2.8 [18379] and later

SYMPTOMS
EIM_29850.log had the following entries:

SQLStatementOptions Free Statement Details 5 0 2010-10-12 03:37:11 (SQLFreeStmt) Option: SQL_RESET_PARAMS

GenericLog GenericError 1 0 2010-10-12 03:37:11 Message: GEN-13, Additional Message: dict-ERR-1109: Unable to read value from export file (Data length (4) > Column definition (3)).

GenericLog GenericError 1 0 2010-10-12 03:37:11 Message: GEN-13, Additional Message: dict-ERR-1107: Unable to read row 0 from export file (UTLDataValRead pBuf, col 4 ).

GenericLog GenericError 1 0 2010-10-12 03:37:11 Message: Generated SQL statement:, Additional Message: SQLFetch:

SELECT IND.ROW_ID, IND.NAME, IND.ALIAS, IND.TBL_ID, IND.ISUNIQUE,
IND.USER_PR_KEY, IND.USER_NAME, IND.TYPE, IND.ISCLUSTERED,
TBL.TYPE, IND.ISCLUSTERED2, IND.ALLW_RVRS_SCAN_FLG, IND.NUM_UNIQUE_COLS,
IND.MODULE_NAME
FROM SIEBELPRD.S_INDEX IND, SIEBELPRD.S_TABLE TBL
WHERE IND.REPOSITORY_ID = (SELECT ROW_ID FROM SIEBELPRD.S_REPOSITORY WHERE NAME = ?)
AND TBL.ROW_ID = IND.TBL_ID
AND (TBL.INACTIVE_FLG = 'N' OR TBL.INACTIVE_FLG IS NULL)
AND (IND.INACTIVE_FLG = 'N' OR IND.INACTIVE_FLG IS NULL)
AND TBL.TYPE <> 'External'
AND TBL.TYPE <> 'External View'

GenericLog GenericError 1 0 2010-10-12 03:37:11 Message: Error: An ODBC error occurred, Additional Message: Function: DICGetIndexes; ODBC operation: SQLFetch

SQLTraceAll SQLTraceAll 4 0 2010-10-12 03:37:11 (SQLFreeStmt) Conn Handle: 65148304, Stmt Handle: 65156360, Time : 0s

SQLStatementOptions Free Statement 4 0 2010-10-12 03:37:11 (SQLFree Stmt) Conn Handle: 65148304, Stmt Handle: 65156360, Time: 0s

SQLStatementOptions Free Statement Details 5 0 2010-10-12 03:37:11 (SQLFreeStmt) Option: SQL_RESET_PARAMS

SQLTraceAll SQLTraceAll 4 0 2010-10-12 03:37:11 (SQLFreeStmt) Conn Handle: 65148304, Stmt Handle: 65156360, Time : 0s

SQLStatementOptions Free Statement 4 0 2010-10-12 03:37:11 (SQLFree Stmt) Conn Handle: 65148304, Stmt Handle: 65156360, Time: 0s

SQLStatementOptions Free Statement Details 5 0 2010-10-12 03:37:11 (SQLFreeStmt) Option: SQL_UNBIND

SQLTraceAll SQLTraceAll 4 0 2010-10-12 03:37:11 (SQLFreeStmt) Conn Handle: 65148304, Stmt Handle: 65156360, Time : 0s

SQLStatementOptions Free Statement 4 0 2010-10-12 03:37:11 (SQLFree Stmt) Conn Handle: 65148304, Stmt Handle: 65156360, Time: 0s

SQLStatementOptions Free Statement Details 5 0 2010-10-12 03:37:11 (SQLFreeStmt) Option: SQL_CLOSE

GenericLog GenericError 1 0 2010-10-12 03:37:11 Message: GEN-13, Additional Message: dict-ERR-1107: Unable to read row 0 from export file (UTLDataDelimRead).

GenericLog GenericError 1 0 2010-10-12 03:37:11 Message: GEN-10, Additional Message: Calling Function: DICLoadDict; Called Function: Calling DICGetIndexes

GenericLog GenericDetail 4 0 2010-10-12 03:37:11 Release shared lock for cache file D:\sea77\siebsrvr\bin\diccache.dat

SQLTraceAll SQLTraceAll 4 0 2010-10-12 03:37:11 (SQLFreeStmt) Conn Handle: 65148304, Stmt Handle: 65156360, Time : 0s

SQLStatementOptions Free Statement 4 0 2010-10-12 03:37:11 (SQLFree Stmt) Conn Handle: 65148304, Stmt Handle: 65156360, Time: 0s

SQLStatementOptions Free Statement Details 5 0 2010-10-12 03:37:11 (SQLFreeStmt) Option: SQL_DROP

SQLSummary Header 4 0 2010-10-12 03:37:11 *******************************************************************************

SQLSummary Stmt 4 0 2010-10-12 03:37:11

SELECT DB_SCHEMA_VER, DB_MINOR_VER, DB_MAINT_VER, CUSTOM_SCHEMA_VER, CUSTOM_DOCK_VER

FROM SIEBELPRD.S_APP_VER

SQLSummary Header 4 0 2010-10-12 03:37:11 Call Count Total Time Avg. Time Rows
SQLSummary Sep 5 0 2010-10-12 03:37:11 -------------------------------------------------------------------------------
SQLSummary ExecDir 5 0 2010-10-12 03:37:11 Exec Direct 1 0.016s 0.016s 0
SQLSummary Fetch 5 0 2010-10-12 03:37:11 Fetch 1 0s 0s 1
SQLSummary Sep 5 0 2010-10-12 03:37:11 -------------------------------------------------------------------------------
SQLSummary Totals 4 0 2010-10-12 03:37:11 Total 2 0.016s 0.008s 1

EIMTrace EIMTraceSubEvent 3 0 2010-10-12 03:37:11 10/12/10 3:37 Error 205: Failure in DICLoadDict. Unable to load dictionary!

EIMError EIMErrorSubEvent 0 0 2010-10-12 03:37:11 Error 205: Failure in DICLoadDict. Unable to load dictionary!

EIMTrace EIMTraceSubEvent 3 0 2010-10-12 03:37:11 10/12/10 3:37 Error 205: Failed to load the application dictionary.

EIMError EIMErrorSubEvent 0 0 2010-10-12 03:37:11 Error 205: Failed to load the application dictionary.

EIMTrace EIMTraceSubEvent 3 0 2010-10-12 03:37:11 > Loading Siebel dictionary 1s

GenericLog GenericError 1 0 2010-10-12 03:37:11 (compmain.cpp (1558) err=100205 sys=0) SBL-EIM-00205: Failed to load the application dictionary.

GenericLog GenericError 1 0 2010-10-12 03:37:11 (smisched.cpp (830) err=100205 sys=0) SBL-EIM-00205: Failed to load the application dictionary.

SQLTraceAll SQLTraceAll 4 0 2010-10-12 03:37:11 (SQLFreeStmt) Conn Handle: 65148304, Stmt Handle: 65153112, Time : 0s

SQLStatementOptions Free Statement 4 0 2010-10-12 03:37:11 (SQLFree Stmt) Conn Handle: 65148304, Stmt Handle: 65153112, Time: 0s
CAUSE
This is caused due to the incorrect ODBC registry entries.

SOLUTION
The ODBC registry entries for Siebel Server data source did not contain the "EnableNCharSupport". After creating this entry and set the value to '0' and rename the diccache.dat, EIM job ran successfully.

SBL-EIM-00206 Failed to run initial process.

APPLIES TO:
Siebel Enterprise Integration Manager - Version 7.8.2.3 SIA [19221] and later
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.8.2.3 [19221] Com/Med
Database: IBM DB2 8.2
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: IBM AIX 5L 5.2

SYMPTOMS
SBL-EIM-00206

We are running the same EIM loading scripts and IFB files (and same EIM command lines) across environments. Every environment runs fine except one of them.

It gives this error.
SBL-EIM-00206: Failed to run initial process

We've checked and made sure that the password of the job is correct. ODBC on the server runs fine. We tried to turned on more tracing but unfortunately we couldn't get more details other than the ones attached. Are there any other reasons for the failing?

CAUSE
Configuration/ Setup

SOLUTION
Message 1
For the benefit of other users:

The reported behaviour was because of missing "USERNAME" and "PASSWORD" parameters in the header section of the IFB-File used for the EIM task.

Reference: Siebel Bookshelf, EIM Administration Guide, Header Section Parameters Generic to All EIM Processes, Table 6: General Header Parameters for the EIM Configuration File.

SBL-EIM-00207 Unable to log in to the database.

SBL-EIM-00207: Unable to log in to the database

APPLIES TO:
Siebel Enterprise Integration Manager - Version 7.7.2.8 [18379] to 8.2.2 SIA[22320] [Release V7 to V8]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Professional)
Version: 7.7.2.8 [18379]
Database: Microsoft SQL Server 2000 SP4
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Microsoft Windows 2000 Server SP 4
SYMPTOMS
We use EIM to upload customer information for benefit eligibility purposes. We are starting to see this error:SBL-EIM-00207: Unable to log in to the database.

Here are the errors:

1.
EIMError EIMErrorSubEvent 0 0 2007-04-13 14:26:09 Error 107: ODBC error 28000:

EIMError EIMErrorSubEvent 0 0 2007-04-13 14:26:09 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'SADMIN'.
EIMError EIMErrorSubEvent 0 0 2007-04-13 14:26:09 Error 207: Unable to log in to the database.

GenericLog GenericError 1 0 2007-04-13 14:26:09 (compmain.cpp (1558) err=100207 sys=0) SBL-EIM-00207: Unable to log in to the database.

2.
GenericLog GenericError 1 0 2007-04-15 21:52:42 (compmain.cpp (1558) err=100108 sys=0) SBL-EIM-00108: Internal error in retrieving scf parameter

Some customers who got error SBL-EIM-00108 when starting EIM task from GUI can successfully starting EIM task from srvrmgr command line.

I have verified the username and password and we are able to login via ODBC just fine. We have the username password in our IFB file as well as at the component level (identical)

I tried to look it up on SupportWeb and saw SR# 38-1638406931 which has the same symptom. However the result in this SR is not the problem.

Even though it is the test environment, we cannot update Production until we have verified in our Test environment.

I will attache the EIM log file and the IFB file.

CAUSE
The issue is caused by wrong setup.

SOLUTION

This issue is resolved after changing the parameters of the default user using srvrmgr via command line and restart the Gateway and Siebel Servers.

Impressum und Datenschutz Copyright ©2020 eir.me
Siebel Articles Python Perl 5 Documentation Manuel PHP7 français
Java Das PHP7 Handbuch PHP7 Manual English Linux and Unix News