Symptom:

The following error from a DNN site:

------------
[AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.]
   AspDotNetStorefrontExcelWrapper.ExcelToXml.SetLicense() +0
   AspDotNetStorefrontCommon.AppLogic.ApplicationStart() +150
   AspDotNetStorefrontDNNComponents.AppStart..cctor() +103

[TypeInitializationException: The type initializer for 'AspDotNetStorefrontDNNComponents.AppStart' threw an exception.]
   AspDotNetStorefrontDNNComponents.AppStart.Execute() +0
   AspDotNetStorefront.HttpModules.InitializerModule.System.Web.IHttpModule.Init(HttpApplication context) +42
   System.Web.HttpApplication.InitModulesCommon() +65
   System.Web.HttpApplication.InitModules() +43
   System.Web.HttpApplication.InitInternal(HttpContext context, HttpApplicationState state, MethodInfo[] handlers) +729
   System.Web.HttpApplicationFactory.GetNormalApplicationInstance(HttpContext context) +298
   System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context) +107
   System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +289
-------

Resolution:

While apparently there can be several possible causes for the "Attempted to read or write protected memory. This is often an indication that other memory is corrupt", we have documented one possible cause relevant to the AspDotNetStorefrontDNNComponents and 3Essentials hosting. 

In 09/2008, 3Essentials began deploying ASP.net 3.5 SP1 to it's shared web hosting servers.  In our own testing, this change has been linked to generating the above error on DNN sites with the ASPDotNetStorefrontDNNcomponent.

If you think you are affected by this issue, please contact support, and reference this KB article.