Siebel EIM >  EIM Error SBL-EIM-00423: Unable to get Audit Trail columns

EIM Error SBL-EIM-00423: Unable to get Audit Trail columns

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

SYMPTOMS
On : 8.2.2.4 SIA [23030] version, EIM

When attempting to import Contacts, the following error occurs.

ERROR
-----------------------

GenericLog GenericError 1 0009ed2059810a58:0 2017-08-06 17:04:00 Message: GEN-10,
Additional Message: Calling Function: UTLDLogGetAuditColumns; Called Function: GetAuditColumns

EIMError EIMErrorSubEvent 0 0009ed2059810a58:0 2017-08-06 17:04:00

EIMError EIMErrorSubEvent 0 0009ed2059810a58:0 2017-08-06 17:04:00 -------------------------------------------------------------------------------

EIMError EIMErrorSubEvent 0 0009ed2059810a58:0 2017-08-06 17:04:00

EIMError EIMErrorSubEvent 0 0009ed2059810a58:0 2017-08-06 17:04:00 Error SBL-EIM-00423: Unable to get Audit Trail columns for S_PARTY

EIMError EIMErrorSubEvent 0 0009ed2059810a58:0 2017-08-06 17:04:06 A low-level error occurred during import processing for this table. The error

EIMError EIMErrorSubEvent 0 0009ed2059810a58:0 2017-08-06 17:04:06 could not be handled during the step in which it occurred and caused all import

EIMError EIMErrorSubEvent 0 0009ed2059810a58:0 2017-08-06 17:04:06 processing for that table to stop.

EIMError EIMErrorSubEvent 0 0009ed2059810a58:0 2017-08-06 17:04:06

EIMError EIMErrorSubEvent 0 0009ed2059810a58:0 2017-08-06 17:04:06 This low-level failure caused all processing to halt for the specified

EIMError EIMErrorSubEvent 0 0009ed2059810a58:0 2017-08-06 17:04:06 interface table. Check the error messages for more information.

CHANGES

EnableEimAuditing (Administration - Application--> System Preferences view) Controls auditing for EIM was changed.

CAUSE
Root cause unknown as a DB Level troubleshooting was not done.

SOLUTION
Administration - Application screen --> System Preferences view : EnableEimAuditing—Controls auditing for EIM. This preference is false by default. As there was a clear suspicion on the Audit trail from the error message, it was found that this parameter was changed recently in their environment to True. Reverting back to false, fixed the issue.