My Oracle Support Banner

Gateway Sends SOAP 1.2 Messages, But Client Requires SOAP 1.1 Reporting The " Couldn't create SOAP message" Error (Doc ID 1585645.1)

Last updated on JULY 20, 2021

Applies to:

Oracle API Gateway - Version and later
Information in this document applies to any platform.


A SOAP 1.1 client connects to the Gateway.

The following error is observed on the client

#### <> <> Couldn't create SOAP message. Expecting Envelope in namespace, but got

The Gateway's trace file, at trace level DATA, shows:

ERROR <TIMESTAMP> [<THREAD ID>] Service Handler for '<SERVICE NAME>' filter failed
DEBUG <TIMESTAMP> [<THREAD ID>] run filter [Call 'Global Exception Handler'] {
DEBUG <TIMESTAMP> [<THREAD ID>] run circuit "Global Exception Handler"...
DEBUG <TIMESTAMP> [<THREAD ID>] run filter [Set Exception Message] {
DEBUG <TIMESTAMP> [<THREAD ID>] The content type of the converted message is text/xml
DATA <TIMESTAMP> [<THREAD ID>] The converted message is <?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="">
                 <env:Value xmlns:fault="http://www.<company.domain>/soapfaults">
                    [invalid field]
    [invalid field]
             <env:Text lang="en">
                Your request failed. Contact the administrator with the following code : Id-12345678



To view full details, sign in with your My Oracle Support account.

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

In this Document
Additional Information

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