Inbound SOAP Message Having '&' Then XML Parsing Failed Error When Invoking Siebel Webservices (Doc ID 2657078.1)

Last updated on JUNE 23, 2023

Applies to:

Symptoms

When attempting to call the Inbound Web service to Siebel from Source system and request pay load having the '&' then Interface is failing with the following errors in SWSE logs.

Example: <Name>TEST & DATA</Name>

ERROR
-----------------------
ProcessPluginRequest ProcessPluginRequestError 1 000015ff5e336593:0 2020-01-31 05:03:08 Fatal Error at line : 1 char : 1583, Message : An exception occurred! Type:RuntimeException, Message:Could not open external entity ''
ProcessPluginRequest ProcessPluginRequestError 1 000015ff5e336593:0 2020-01-31 05:03:08 390: [SWSE] Failed to obtain a session ID. nbound SOAP Message - XML parsing failed, %1
ProcessPluginRequest ProcessPluginRequestError 1 000015ff5e336593:0 2020-01-31 05:03:08 Error Message: Error: nbound SOAP Message - XML parsing failed, Fatal Error at line : 1 char : 1583, Message : An exception occurred! Type:RuntimeException, Message:Could not open external entity '' Error ID : 10944643
ProcessPluginRequest ProcessPluginRequestError 1 000016005e336593:0 2020-01-31 05:03:08 386: [SWSE] Failed to obtain a session ID. Inbound SOAP Message - Session Token is missing or invalid or has expired
ProcessPluginRequest ProcessPluginRequestError 1 000016005e336593:0 2020-01-31 05:03:08 Error Message: Error: Inbound SOAP Message - Session Token is missing or invalid or has expiredError ID : 10944642
SisnapiLayerLog Error 1 000016015e336593:0 2020-01-31 05:03:08 672: [SISNAPI] Async Thread: connection (0x6b95448), error (1180682) while reading message

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.