Originally posted on: http://geekswithblogs.net/RobBowman/archive/2013/11/29/received-unexpected-message-type.aspx
Starting new year's resolution early - two blog posts in one day!
After receiving a response from a WCF solicit response port, my orchestration was raising the following exception:
Inner exception: Received unexpected message type '' does not match expected type 'http://xxx/dynamics/2013/03/services#EXDSalesLineShippingServiceFindResponse'
I updated the BizTalk config to trace the received WCF message. It looked ok, had expected namespace and root node.
Problem was, I'd forgotten to set the receive pipeline of the physical two way send port to XML Receive - it was sat at PassThruReceive. This meant that the message type wasn't getting promoted. Because the receive on my orchestration's logical solicit response port was strongly typed - it threw the exception.
