SBL-SVR-01042: Internal: Communication protocol error

Applies to:

Siebel Reports - Version 7.7.2.10 SIA [18385] and later
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Professional)
Version: 7.8.2.3 [19221]
Database: Oracle 9.2.0.8
Application Server OS: Sun Solaris 10
Database Server OS: Sun Solaris 10

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

Symptoms

SBL-SVR-01042, SBL-SMI-00121
Hi,

After applying the patch 7.8.2.5, the report server is Not working. I have attached the log file for your reference. Please take a look at this and advice soon. Below is the error.

(sasess.cpp (711) err=2001042 sys=0) SBL-SVR-01042: Internal: Communication protocol error while instantiating new task SBL-SMI-00121: Internal: SISDecodeRawMessage() failed

Cause

Configuration/ Setup

Solution

Message 1

Description
Hi,

After applying the patch 7.8.2.5, the report server is Not working. I have attached the log file for your reference. Please take a look at this and advice soon. Below is the error.

(sasess.cpp (711) err=2001042 sys=0) SBL-SVR-01042: Internal: Communication protocol error while instantiating new task SBL-SMI-00121: Internal: SISDecodeRawMessage() failed

Thanks,

For the benefit of other readers:

The customer applied the patch 7.8.2.5 and the report server was not working. After restart the HTTP Service and kill the old process that was running the reports started to work fine.

Applies to:

Siebel Financial Services CRM - Version 8.1.1 SIA [21111] and later
Information in this document applies to any platform.
***Checked for relevance on 05-Feb-2013***

Symptoms

When attempting to start multiple EIM tasks the following error occurs:

SBL-SVR-01042: Internal: Communication protocol error while instantiating new task.
SBL-SVR-09127: Internal: Fail to initialize the shared memory resource for the process.
SBL-SVR-09124: Internal: Cannot allocate shared memory resource for the current process. Most likely we have reached the maximum number of processes.

From ServerMgr_xxx.log:
GenericLog GenericError 1 000000084b2f113c:0 2009-12-21 16:40:38 (sciapi.cpp (1130) err=1311762 sys=0)
SBL-SVR-01042: Internal: Communication protocol error while instantiating new task.
SBL-SVR-09127: Internal: Fail to initialize the shared memory resource for the process.

From Enterprise log(<Enterprise Server>.<Siebel Server>.log):
ServerLog ProcessExit 1 000019474b2f1598:0 2009-12-21 16:40:41 <NoCompName> 4712 SBL-SVR-09127 Process 4712 exited with error - Internal: Fail to initialize the shared memory resource for the process.

Cause

This error occurs when EIM tasks reaches to the MaxTasks.

Solution

Set an appropriate MaxTasks value for EIM component.

For example:
srvrmgr> change param maxtasks=<value> for comp eim

Applies to:

Siebel Enterprise Integration Manager - Version 8.0.0.5 SIA [20420] and later
Information in this document applies to any platform.
""""Checked for relevance on 28-Sep-2011""""

Symptoms

Statement of what the issue is
Version: 8.0.0.5 SIA [20420]

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.

Applies to:

Siebel Enterprise Integration Manager - Version 7.7.2 [18325] to 8.1.1.9 [23016] [Release V7 to V8]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.7.2 [18325]
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Microsoft Windows 2000 Server SP 4

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

Symptoms

SBL-EIM-00900
During our EIM import of file into Siebel, we encounter this error.

I've verified that all files have already been compressed and moved to the Siebel FIle System. However, the process still errors out with this message.

Process [Import Agreement Attachment] had all rows fail on EIM_AGREE_DTL for batch 2 in step 9, pass 112:      Import processing aborted due to internal error. (severity 1, table aborted)     A low-level error occurred during import processing for this table. The error     could not be handled during the step in which it occurred and caused all import     processing for that table to stop.     This low-level failure caused all processing to halt for the specified     interface table. Check the error messages for more information.

Please see attached EIM log.

Cause

Configuration/ Setup

Solution

Customer used EIM_AGREE_DTL to import agreement attachments. The EIM task aborted midway without finishing processing all records in EIM table and without giving any clues in the log for the reason it failed.   This isn’t expected behavior because EIM usually errors out the record that fails to be process and moves on to process the next row until it finishes processing all rows.   In EIM log, there are these errors:

EIMTrace    EIMTraceSubEvent    3    0    2005-03-23 14:35:25    Attachment Not Found: D:\sea77\siebsrvr\input\aextract_445_MAINT_RENEWAL_34024_Deactivation_E-mail.MSG

EIMError    EIMErrorSubEvent    0    0    2005-03-23 14:35:40    Error 900: Unknown failure running process [Import Agreement Attachment]!

GenericLog    GenericError    1    0    2005-03-23 14:35:40    (compmain.cpp (1558) err=100900 sys=2) SBL-EIM-00900: Error running EIM process. See the error trace for more information.


The "Attachment Not Found" error means the attachment to be imported is not in siebsrvr\input physically. Or if the FILE_EXT is not populated correctly, e.g., the filename is My_Email_Message.msg but you use doc for FILE_EXT instead of msg. The behavior of EIM with this error is it gives "Attachment Not Found" error on that particular attachment but won't fail the task and continue to process the next record.
For example, there are 24 records in EIM table, the 10th one fails with this error, and EIM ends up importing 23 records successfully, the error one isn’t imported. So the "Attachment Not Found" error won't cause EIM to abort.

