Siebel EIM >  EIM File Import error SBL-EIM-00900

EIM File Import error SBL-EIM-00900

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

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 information.
SBL-SVR-01042: Internal: Communication protocol error while instantiating new task

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.

In customer’s scenario there can be attachment files physically missing from siebsrvr\input, 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.