08-05-04 01:09 PM
I found the problem, is was the sending reciept which has a namespace
in the identity element for the delivery receipt. so it looked like:
<identity xmlns="http://schemas.biztalk.org/btf-2-0/properties">uuid:ee95429
a-c52e-4949-bf67-4abc2b593168</identity>
When I removed this namespace it works fine and is taken and matched
by my BT server. i.e.
<identity>uuid:ee95429a-c52e-4949-bf67-4abc2b593168</identity>
Anyone know if this is something I can remove on my server end or is
it a problem from the sending BT server ?
Lee
lee.connor@trustmarquesolutions.com (Lee) wrote in message news:<6ca2bfc1.0408031306.5a4d069
4@posting.google.com>...
> Hi,
>
> I am currently having a problem getting a reliable receipt from a BT
> 2002 into my 2004 server. I have an orchestration that has a send port
> using a pipeline the sends the XML with envelope using the BT
> Framework assembler over HTTP which works fine.
>
> I then have a receiving port which has a BT Framework disassemble
> piepline, this is however not attached to anything. From my
> understanding this should pick up the incoming SOAP receipt and
> automatically match with the sent envelope using the uuid. But every
> time I get a receipt I get the following error:
>
> ?Could not find a matching subscription for the message.
> The Messaging engine failed to process a message submitted by adapter:
> FILE Source URL:\\yweb01\BizTalkFiles\UAT\REC*.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 have checked the sending envelope uuid and the receipt uuid and they
> match, but then again I would expect a differing error if they didn't.
>
> Has anyone got any ideas on what this error means?
>
> Thanks
> Lee
[ Post a follow-up to this message ]
|