ABAP Consumer Proxy error after upgraded from 7.0 SP14 to 7.01 SP3

[Former Member]

The ABAP consumer proxy was created in ECC6 with Netweaver 7.0 SP14. After the system was upgraded to Netweaver 7.01 SP3 the proxy call started to get error back.

The first error message from the service provider said "SoapException: Server did not recognize the value of HTTP Header SOAPAction". This error was resolved by manually putting the correct action in the SOAManager configuration.

Ran the same test again and then the service provider complained about the To field in the SOAP Header. The error message said "SoapHeaderException: SOAP header To was not understood".

Below is the To field in the Requesting XML message from the 7.0 SP14 system that worked fine:

<n3:To soap-env:mustUnderstand="1" xmlns:n3="http://schemas.xmlsoap.org/ws/2004/08/addressing" 
xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope">
<a href="http://localhost:50081/AddSix.asmx" TARGET="test_blank">http://localhost:50081/AddSix.asmx</a>
</n3:To>

Below is the To field in the Requesting XML message from the 7.01 SP3 system that did not work:

<wsa:To soap-env:mustUnderstand="1" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" 
xmlns:soap-env="http://www.w3.org/2003/05/soap-envelope">
<a href="http://localhost:50081/AddSix.asmx" TARGET="test_blank">http://localhost:50081/AddSix.asmx</a>
</wsa:To>

It looks like the issue is with the xmlns:soap-env element that has different values in these two systems. Searched in SDN but could not find any related information. Please help if anyone has experienced similar issue or knows how to fix it.

Thanks,

Jiannan

[Former Member · Accepted solution]

Hi,

Please check OSS note Note 1333830.

Thanks,

Sridhar

[Former Member]

Solution provided by SAP thru OSS message.

[Former Member]

SAP has also created OSS note 1361688 as the resolution to this issue.

[Former Member]

Got solution from SAP through an OSS message. Below is SAP's solution:

Either the Message ID protocol should be switched off on the SAP
consumer side or turn on this protocol support on the .NET provider.
To switch off the Message ID protocol:
1. start the soa manager
2. find the consumer proxy
3. find the corresponding logical port
4. jump to the 'Messaging' tab
5. choose the 'Suppress ID Transfer' from the dropdown list of the Message ID Protocol field

Besides this setting I also have to specify the operation in the Operation specific tab of the logical port configuration.

[Former Member]

Hi Sridhar,

The note looked promising but it did not solve the problem. I have applied the note,

regenerated the proxy, recreated the logical port, and reactivated the

test program. It still got the same error. Please let me know if I missed anything. Thanks.

Regards,

Jiannan

[Former Member]

The below links could be of your interest. Please check.

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c02359e5-4732-2c10-0aad-f48fc711...

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/3b28e590-0201-0010-968f-e10ed532...

Thanks,

Sridhar

[Former Member]

Hi,

I am getting the same error, please let me know if your issue was solved.

Thanks,

Simmi