Sean wrote:
> Thanks Tom. This seems to work as far as we can tell.
>
> "TDC" wrote:
>
> > I can only imagine it is because only occasionally does ole32 (or
> > whichever module) copy data into executable memory?
> >
> > Here's an article that may help:
> >
> > http://support.microsoft.com/kb/875351/
> >
> > Tom
> >
> > Sean wrote:
> > > Thank you TDC.
> > > Could be - I don't know. But if so:
> > > 1. Why do we have this problem only occasionally?
> > > 2. Would it be wise to turn it of in production environment?
> > >
> > > Sean
> > >
> > > "TDC" wrote:
> > >
> > > > Isn't "Data execution prevention" a new Microsoft security feature that
> > > > (I think) helps protect against buffer overrun-type vulnarabilities?
> > > >
> > > > I just installed Visual Studion 2003 on a new laptop and Ihad to turn
> > > > off the DEP in the boot.ini to allow the emulator to work. (How lame
> > > > is that, by the way..."Here's a great new feature, but if you are a
> > > > developer you have to turn it off")
> > > >
> > > > Tom
> > > >
> > > > Sean wrote:
> > > > > HI,
> > > > > We have a WinForms App written in C#. It's all 100% manged code. This app
> > > > > monitor 4 Windows services that uses MSMQ to get and send messages from
> > > > > another WinForms App.
> > > > > One of the services interact with a CD printer API; Another is dowloading
> > > > > files from a server using HTTP; and another is is interacting with Verisign
> > > > > payment web services. Some of the services read and writes to a SQL server
> > > > > (MSDE).
> > > > >
> > > > > Ocassionally the app will display the following error message:
> > > > >
> > > > > To help protect your computer, Windows has closed this program.
> > > > > Name: COM Surrogate
> > > > > Publisher: Microsoft Corporation
> > > > >
> > > > > Once the user press the close message button the program is indeed
> > > > > terminated. The title bar of the message window is: Data execution prevention
> > > > > - Microsoft Windows.
> > > > >
> > > > > The problem occure occasionally in production environment. We were never
> > > > > able to reconstruct it on our dev environment and therefore we can't debug
> > > > > it. We are not sure were to even start looking or what the error means. The
> > > > > event viewer provide the following:
> > > > >
> > > > > Event Type: Error
> > > > > Event Source: Application Error
> > > > > Event Category: (100)
> > > > > Event ID: 1000
> > > > > Date: 08/04/2006
> > > > > Time: 15:43:48
> > > > > User: N/A
> > > > > Computer: AAX44
> > > > > Description:
> > > > > Faulting application dllhost.exe, version 5.1.2600.2180, faulting module
> > > > > ole32.dll, version 5.1.2600.2180, fault address 0x0001715e.
> > > > >
> > > > > Any clues? Ideas? Solutions?
> > > > >
> > > > > Thank you
> > > >
> > > >
> >
> >