Hi,

I’m facing a silly problem in BizTalk 2004

here is the scenario:

I’m dropping one xml file to a “pickup” location on my development server.
I’ve a receive location looking at the folder that picks up this message.

Now I’ve a send port configured that has some filters defined on it…. It picks up this xml file and transforms this to another xml file and HTTP posts this to the same BizTalk server (to the BTSHTTPReceive.dll).

Now I’ve an orchestration waiting for this precise message that has been http posted.

The orchestration picks up this message and after going through some test conditions and processing sends this message to a file location on the same server.
The same orchestration when it encounters an error, sends the “filtered” xml to an “error” location (file store location) on the same server.

So far so good.

But, now comes the problem…. Once the message is picked up by the orchestration, I expect the xml to either come to the “passed” folder or the “error” folder… but what is happening is instead of just ONE file appearing in either of these locations, I see that the original message that I had sent (http posted to the BTSHTTPReceive.dll) is still “active” in the message box database and the orchestration again picks up the same message and dumps it to the file location – “passed” or the “error” locations as the case maybe…

I’m really stumped here – I don’t know what I’ve done wrong here… I expected the message to “die” once its been picked up by the ONLY subscriber for that message, but no… the message is persisted in the message box and the orchestration is in an “infinite” loop and is continuously processing the same xml…. !

Kindly point out as to what silly thing that I’ve done or forgotten to do… this issue is driving me up the wall.

And yes, I need to have this process exactly as I’ve described above – that is to have one receive location receive the “raw” file, a send port acting as a subscriber that does the initial transformation and this posts the message back to the BTS and finally an orchestration waiting to pick up this message for further processing.

Any help is greatly appreciated!

Hi All,

i've resolved the issue i had; it had to do with not having sufficient filters defined in the send port and the orchestration.

i just had a genric filter on the send port as BTS.ReceivePortName = "PortName".
I've now added more meaningful filters and its working fine!

Thanks,
CK