Uncaught exception (see the ‘inner exception’ below) has suspended an instance of service ‘MyApp.Common.BizTalk.Artifacts.HandleCommonErrors(4e50ec54-338d-1887-a441-2dc31c830952)’.
The service instance will remain suspended until administratively resumed or terminated.
If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.
Exception thrown from: segment -1, progress -1
Inner exception: Received unexpected message type ” does not match expected type ‘http://MyApp.Common.BizTalk.Artifacts/Config#ConfigResp’.
Exception type: UnexpectedMessageTypeException
Target Site: Void VerifyMessage(Microsoft.XLANGs.Core.Envelope, System.String, Microsoft.XLANGs.Core.Context, Microsoft.XLANGs.Core.OperationInfo)
The following is a stack trace that identifies the location where the exception occured
Change Send Port ReceivePipeline to XMLReceive instead of PassThru.
BizTalk could not parse the XML without the XMLRecieve pipeline.
Update on 08/31/2016:
This happened to me again. I had a solution with multiple projects, and every time I did a deploy, the SendPort was getting reset. I’m not 100% sure why, but the way I fixed that was to go to the Solution itself, and turn off the deploy of the common module. I must have had a pipeline or something that was causing the SendPort to be modified each time I deployed.
Filed under: SQL