Consumer Client Proxy for multi-operation Web Service [PROBLEM]

Former Member — Tue, 23 Dec 2014 14:48:42 GMT

Hello everyone,

I created a client proxy and a logical port for multi-operation Microsoft WCF service. Everything was ok with the generation.

When I call an operation with a particular logical port, I get the LO_SYS_EXCEPTION :

SoapFaultCode:1 The message with Action 'http://tempuri.org/DispatchAppointmentsLogin' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).

I introduce the same wsdl in SOAP UI and I get connection to the service. Also, when I call .asmx services from SAP everything works fine.

I understand that the problem is caused due to a name-binding mismatch. Do I need to define a different access path for every operation or make custom settings?

Any ideas?

Thank you and Regards,

Kostas

Re: Consumer Client Proxy for multi-operation Web Service [PROBLEM]

Former Member — Wed, 14 Sep 2016 15:25:42 GMT

This message was moderated.

topic Consumer Client Proxy for multi-operation Web Service [PROBLEM] in Application Development and Automation Discussions

Consumer Client Proxy for multi-operation Web Service [PROBLEM]

Re: Consumer Client Proxy for multi-operation Web Service [PROBLEM]