I am getting this exception on my staging server (IIS6). The same code runs well in my local Visual Studio's ASP.NET Development Server. Here is my classes in question. It looks like the proxy returns null when retrieving the SiteID
public abstract class ApplicationController : Controller
{
private IRepository _Repository = new Repository();
[code]...
InnerException: System.AccessViolationException: Attempted to read or write protected memory.This is often an indication that other memory is corrupt.at System.Runtime.InteropServices.CustomMarshalers.EnumeratorViewOfEnumVariant.MoveNext()
I am getting this exception few times a day in our website.The page that create PDF file from the uploaded image files result in above excption.
I have an asp.net (3.5) web application.In one page i use an unmanaged C library (a simulator) that produces a set of results based on some input. When i've set the debug="false" in web.config (Release mode) that call will result in a System.AccessViolationException. If i am in the debugger, or at least set debug="true" in web.config, that exception will never appear.Because of the nature of the bug i placed the call inside a try-catch to log the exception and then the exception does not appear!
Is there some magical work on protected memory space when in debug mode and/or in a try-catch?