Friday, August 12, 2011

Error: "The published message could not be routed because no subscribers were found."


Charan: Hey Rohit I am getting the error "The published message could not be routed because no subscribers were found." as shown below. Do you have any idea how I can get rid of it?


Rohit: As this error is stating that  "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." Let  trouble shoot this error by using the BizTalk Administration console. 

First check the properties in the context of message and verify if you can see the desired properties promoted.

Charan: hmmm ok I am opening the routing failure reports:

 
I can see the property 'Customer' is promoted in the context of message.

 
Rohit: Then the second step would be to check the subscription. Let me check the Activation Subscription:


I can't see any subscription. Have you forgot to enlist the Send Port/Orchestration.

Charan: Let me check 
ohh... yes I forget to start the send port.

Rohit: Then start it and resume the message again.

Charan: I have started it and resuming the message.


Charan: hmmm... I am still getting the same error

Rohit: Let me check the Activation Subscription details.


I can see that you have specified the wrong name in send port subscription. It is showing as "ab" and based on the value of property Customer in the context of the message I think it should be "abc". Correct it in send port filter and resume the message.


Charan: Ah!! at last it worked !!!

Cheers
Rohit Sharma

1 comment:

Waylon Kenning said...

Awesome, I like this style. I'm still having problems, but at least this helps me to troubleshoot my issue. This "The published message could not be routed because no subscribers were found." error is killing me!

Post a Comment