Siebel EAI >  SBL-EAI-00133 EAI Common Internal Error: %1

SBL-EAI-00133 EAI Common Internal Error: %1

APPLIES TO:
Siebel CRM - Version 8.1.1.11 [IP2013] and later
Information in this document applies to any platform.
""Checked for Relevance on 11-Aug-2016""
SYMPTOMS
SIEBEL VERSION:
Siebel version : 8.1.1.11
Database version : Oracle 11.2.0.2
OS version : Oracle Linux 5

ISSUE STATEMENT:
Error is reported when executing an inbound web service (based on a Workflow Process) :-

Completed inbound web service
(operation.cpp (1115)) SBL-EAI-00133: EAI Common Internal Error : ?

This is an environment upgraded to 8.1.1.11 from 8.1.1.3 SIA (there was no error at the previous version).

ERROR:
(operation.cpp (1115)) SBL-EAI-00133: EAI Common Internal Error : ?

CAUSE
With Siebel 8.1.1.11, if there is a non-empty 'Error Message' property in the output of the Workflow Process, it generates this error and results in a soap fault, for example :-

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>EAI Common Internal Error: Some custom error !(SBL-EAI-00133)</faultstring>
<detail>
<siebelf:siebdetail xmlns:siebelf="http://www.siebel.com/ws/fault">
<siebelf:logfilename>EAIObjMgr_enu_0046_48234506.log</siebelf:logfilename>
<siebelf:errorstack>
<siebelf:error>
<siebelf:errorcode>SBL-EAI-00133</siebelf:errorcode>
<siebelf:errorsymbol/>
<siebelf:errormsg>EAI Common Internal Error: Some custom error !(SBL-EAI-00133)</siebelf:errormsg>
</siebelf:error>
</siebelf:errorstack>
</siebelf:siebdetail>
</detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

SOLUTION
Ensure Error Message is not populated at Workflow Process completion. If the Workflow is deemed to have finished 'successfully' it should not result in a soap fault.

A bug was logged to request the ability to control whether a populated Error Message should result in a soap fault :-

BUG 18174767 - SBL-EAI-00133: EAI COMMON INTERNAL ERROR IF WORKFLOW 'ERROR MESSAGE' NOT EMPTY

The solution going forward will be, if there is a 'FaultOnError' Process Property defined in the invoked Workflow, then if the Error Message is populated, a soap fault will be thrown. But if the 'FaultOnError' Process Property does not exist in the Worklfow Process, the the previous behaviour will persist, i.e. a normal SOAP response. This solution is scheduled to be implemented at 8.1.1.11.7 (i.e. Patchset 7 on 8.1.1.11) and higher maintenance releases.

The mentioned bug is listed as addressed at the following versions :-

8.1.1.11.7 / 8.2.2.4.7 and higher patchsets
8.1.1.14 / 8.2.2.14 and later maintenance releases