Consider the following scenario:

  • You are using Microsoft BizTalk Server.

  • You have a two-way send port that uses the Windows Communication Foundation (WCF)-based SQL adapter to connect BizTalk applications to an instance of Microsoft SQL Server.

  • The WCF-SQL two-way send port is bound to an orchestration.

  • The send port calls a stored procedure to send messages to the instance of SQL Server.

In this scenario, when you have many messages to process, you may intermittently receive the following error message that states that the process failed and "no subscribers were found":

The Messaging engine failed to process a message submitted by adapter: WCF-Custom Source URL:FilePath.

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 is fixed in the following cumulative update for BizTalk Server:

       Cumulative Update 4 for BizTalk Server 2016

       Cumulative Update 7 for BizTalk Server 2013 R2


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


For information about the service packs and cumulative update list for BizTalk Server, go to the following article in the Microsoft Knowledge Base:

2555976 Service pack and cumulative update list for BizTalk Server

For more information about BizTalk Server hotfixes, go to the following article in the Microsoft Knowledge Base:

2003907 Information about BizTalk hotfixes and Service Pack support

Need more help?

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

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!