|
Home > Archive > BizTalk Server General > December 2004 > Biztalk not able to find subscription
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 not able to find subscription
|
|
| KalyanT 2004-12-27, 5:48 pm |
| Hi,
Here is the error I am seeing in event viewer. My receive port is binded to
a stored procedure. Orchestration transforms input file to output format &
sends to send port.
The Messaging Engine encountered an error publishing a batch of "1" messages
to the Message Box database for the transport adapter "SQL". Please refer to
Health and Activity Tracking tool for more detailed information on this
failure and check the endpoint bindings are correctly configured.
The Messaging engine failed to process a message submitted by adapter:SQL
Source URL:SQL://WFOSRMDEV02/pubs/. 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
--
Kalyan
| |
| Jon Flanders 2004-12-27, 5:48 pm |
| If you are using a send port subscription - you don't need to use the
XmlReceive pipeline. The XML Dissasembler will try to find the schema in the
configuration database. So the two options are:
1) Use the PassThroughReceive pipeline
2) Register the schema by deploying the assembly that contains the schema
Do make sure that your send port is started.
--
Jon Flanders
http://staff.develop.com/jfland/
"KalyanT" <KalyanT@discussions.microsoft.com> wrote in message
news:A9D73485-DDD1-437F-8E03-43C86690E01C@microsoft.com...
> Hi,
> Here is the error I am seeing in event viewer. My receive port is binded
to
> a stored procedure. Orchestration transforms input file to output format &
> sends to send port.
>
> The Messaging Engine encountered an error publishing a batch of "1"
messages
> to the Message Box database for the transport adapter "SQL". Please refer
to
> Health and Activity Tracking tool for more detailed information on this
> failure and check the endpoint bindings are correctly configured.
>
> The Messaging engine failed to process a message submitted by adapter:SQL
> Source URL:SQL://WFOSRMDEV02/pubs/. 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
>
>
> --
> Kalyan
| |
| Matt Milner 2004-12-27, 8:46 pm |
| Make sure you have a send port or orchestration that is enlisted and
expecting this message type. It sounds like the message was received OK and
the type could be determined, so you probably have your schema deployed
propely, but you need something ready to consume the message. A good test
would be to setup a send port that has a filter for either your message
type, or the receive port and just write out to a file.
matt
"KalyanT" <KalyanT@discussions.microsoft.com> wrote in message
news:A9D73485-DDD1-437F-8E03-43C86690E01C@microsoft.com...
> Hi,
> Here is the error I am seeing in event viewer. My receive port is binded
> to
> a stored procedure. Orchestration transforms input file to output format &
> sends to send port.
>
> The Messaging Engine encountered an error publishing a batch of "1"
> messages
> to the Message Box database for the transport adapter "SQL". Please refer
> to
> Health and Activity Tracking tool for more detailed information on this
> failure and check the endpoint bindings are correctly configured.
>
> The Messaging engine failed to process a message submitted by adapter:SQL
> Source URL:SQL://WFOSRMDEV02/pubs/. 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
>
>
> --
> Kalyan
| |
| Richard Blewett [DevelopMentor] 2004-12-27, 8:46 pm |
| This sounds to me like you are using the PassThroughReceive pipeline for the message. This means that the XmlDisassembler isn't running so no-one is taking the message type (namespace) and putting it into the message context. The orchestration has subscri
bed on to the message type and it isn't in the context so the message has nowhere to go.
Switch your receive pipeline to the XMLReceive pipeline or a custom one with the XmlDisassembler in it
Regards
Richard Blewett - DevelopMentor
http://www.dotnetconsult.co.uk/weblog
http://www.dotnetconsult.co.uk
Hi,
Here is the error I am seeing in event viewer. My receive port is binded to
a stored procedure. Orchestration transforms input file to output format &
sends to send port.
The Messaging Engine encountered an error publishing a batch of "1" messages
to the Message Box database for the transport adapter "SQL". Please refer to
Health and Activity Tracking tool for more detailed information on this
failure and check the endpoint bindings are correctly configured.
The Messaging engine failed to process a message submitted by adapter:SQL
Source URL:SQL://WFOSRMDEV02/pubs/. 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
--
Kalyan
--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.296 / Virus Database: 265.6.5 - Release Date: 26/12/2004
[microsoft.public.biztalk.general]
|
|
|
|
|