Consider the following scenario:

  • You create an orchestration in Microsoft BizTalk Server 2013 R2 or in Microsoft Host Integration Server 2013.

  • You use a correlation type that specifies the BizTalk_CorrelationID context property that's provided by MQSeries.dll.

  • You try to process a message.

In this scenario, you receive the following routing failure error message:

The Messaging engine failed to process a message submitted by adapter:MQSC Source URL:MQSCURL. Details:The published message could not be routed because no subscribers were found. This error occurs if the subscribing orchestration or send port has not been enlisted, or if some of the message properties necessary for subscription evaluation have not been promoted. Please use the BizTalk Administration console to troubleshoot this failure.


This problem occurs because the orchestration creates the correlating instance subscription at runtime by using the TransactionSupported property instead of BizTalk_CorrelationID.


This problem was fixed in the following cumulative updates:

Cumulative update information

For BizTalk Server 2013 R2

Cumulative update package 1 for BizTalk Server 2013 R2

For Host Integration Server 2013

Cumulative Update 3 for Host Integration Server 2013


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


For more information about the service packs and cumulative update list for BizTalk Server, see KB 2555976: Service pack and cumulative update list for BizTalk Server.

For more information about BizTalk Server hotfixes, see KB 2003907: Information about BizTalk hotfixes and cumulative update support.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!