- This topic has 13 replies, 1 voice, and was last updated 8 years, 3 months ago by
.
-
Posts
-
-
-
-
-
my solution is like this, i create custom pipeline and deployed it for orchestration iam not using any direct binding
-
-
Iam getting following error
Details:Could not find a matching subscription for the message. . This error occurs if the subscribed orchestration schedule or send port has not been started, or if some of the message properties necessary for subscription evaluation have not been promoted. Please refer to Health and Activity Tracking tool for more detailed information on this failure
-
walter
i think you have not understood my problem, iam able to use elements properly without error, attributes when iam using receive shape filter iam getting this error
-
-
-
There is no difference in the way attributes and elements are treated when they are promoted.
The Disassembler will write the value from whatever element/attribute and set the property to be promoted.Can you provide a bit of background as to the message flow – adapter/pipeline/orchestrations
Are you using custom pipeline components to promote properties, are you passing messages between orchestrations using direct ports.
Or are you just receiving an Xml message thru the XmlReceive pipeline?
-
-
Kiran,
There should be no difference between elements and attributes when it comes to property promotion. The property value is extracted using xpath that can access elements and attributes.
The way properties are promoted can be a complicated process, involving pipelines, pipeline components, schema definitions, orchestrations, correlation sets and other factors that I cannot remember.
In order to assertain why your attribute properties are not being promoted properly, you will need to explain in detail how the message is being processed. From adapter to messagebox, including the schemas that are involved, how these were created etc. The pipeline and what components you are using.
-
[quote:bac1291d88]Details:Could not find a matching subscription for the message. . This error occurs if the subscribed orchestration schedule or send port has not been started, or if some of the message properties necessary for subscription evaluation have not been promoted. Please refer to Health and Activity Tracking tool for more detailed information on this failure[/quote:bac1291d88]
This errror may have nothing to do with promoted fields.
If you are using an orchestration, make sure it is deployed and started.
Are are you using message based routing?Do you have a filter on a send port that subscribes to only certain values(based on your promoted field)? Does the message go through if you remove these filtered values?
You might also try going to your schema, right-click properties, set file name, then right-click \”generate instance\”. Try dropping this file and see if it goes through. If it does, compare the root element and target namespace to the file you were testing with when you got this error.
-
Maybe you just need a second pair of eyes – to double check everything?
Are you dropping the right message? Is the attribute spelled correctly? Is the value in the filter spelled correctly? One upper-lowercase letter that is wrong can blow the whole thing! I often go to a co-worker and have them do a sanity check. Often when I am explaining to them, I see my error.
-
-
-
-
-
-
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.