Sounds like you are running out of memory, have you got a new Host for the
Send, Receive and Processing (Orchestration) for that Application ?.
Monitor
the BTS using Perfmon (Processes, Working Set) to see if you are bleeding
memory.
Remove all of the custom components and then add them back in one at a
time.
- Don’t try to tune the Host UNTIL After you have done this!
When you tune it, drop the number of messages being processed by the send
****ts right down (1/2) then retry, if that fixes it then the messages are
to
big (It loads based on Processor, Core etc). There is a good but complex
article on the MSDN about this.
Don’t try and change to much at once.
N
"Q1andQ2" wrote:
> if '0x00' comes without cra****ng, it throws the event of " Attempted to
read
> or write
> protected memory. This is often an indication that other memory is
corrupt".
> After a while, the machine crashed.
>
> "Eric Stott" wrote:
>
> > Lets leave the swearing to other forums.
> >
> > Do you experience the same problem with the memory when you use the
pipeline
> > testing components in the SDK?
> >
> > Eric
> > http://blog.biztalk-info.com
> >
> > "Q1andQ2" <Q1andQ2@[EMAIL PROTECTED]
> wrote in message
> > news:609E04F9-B901-4B71-988E-EA8BFB8885B3@[EMAIL PROTECTED]
> > > There was a failure executing the receive pipeline: ....Source:
"Flat file
> > > disassembler" Receive ****t:... URI: ....Reason: Attempted to read or
write
> > > protected memory. This is often an indication that other memory is
> > > corrupt.
> > >
> > > What the hell is going on?
> > >
> > >
> >
> >
> >
|
