Siebel Inbound Web Service With Inline Base-64 Attachment IC Content Fails With Error "Type:UTFDataFormatException, Message:invalid byte 2 (ë) of a 2-byte sequence" When SOAPUI Request Properties Has "Enable MTOM" = True

(Doc ID 2349335.1)

Last updated on JANUARY 16, 2018

Applies to:

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

Symptoms

PRODUCT VERSIONS:
------------------------------
SIEBEL VERSION: Siebel 8.1.1.11.17 [IP2013]
SIEBEL APP O/S: IBM AIX on POWER Systems (64-bit)

ISSUE STATEMENT:
----------------------------
When sending a message into Siebel with an activity and attachment IC, the Siebel application should create the activity and attachment record with the incoming attachment content in inline base64.

However, the request fails with an error instead.

ERROR MESSAGE:
--------------------------
The error message that occurs with this issue is:

Error: Inbound SOAP Message - XML parsing failed, Fatal Error at line : 1 char : 1, Message : An exception occurred! Type:UTFDataFormatException, Message:invalid byte 2 (ë) of a 2-byte sequence.

STEPS TO REPRODUCE:
---------------------------------
The behaviour occurs as follows:

1. Use the vanilla ActivityWS web service, generate WSDL for it and import the WSDL into soapui.

2. Use soapui to send an inbound message with an activity and attachment content in inline base64.

3. Send the request into Siebel, the request fails and returns the reported error to soapui response window.

LOSS OF FUNCTIONALITY / BUSINESS IMPACT:
--------------------------------------------
Due to error, the activity and attachment was not created in the Siebel application.

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms