Re: Strange behaviour in pipeline
From: Christof [MVP] ("Christof)
Date: 08/18/04
- Next message: larry franks: "RE: loading xml into sql using bulkload"
- Previous message: Christof [MVP]: "Re: BizTalk creating strange characters in XML"
- In reply to: Karagu: "Strange behaviour in pipeline"
- Next in thread: Karagu: "Re: Strange behaviour in pipeline"
- Reply: Karagu: "Re: Strange behaviour in pipeline"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 18 Aug 2004 20:19:37 +0200
Please try debugging your pipeline component by attaching VS.NET to the
BTSNTSvc.exe process. You may post any results here...
Best regards,
Christof
--
Christof [Microsoft BizTalk Server MVP]
"Karagu" <Karagu@discussions.microsoft.com> wrote in message
news:81952875-7815-4C29-BB7C-8002F307D1BD@microsoft.com...
> Hi!
> I'm having a real hard time trying to understand the following behaviour:
> I have succesfully deployed the "HelloWorld" sample wich comes with the
SDK,
> and that basically just takes an incomming file from a receive location,
maps
> the content in that file into a new one, and puts the new file in an
> Out-catalog. I can drop the test file provided within the sample
> ("SamplePOInput.xml"), and out comes the out-file. So far so good...
> However, a strange thing happens (at least if you ask me) when I drop
> another file, wich is incorrect according to the expected content in the
> incomming file: the incorrect file that I drop in the receive location
> remains in that receive location instead of "dissapearing" into Biztalk,
and
> there are no entries what so ever in the event log about that incorrect
file.
> You could get the impression that nothing happens with the file, but if I
> look in HAT -> Operations -> Service Instances, I can see that two new
> instances of type "Pipeline" and with status "Active" are created each
> minute, until I manually delete the file from the receive location. These
> instances have exit code "-1061153238", wich I have found absolutly no
> information about...
> I'd appreciate if anyone could explain this behaviour to me, because what
I
> expected was simply the incorrect file "dissapearing" as usually, and an
> error being loged in the application log containing something like
"invalid
> content" or something like that.
> Regards
>
- Next message: larry franks: "RE: loading xml into sql using bulkload"
- Previous message: Christof [MVP]: "Re: BizTalk creating strange characters in XML"
- In reply to: Karagu: "Strange behaviour in pipeline"
- Next in thread: Karagu: "Re: Strange behaviour in pipeline"
- Reply: Karagu: "Re: Strange behaviour in pipeline"
- Messages sorted by: [ date ] [ thread ]