Received unexpected message type ''

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.

Print | posted on Friday, November 29, 2013 12:21 PM


# re: Received unexpected message type ''

left by Clare Leach at 5/8/2014 1:49 PM Gravatar
It's not often you google an error message from BizTalk and find the exact answer straight away! Thank you very much

# re: Received unexpected message type ''

left by Dinesh Gadewal at 11/25/2014 12:19 AM Gravatar
Thanks for this post.
Saved my time to resolve the same issue !

Keep Writing :)

# re: Received unexpected message type ''

left by Andreas at 9/3/2015 9:25 AM Gravatar
Good one - thanks!

# re: Received unexpected message type ''

left by Neal Walters at 2/9/2016 3:52 PM Gravatar
Thanks. I got this error today. In my case, I had redeployed a .DLL, and recycled the Orchestration Host Instance, but not the SendPort Host Instance. So the two were out of sync.
Post A Comment