- This topic has 5 replies, 1 voice, and was last updated 9 years, 6 months ago by
.
-
Posts
-
-
Hi everyone,
I always get this error message:
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.
So it seems that no subscription was set for the incoming message but i checked in the administration tool that there is one.
I have a custom disassambler in my incoming pipeline and a xmlValidator. If I debug the pipeline with the pipeline tool the format validates without errors.
Has anyone an idea what i'm doing wrong?
Kind Regards
Julian
-
Is your custom disassembler correctly promoting the MessageType property? Most regular subscriptions (such as typed subscriptions from orchestrations) depend on that property being there correctly set up (the XmlDisassembler and FFDisassembler do it by defauult).
-
context.Promote("MessageType", "http://schemas.microsoft.com/BizTalk/2003/system-properties ", "http://ClaimSchemas.s_ExcelContract")
"MessageType", "http://schemas.microsoft.com/BizTalk/2003/system-properties ", "http://ClaimSchemas.s_ExcelContract")
if this is promoting the MessageType correctly then it does. Otherwise i would be thankful for a little hint how to do it correctly
-
You seem to be promoting only the namespace but not the root element name…. remember the MessageType is formed namespace#root
-
-
-
-
Julian,
Recently I had the same error you received. In my case I received a flat file which I transformed to XML in a custom pipeline. However I forgot to promote the MessageType to the Message Context, resulting in the 'no subscription found' error.
Promoting the MessageType tot the message context fixed the error. The code of the Execute-method in your custom pipeline component will look as follows:
public IBaseMessage Execute(IPipelineContext pContext, IBaseMessage pInMsg)
{
string systemPropertiesNamespace = @"http://schemas.microsoft.com/BizTalk/2003/system-properties";
string _XMLMessageType = @"http://BizTalk2004TestProjects.ReceiveEmptyFile.EmptyFile#EmptyFile";
pInMsg.Context.Promote("MessageType", systemPropertiesNamespace, _XMLMessageType);return pInMsg;
}Good luck,
Lex
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.