November 2013 Entries

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/0... 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 ......

Multiple Orchestration Instances

Had a funny problem with BizTalk today that I thought worth blogging about in case anyone else makes the same mistake. I have the following setup: File Receive Port (map to canonical) --> Orchestration --> Send Port (map to external) After deploying with the BizTalk Deployment Framework I kicked off an integration test which dropped a single record flat file in the receive location. The send port did its thing and all looked good. Then I noticed many (and I mean many!) messages were being sent. ......