‘unknown system exception’ error when working with orchestrations

Every now and then I run into the most annoying of BizTalk errors – ‘unknown system exception’ – when working with orchestrations. Sometimes this would be fixed by a restart of Visual Studio, but today I hit the problem and it just wouldn’t go away.

It seems this error can occur if you have unreachable Call Orchestration shapes in your orchestration. Specifically if you have a Decide shape where the conditions are hardcoded boolean literals. For example if one branch has the condition ‘true’ and the other branch is never reached, but the other branch contains a Call Orchestration shape. I often do this kind of thing when working on an orchestration, if I’m putting together the flow but haven’t yet worked through the logic.

 I can only presume that compilation is attempting to optimise away the other loop, but getting in a twist somewhere along the way. Nevertheless it’s easily fixed by replacing the literal with a boolean variable.


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 )

Google+ photo

You are commenting using your Google+ 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 )


Connecting to %s

%d bloggers like this: