Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Source Error:

Line 37:         protected void Application_Start(Object sender, EventArgs e)
Line 38:         {
Line 39:             AppStartLogger.ResetLog();
Line 40:             AppStartLogger.WriteLine("Starting AspDotNetStorefront...");
Line 41: 

Source File: e:\Just\JustWeb\App_Code\Global.asax.cs    Line: 39

 

 

Symptoms
Accessing the site results in an "Attempted To Read Or Write Protected Memory" error.

Cause
There are 2 potential causes of this issue:

    1 - A site running a version of the ASPDNSF software older than 7.0.2.5 is attempting to run in a medium-trust hosting environment.

    2 - A site running a version of the ASPDNSF software older than 7.0.2.5 is running on a host that has just applied the .NET 3.5 SP1 upgrade to the servers.

NOTE: In both of these cases, the problem lies with the environment the software is running in, as configured by the host.  These are not flaws in the software, and are beyond our control.

Procedure
The best solution (regardless of which of the 2 causes above is creating your issue) is to upgrade to version 7.0.2.5 SP1 or higher of the ASPDNSF software.  Those later versions can run natively in medium-trust (thus avoiding issue #1) and work fine with the latest .NET service pack (which didn't even exist before then for us to test against). 

If upgrading is not an option at the moment, there are other workarounds for each possible cause.  Note that these are the ONLY workarounds.  We can provide no other advice than these steps:

Medium Trust:

    1 - First, have the host or server admin apply the Microsoft-created hotfix available at
http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=6003

    2 - Contact support and request a special medium-trust build of the software.  We will need a valid order number to provide that.

    3 - Move to a full-trust environment (this may mean switching hosts).

.NET 3.5 SP1 Patch:

    1 - Have the host roll back the changes on the server, or move your site to a server that has not had the patch applied.

 

https://support.aspdotnetstorefront.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=208

 

If you are using aspdotnetstorefront and are getting the following error: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. 

then please contact aspdotnetstorefront in regards to the error as you will have to upgrade your aspdotnetstorefront storefront application to version 7.0.2.5 SP1 or version 7.1.0.0 if the .NET 3.5 service pack is installed.

If you are not using aspdotnetstorefront and are getting this error, you will need to verify that you code works with the lates dotnet service packs for all versions. This error is usually remoting related, but not always.