AnsweredAssumed Answered

9101 64-bit .NET agent causes MVC3 apps to fail

Question asked by Jonathan.Openshaw on Jun 21, 2012
Latest reply on Jul 16, 2012 by andrewy
We recently promoted our first MVC3 application to production where we are running the 64-bit Wily APM agent for .NET. When we tried to launch the new application, we received the following error:

Exception information:
Exception type: VerificationException
Exception message: Operation could destabilize the runtime.
at System.Web.Mvc.MvcHandler.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Request information:
Request URL: http://
Request path: /
User host address:
User:
Is authenticated: True
Authentication Type: Negotiate
Thread account name: NT AUTHORITY\NETWORK SERVICE

Thread information:
Thread ID: 22
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at System.Web.Mvc.MvcHandler.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

In our dev and test tiers, the application worked perfectly. After many hours of research we discovered that our test tier was running the 32-bit version of the 9.1.0.1 APM agent for .NET. When we disabled Wily monitoring of our production MVC app's application pool, the application worked perfectly. If anyone else is running the 64-bit Wily APM agent for .NET and is able to monitor MVC3 apps I would love to hear how you made it work.

Outcomes