|
Home > Archive > BizTalk Server Orchestration > March 2004 > Biztalk 2004 Error: Could not find a matching subscription for the message.
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Biztalk 2004 Error: Could not find a matching subscription for the message.
|
|
| Santhoshi D.B. 2004-03-11, 10:43 pm |
| All,
I get this error : "Could not find a matching subscription
for the message. " for very project that I deploy on BTS
2004. I even created a simple orchestration that receives
Message_1 in a receive port, constructs Message_2 (simply
by Message_2 = Message_1) and sends out Message_2 using a
Send port.
The detailed message on the eventlog is:
"The Messaging engine failed to process a message
submitted by adapter:FILE Source URL:C:\Sony\Test1
\In\*.xml. 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"
I am unable to test any of my projects due to this error.
It seemed like a simple error, but I have started and
enlisted my orchestration and the send and receive ports.
Cannot think of what I am missing here. Please help!!
Thanks,
Santhoshi
| |
| hadsy 2004-03-17, 12:19 pm |
| Did you figure out what the problem was?
I had it before and the only way I solved it was to re-install Biztalk.
I hope there is another solution because I have the same problem again!
let me know how you got on
quote:
Originally posted by Santhoshi D.B.
All,
I get this error : "Could not find a matching subscription
for the message. " for very project that I deploy on BTS
2004. I even created a simple orchestration that receives
Message_1 in a receive port, constructs Message_2 (simply
by Message_2 = Message_1) and sends out Message_2 using a
Send port.
The detailed message on the eventlog is:
"The Messaging engine failed to process a message
submitted by adapter:FILE Source URL:C:\Sony\Test1
\In\*.xml. 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"
I am unable to test any of my projects due to this error.
It seemed like a simple error, but I have started and
enlisted my orchestration and the send and receive ports.
Cannot think of what I am missing here. Please help!!
Thanks,
Santhoshi
| |
| Brian Loesgen 2004-03-18, 2:00 pm |
| Santhoshi:
The instance that you're submitting does not match any of the schemas you've
deployed. Right-click the XSD in the solution explorer, set a "generated
instance" path, then right-click it again and chose "generate instance".
This way you can be 100% certain that the instance message conforms to the
schema.
The cool part is this works for flat files too, you just set the output type
to "Native" for any schema that uses the flat file extension, and voila!
It's magic 
HTH,
Brian
BizTalk Server MVP
Neudesic
"Santhoshi D.B." <santhoshi@riverone.com> wrote in message
news:a89001c406e7$b3daf5e0$a401280a@phx.gbl...
> All,
>
> I get this error : "Could not find a matching subscription
> for the message. " for very project that I deploy on BTS
> 2004. I even created a simple orchestration that receives
> Message_1 in a receive port, constructs Message_2 (simply
> by Message_2 = Message_1) and sends out Message_2 using a
> Send port.
>
> The detailed message on the eventlog is:
>
> "The Messaging engine failed to process a message
> submitted by adapter:FILE Source URL:C:\Sony\Test1
> \In\*.xml. 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"
>
> I am unable to test any of my projects due to this error.
>
> It seemed like a simple error, but I have started and
> enlisted my orchestration and the send and receive ports.
> Cannot think of what I am missing here. Please help!!
>
> Thanks,
> Santhoshi
|
|
|
|
|