|
Home > Archive > BizTalk Server Orchestration > October 2005 > Desperate Subscription Issue
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 |
Desperate Subscription Issue
|
|
| Chris Tucker 2005-10-24, 10:32 am |
| All subscription information looks good for one of 30 of my orchestrations.
The namespace is correct, the subscription attributes match the namespace and
port information. Here they are.
This is the namespace mapped in the Subscription viewer
MessageType= http://NexstarInboundInterface.Sche...starFunding_CSV
This is the targetnamespace in my schema
http://NexstarInboundInterface.Sche...starFunding_CSV
And the name of the root node is NexstarFunding
The orchestration is correctly configured to use this schema.
Message Type= NexstarInboundInterface.Schemas.schNexstarFunding_CSV
I have a Pipeline defined that has a flat file disassembler and uses
NexstarInboundInterface.Schemas.schNexstarFunding_CSV,
NexstarInboundInterface_Documents, Version=1.0.0.1, Culture=neutral,
PublicKeyToken=df67e85fa2382ee7
for the Document schema.
I have already checked that my version numbers and publick keys map as well.
I have run FFDASM and set a send port to retreive the receive locations
output after the pipeline and the xml has the correct namespace.
I get the dreaded "cannot find subscription for message" error no matter
what I do.
I have the latest service pack and all other orchestrations work and are
doing well.
Any suggestions will be greatly appreciated.
| |
| Jon Flanders[MVP] 2005-10-24, 10:32 am |
| Have you looked at the message context in HAT to see what teh messagetype on
the message that is suspended is?
--
Jon Flanders
http://www.masteringbiztalk.com/blogs/jon/
"Chris Tucker" <Chris Tucker@discussions.microsoft.com> wrote in message
news:8AEFA317-4628-44BB-B615-E9B3F7777DB6@microsoft.com...
> All subscription information looks good for one of 30 of my
> orchestrations.
> The namespace is correct, the subscription attributes match the namespace
> and
> port information. Here they are.
>
>
> This is the namespace mapped in the Subscription viewer
> MessageType= http://NexstarInboundInterface.Sche...starFunding_CSV
>
> This is the targetnamespace in my schema
> http://NexstarInboundInterface.Sche...starFunding_CSV
>
> And the name of the root node is NexstarFunding
>
> The orchestration is correctly configured to use this schema.
> Message Type= NexstarInboundInterface.Schemas.schNexstarFunding_CSV
>
> I have a Pipeline defined that has a flat file disassembler and uses
>
> NexstarInboundInterface.Schemas.schNexstarFunding_CSV,
> NexstarInboundInterface_Documents, Version=1.0.0.1, Culture=neutral,
> PublicKeyToken=df67e85fa2382ee7
>
> for the Document schema.
>
> I have already checked that my version numbers and publick keys map as
> well.
>
> I have run FFDASM and set a send port to retreive the receive locations
> output after the pipeline and the xml has the correct namespace.
>
>
> I get the dreaded "cannot find subscription for message" error no matter
> what I do.
>
> I have the latest service pack and all other orchestrations work and are
> doing well.
>
> Any suggestions will be greatly appreciated.
>
>
>
| |
| Chris Tucker 2005-10-24, 10:32 am |
| Yes, it is the same, good catch though.
"Jon Flanders[MVP]" wrote:
> Have you looked at the message context in HAT to see what teh messagetype on
> the message that is suspended is?
>
> --
> Jon Flanders
> http://www.masteringbiztalk.com/blogs/jon/
>
> "Chris Tucker" <Chris Tucker@discussions.microsoft.com> wrote in message
> news:8AEFA317-4628-44BB-B615-E9B3F7777DB6@microsoft.com...
>
>
>
|
|
|
|
|