Hi all. I am trying to migrate a working BTS 2004 project to BTS 2006 that
contains a custom pipeline. The custom pipeline is used to identify an XML
Envelope and Document schema for splitting batched messages into multiple
messages.

I have successfully compiled the project in VS2005, deployed to BTS 2006 and
executed instances of the batch message that contain one message. However,
whenver I execute a batched message that contains multiple messages I run
into problems ... i.e.

--- Works Fine -----
<VIPUpdates>
<VIP_Temp attrib1="" atrrib2=""/>
</VIPUpdates>
----------------------

--- Throws Error ---
<VIPUpdates>
<VIP_Temp attrib1="" atrrib2=""/>
<VIP_Temp attrib1="" atrrib2=""/>
</VIPUpdates>
----------------------

When the pipeline fails and I receive the following error messages:

Event ID: 5719
"There was a failure executing the receive pipeline:
"PhysWorksheet.pipelines.VIPSplit, PhysWorksheet, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=9e8086a9cece9671" Source: "Pipeline " Receiv
e
Port: "PhysWorksheet__VIP_SQL_RecvPort" URI:
"SQL://IND1SQL12\IN02/./WebServices_PhysWorksheet/" Reason: Unexpected event
("document_start") in state "processing_empty_document". "

I also receive Event ID: 5753.

Can anyone help me understand why my pipeline works fine splitting batched
messages that only contain 1 record, but fails when their are multiple
records? It doesn't make any sense to me ... especially considering the same
pipeline works fine in BizTalk 2004.

Thanks,
D

[ Post a follow-up to this message ]

Hello.
I'm stuck with the same problem.
It seems that the problem only occurs if you have a message like this:
<VIPUpdates>
<VIP_Temp attrib1="" atrrib2=""/>
<VIP_Temp attrib1="" atrrib2=""/>
</VIPUpdates>
But if you have something like this:
<VIPUpdates>
<VIP_Temp attrib1="" atrrib2=""><VIP>
<VIP_Temp attrib1="" atrrib2=""><VIP>
</VIPUpdates>
Well, your problem is gone.

What you could do is to change the stored procedure in order to include
a child element, as a result you will have the begin and end tag. (use
this only for testing, this is a stupid solution ).
OR
Use the for xml explicit instead of the for xml auto.

Let me know if you find out any other solution.

Pedro Rafael

dwg wrote:
> Hi all. I am trying to migrate a working BTS 2004 project to BTS 2006 that
> contains a custom pipeline. The custom pipeline is used to identify an XML
> Envelope and Document schema for splitting batched messages into multiple
> messages.
>
> I have successfully compiled the project in VS2005, deployed to BTS 2006 a
nd
> executed instances of the batch message that contain one message. However,
> whenver I execute a batched message that contains multiple messages I run
> into problems ... i.e.
>
> --- Works Fine -----
> <VIPUpdates>
>    <VIP_Temp attrib1="" atrrib2=""/>
> </VIPUpdates>
> ----------------------
>
> --- Throws Error ---
> <VIPUpdates>
>    <VIP_Temp attrib1="" atrrib2=""/>
>    <VIP_Temp attrib1="" atrrib2=""/>
> </VIPUpdates>
> ----------------------
>
> When the pipeline fails and I receive the following error messages:
>
> Event ID: 5719
> "There was a failure executing the receive pipeline:
> "PhysWorksheet.pipelines.VIPSplit, PhysWorksheet, Version=1.0.0.0,
> Culture=neutral, PublicKeyToken=9e8086a9cece9671" Source: "Pipeline " Rece
ive
> Port: "PhysWorksheet__VIP_SQL_RecvPort" URI:
> "SQL://IND1SQL12\IN02/./WebServices_PhysWorksheet/" Reason: Unexpected eve
nt
> ("document_start") in state "processing_empty_document". "
>
> I also receive Event ID: 5753.
>
> Can anyone help me understand why my pipeline works fine splitting batched
> messages that only contain 1 record, but fails when their are multiple
> records? It doesn't make any sense to me ... especially considering the sa
me
> pipeline works fine in BizTalk 2004.
>
> Thanks,
> D

[ Post a follow-up to this message ]

Hola Pedro y muchas gracias! Your suggestion was right on the money 

I was able to switch to "FOR XML Explicit" without to much trouble (well
some trouble  and after adding a child element was able to split the SQL
batched records just fine.

FYI: I also found the following BLOG to be very helpful on this subject as
http://objectsharp.com/blogs/matt/a...03/22/1560.aspx

Thanks Again,
D


"Moleiro" wrote:

> Hello.
> I'm stuck with the same problem.
> It seems that the problem only occurs if you have a message like this:
>  <VIPUpdates>
>     <VIP_Temp attrib1="" atrrib2=""/>
>     <VIP_Temp attrib1="" atrrib2=""/>
>  </VIPUpdates>
> But if you have something like this:
>  <VIPUpdates>
>     <VIP_Temp attrib1="" atrrib2=""><VIP>
>     <VIP_Temp attrib1="" atrrib2=""><VIP>
>  </VIPUpdates>
> Well, your problem is gone.
>
> What you could do is to change the stored procedure in order to include
> a child element, as a result you will have the begin and end tag. (use
> this only for testing, this is a stupid solution ).
> OR
> Use the for xml explicit instead of the for xml auto.
>
> Let me know if you find out any other solution.
>
> Pedro Rafael
>
> dwg wrote: 
>
>

[ Post a follow-up to this message ]