Home > BizTalk, WCF > Issue: Received unexpected message type ‘http://www.w3.org/2003/05/soap-envelope#Fault’ does not match expected type ‘http://abhijit/WCF/06/2011#Operation1’

Issue: Received unexpected message type ‘http://www.w3.org/2003/05/soap-envelope#Fault’ does not match expected type ‘http://abhijit/WCF/06/2011#Operation1’

Generally we encounter this issue when we try to consume a WCF Service with Custom Fault Contract from BizTalk. To circumvent this issue, check the WCF-Transport configuration settings of the Send port.

Select the xPath option under the inbound BizTalk message body and set the Body path expression to /*[local-name()=’Fault’]/*[local-name()=’detail’]/* | /*[local-name()=’Operation1Response’] | /*[local-name()=’Operation2Response’]

In the above xPath expression, I have used the union operation for multiple responses. So, if BizTalk receives the fault message then the Custom Fault will be extracted from /Fault/Detail path and when there is no fault then the successful response message will be forwarded to the orchestration.

Advertisements
Categories: BizTalk, WCF
  1. May 28, 2013 at 1:09 am

    Thank you for some other informative website. The place
    else could I get that kind of info written in such an ideal way?
    I have a mission that I am just now running on, and I’ve been on the glance out for such information.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: