"The published message could not be routed because no subscribers were found." No subscribtion error for single action PIP when sending back Signal/Ack message to the initiator.

  • Article

Problem description:

================================

In a single action PIP scenario of BizTalk Rosettanet, you may get the following error when the responder sending back Signal/Ack message to the initiator.

A message received by adapter "HTTP" on receive location "Async_Http_Receive"
with URI "/BTARNHttpReceive/BTSHTTPReceive.dll?xRNResponseType=async" is
suspended. Error 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. MessageId:

Troubleshooting:

================================

In Biztalk Admin console, please check if you can find the following subscribtion of PublicInitiator orchestration.

https://schemas.microsoft.com/BizTalk/2003/system-properties.ReceivePortID == {139D54E9-5A17-490B-B42F-893332124F36}  And    

https://schemas.microsoft.com/biztalk/btarn/2004/context-properties.IsDuplicateMessage == False  And

https://schemas.microsoft.com/biztalk/btarn/2004/rnifproperties.PIPVersion == V02.00  And

https://schemas.microsoft.com/biztalk/btarn/2004/context-properties.IsOrphanMessage == False  And

https://schemas.microsoft.com/biztalk/btarn/2004/rnifproperties.PIPCode == 4A3  And

https://schemas.microsoft.com/biztalk/btarn/2004/rnifproperties.PIPInstanceIdentifier == e209c7a4-7807-490a-81a3-ac905c05df23  And

https://schemas.microsoft.com/BizTalk/2003/system-properties.MessageType == https://schemas.microsoft.com/biztalk/btarn/2004/ServiceHeader_MS_V02_00.dtd#ServiceHeader

The most important part is the receive port ID. Please make sure the id belongs to Async_Http_Receive port. Otherwise, it means the public initiator orchestration isn't binding to the Async_Http_Receive port to receive the signal/ack messages which should result into the no subscriber error.

 

Best regards,

WenJun