You searched for the word(s): userid:750446

More Search Options

RSS Available

• Re: Attempted to read or write protected memory. This is often an indication that other memory has been corrupted

  Only that I personally experienced that Oracle OLE DB driver doesn't work with NET Framework 2.0, while MSDAORA interacts correctly. I spent a week trying every trick to use Oracle driver, then I changed to Microsoft driver. It works in my environment. Gogliogi

  Posted to Migrating from ASP.NET 1.x to ASP.NET 2.0 (Forum) by gogliogi on 8/20/2007

• Re: Attempted to read or write protected memory. This is often an indication that other memory has been corrupted

  Microsoft also released a hotfix (July 2nd, 2007) to prevent the error "Attempted to read or write protected memory" that has been plaguing the .NET 2.0 platform for some time now. But it did NOT worked in my case. The hotfix can be downloaded from http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=6003 Gogliogi

  Posted to Migrating from ASP.NET 1.x to ASP.NET 2.0 (Forum) by gogliogi on 7/27/2007

• Re: Attempted to read or write protected memory. This is often an indication that other memory has been corrupted

  Hi guys, did you try to use Microsoft driver for OLE (MSDAORA) instead of Oracle driver ? it solved the issue for me: Gogliogi

  Posted to Migrating from ASP.NET 1.x to ASP.NET 2.0 (Forum) by gogliogi on 7/26/2007