I am using envelope schemas.  In my Orchestration, I need to reference one
of the nodes in a 'decide shape'.  What I did was promote a  node in the
'NON' envelope schema.  Now when I run (drop off a file), I get this error
(see below).  If I remove the 'promotion' from the node in the schema,
everything works just fine.  (I also took out the decide shape, and it is
specifically the promotion that is causing the error).

Any ideas how to fiz?


Thanks in advance, Brian



Error:
There was a failure executing the receive pipeline:
"MWH.BTS.VerisignTextMessage.Pipeline.ReceiveVerisignTextMessagePush"
Source: "XML disassembler" Receive Location:
" E:\ProdApps\BizTalk\VerisignTextMessage\
IN\*.xml" Reason: The disassembler
encountered an envelope that does not contain the body element.

[ Post a follow-up to this message ]

Have you tried making the field distinguished instead of promoting it?
--
Regards
Tom Lysholt Hansen


"Brian Cesafsky" wrote:

> I am using envelope schemas.  In my Orchestration, I need to reference one
> of the nodes in a 'decide shape'.  What I did was promote a  node in the
> 'NON' envelope schema.  Now when I run (drop off a file), I get this error
> (see below).  If I remove the 'promotion' from the node in the schema,
> everything works just fine.  (I also took out the decide shape, and it is
> specifically the promotion that is causing the error).
>
> Any ideas how to fiz?
>
>
> Thanks in advance, Brian
>
>
>
> Error:
> There was a failure executing the receive pipeline:
> "MWH.BTS.VerisignTextMessage.Pipeline.ReceiveVerisignTextMessagePush"
> Source: "XML disassembler" Receive Location:
> " E:\ProdApps\BizTalk\VerisignTextMessage\
IN\*.xml" Reason: The disassemble
r
> encountered an envelope that does not contain the body element.
>
>
>
>

[ Post a follow-up to this message ]

yep, I tried that and get the same error.



"Tom Lysholt Hansen" <TomLysholtHansen@discussions.microsoft.com> wrote in
message news:BCF79D53-30AA-4AEC-A799-A5C9692FC5C5@microsoft.com...[vbcol=seagreen]
> Have you tried making the field distinguished instead of promoting it?
> --
> Regards
> Tom Lysholt Hansen
>
>
> "Brian Cesafsky" wrote:
> 

[ Post a follow-up to this message ]

I'm not sure exactly what you are doing, so I can't reproduce the error.

I'm willing to give it a ahot, if you either describe exactly what you are
doing - or send me the project (delete any secrets). We both might learn
something from that.

Another suggestion could be to do a workaround - maybe you can use the rules
engine, if you can't get the promotion strategy to work?

--
Regards
Tom Lysholt Hansen


"Brian Cesafsky" wrote:

> yep, I tried that and get the same error.
>
>
>
> "Tom Lysholt Hansen" <TomLysholtHansen@discussions.microsoft.com> wrote in
> message news:BCF79D53-30AA-4AEC-A799-A5C9692FC5C5@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

Another potential option would be to access the content using the xpath()
function instead of using promotions or distinguished content.

John

"Tom Lysholt Hansen" wrote:
[vbcol=seagreen]
> I'm not sure exactly what you are doing, so I can't reproduce the error.
>
> I'm willing to give it a ahot, if you either describe exactly what you are
> doing - or send me the project (delete any secrets). We both might learn
> something from that.
>
> Another suggestion could be to do a workaround - maybe you can use the rul
es
> engine, if you can't get the promotion strategy to work?
>
> --
> Regards
> Tom Lysholt Hansen
>
>
> "Brian Cesafsky" wrote:
> 

[ Post a follow-up to this message ]