Re: Flat file disassembler, crash event: memory is corrupt

So does this happen on different boxes (do you have different boxes to test

against?)
You have 1000 files, about how big are these files. If they are big, I
have 
seen a memory issue with large files in combination of maps on the recieve

or send ****t. I would recommend using the /3gb switch as do***ented here:
http://technet.microsoft.com/en-us/library/e834e9c7-708c-43bf-b877-e14ae443ecbf.aspx

Eric
http://blog.biztalk-info.com

"Q1andQ2" <Q1andQ2@[EMAIL PROTECTED]
> wrote in message 
news:D35E3331-31C9-4B57-9A94-8E02DF6CFEF7@[EMAIL PROTECTED]
> 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?
>> >
>> >
>>
>>
>>