What caused EIM to abort is improper permission on attachment file. For example, on Windows the following Security:

Full Control            Deny
Modify                    Deny
Read & Execute      Deny
Read                        Deny
Write                      Deny

As soon as EIM tries to process such an attachment, it can't handle it and aborts with the following Status:

SBL-EIM-00900: Error running EIM process. See the error trace for more informat
ion.
SBL-SVR-01042: Internal: Communication protocol error while instantiating new ta
sk

And this error in EIM log:
EIMError    EIMErrorSubEvent    0    0    2005-04-14 11:49:10     Import processing aborted due to internal error. (severity 1, table aborted)
EIMError    EIMErrorSubEvent    0    0    2005-04-14 11:49:10    
EIMError    EIMErrorSubEvent    0    0    2005-04-14 11:49:10    A low-level error occurred during import processing for this table. The error
EIMError    EIMErrorSubEvent    0    0    2005-04-14 11:49:10    could not be handled during the step in which it occurred and caused all import
EIMError    EIMErrorSubEvent    0    0    2005-04-14 11:49:10    processing for that table to stop.
EIMError    EIMErrorSubEvent    0    0    2005-04-14 11:49:10    This low-level failure caused all processing to halt for the specified
EIMError    EIMErrorSubEvent    0    0    2005-04-14 11:49:10    interface table. Check the error messages for more information.

The result is 16 files out of 24 got imported.

So, in customer’s scenario there can be attachment files physically missing from siebsrvr\input and incorrectly populated FILE_EXT and improper permissions, but what really caused EIM to abort in the midway is the attachment files with improper permissions. If you correct the permissions such as changing the above permissions under Security to Allow (have Allow checked), then EIM imports successfully.

The Enhancement Request # 10495429 has been raised for EIM to give some clues for the actual error causing the abort, because it is very difficult to troubleshoot when EIM log also contains "Attachment Not Found" error which isn’t the real cause of the abort.

Applies to:

Siebel Enterprise Integration Manager - Version: 7.7.2.5 SIA [18368] to 8.1.1.2 SIA[21215] - Release: V7 to V8
Information in this document applies to any platform.

Symptoms

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.

IFB-File used:
----------------

[Siebel Interface Manager]
USER NAME = "SADMIN"
PASSWORD = "SADMIN"
PROCESS = Export


[Export]
TYPE = EXPORT
BATCH = 99
TABLE = EIM_CON_DTL
ATTACHMENT DIRECTORY = C:\temp
EXPORT MATCHES = S_CONTACT, (PERSON_UID = '1-2PGD')

Cause

The following extract of the resulting EIM-Log file is relevant in this regard:

UPDATE IT
SET IT.CON_BI = BT.BU_ID,
IT.CON_PERSON_UID = BT.PERSON_UID,
IT.CON_PRIV_FLG = BT.PRIV_FLG
, CON_PRIV_FLG = BT.PRIV_FLG
FROM dbo.EIM_CON_DTL IT, dbo.S_CONTACT BT
WHERE (BT.ROW_ID = IT.T_CONTACTTN_PARROW AND
T_CONTACTTN_PARROW IS NOT NULL AND
IF_ROW_BATCH_NUM = ?)

and error message:

[Microsoft][ODBC SQL Server Driver][SQL Server]Column name 'CON_PRIV_FLG' appears more than once in the result column list.
OR
[Microsoft][SQL Native Client][SQL Server]The column name 'CON_PRIV_FLG' is specified more than once in the SET clause. A column cannot be assigned more than one value in the same SET clause. Modify the SET clause to make sure that a column is updated only once. If the SET clause updates columns of a view, then the column name 'CON_PRIV_FLG' may appear twice in the view definition.

The matter has been reproduced

Solution

Although the EIM export task errored out the attachment was exported to the folder specified in the ATTACHMENT DIRECTORY IFB-parameter and the IF_ROW_STAT column of the EIM_CON_DTL table had a value of EXPORTED.

Product Defect 12-1OFLUGT has been raised to address the matter. 

Applies to:

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

Symptoms

SUMMARY

After enabling user password hashing, EIM jobs fail with an error when run from Server Manager command-line utility (SRVRMGR). Running EIM jobs via the Server Administration screens in a Web client works without error.

ERRORS

SBL-ADM-60070: Error reported on server 'crmsapqa' follows:
SBL-SVR-01042: Internal: Communication protocol error while instantiating new task SBL-EIM-00207: Unable to log in to the database.

Cause

The EIM job started via the Server Manager command-line is using the username and password you use to login to SRVRMGR.
Please refer to Siebel Bookshelf version 8.1 > Siebel Enterprise Integration Manager Administration Guide > EIM Configuration File > Defining EIM Configuration File Parameters > Header Section Parameters Generic to All EIM Processes - under PASSWORD parameter, where it states, * If you start EIM from the command line, it uses the username and password you used to log into the srvrmgr. * If you start EIM from the Siebel application, EIM looks for the username and password in the EIM Server Component parameters first, and if they are not specified, EIM then looks in the .IFB file. If EIM cannot find the username and password in those places, EIM cannot log into the database and it fails.

Solution

From Siebel Server Manager command-line run the following command - for example

srvrmgr> run task for component eim with config=C:\sia81\siebsrvr\ADMIN\test.ifb, password="s3S9CuVlW8POdxTjat/nMXCNJU4="