Search code examples
wcfroutesbiztalkbiztalk2006r2

Routing error - No subscribers were found. WCF-SQL Adapter

I'm attempting to call a Stored proc, get some data back, map that to the desired schema, output the result.

However, I'm getting the following error:

The Messaging engine failed to process a message submitted by adapter:WCF-SQL Source URL:mssql://master-biztalk//ReportServer?InboundId=batman. 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.

I'm not quite certain why I'm getting this error. Searching the web hasn't enlightened me any further. Following are some of the steps I've undertaken

  1. Consume adapter = generated schema.
  2. Map this schema to desired output.
  3. Receive port in the Orchestration which connects to a receive message which has the Schema generated by the consume adapter as the type.
  4. Added a receive port in Biztalk, configured WCF-SQL and setup bindings. (Typed polling)
  5. Linked this receive port to the logical receive port in orchestration.
  6. I haven't promoted any elements in messages.

Thanks for the help

EDIT: I updated the pipeline to XML, and now I'm getting the following error:

There was a failure executing the receive pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "XML disassembler" Receive Port: "DatabaseReceiveport" URI: "mssql://master-biztalk//ReportServer?InboundId=batman" Reason: Finding the document specification by message type "http://schemas.microsoft.com/Sql/2008/05/TypedPolling/batman#TypedPolling" failed. Verify the schema deployed properly.

I'm not quite sure what it's trying to do above.

Solution

  • This means that either:

    1. The Project/Assembly with the specified Schema has not been deployed.
    2. The WCF SQL configuration is off somehow, frequently the InBoundId parameter. That's where "batman" would come from.

    In the All Artifacts Application, check the Schemas folder for that Schema by Root Node and Namespace.