I used WinDbg and i was able to extract the following error. However i do not know what's causing it? Do you guys understand these errors at all? THank you
*** ERROR: Symbol file could not be found. Defaulted to export symbols for mscorwks.dll -
PDB symbol for mscorwks.dll not loaded
OS Thread Id: 0x1ac4 (59)
*** WARNING: Unable to verify checksum for mscorlib.ni.dll
*** ERROR: Module load completed but symbols could not be loaded for mscorlib.ni.dll
*** WARNING: Unable to verify checksum for System.Web.ni.dll
*** ERROR: Module load completed but symbols could not be loaded for System.Web.ni.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for webengine.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for iiscore.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for kernel32.dll -
Child-SP RetAddr Call Site
000000000879d8f0 000007feeee6c126 System.Reflection.Assembly.InternalLoad(System.Reflection.AssemblyName, System.Security.Policy.Evidence, System.Threading.StackCrawlMark ByRef, Boolean)
000000000879d980 000007feeeed3a53 System.Reflection.Assembly.InternalLoad(System.String, System.Security.Policy.Evidence, System.Threading.StackCrawlMark ByRef, Boolean)
000000000879d9e0 000007feec86ee2e System.Reflection.Assembly.Load(System.String)
000000000879da20 000007feec86e9c2 System.Web.Configuration.CompilationSection.LoadAssemblyHelper(System.String, Boolean)
000000000879db30 000007feec8d53f0 System.Web.Configuration.CompilationSection.LoadAssembly(System.Web.Configuration.AssemblyInfo)
000000000879db90 000007feec8fd016 System.Web.Configuration.AssemblyInfo.get_AssemblyInternal()
000000000879dbd0 000007feec86dbda System.Web.Compilation.CompilationUtil.GetTypeFromAssemblies(System.Web.Configuration.AssemblyCollection, System.String, Boolean)
000000000879dc70 000007feec893abd System.Web.Compilation.BuildManager.GetType(System.String, Boolean, Boolean)
000000000879dcf0 000007feec893a5a System.Web.UI.Page.get_ScriptManagerType()
000000000879dd30 000007feec896c04 System.Web.UI.Page.get_IsPartialRenderingSupported()
000000000879dd70 000007feec8b070c System.Web.UI.WebControls.BaseValidator.RegisterValidatorCommonScript()
000000000879ddd0 000007feec8b0780 System.Web.UI.Control.PreRenderRecursiveInternal()
000000000879de20 000007feec8b0780 System.Web.UI.Control.PreRenderRecursiveInternal()
000000000879de70 000007feec8b0780 System.Web.UI.Control.PreRenderRecursiveInternal()
000000000879dec0 000007feec8b0780 System.Web.UI.Control.PreRenderRecursiveInternal()
000000000879df10 000007feec8b0780 System.Web.UI.Control.PreRenderRecursiveInternal()
000000000879df60 000007feec8b0780 System.Web.UI.Control.PreRenderRecursiveInternal()
000000000879dfb0 000007feec8b0780 System.Web.UI.Control.PreRenderRecursiveInternal()
000000000879e000 000007feec8b0780 System.Web.UI.Control.PreRenderRecursiveInternal()
000000000879e050 000007feec8aceb2 System.Web.UI.Control.PreRenderRecursiveInternal()
000000000879e0a0 000007feec8abff0 System.Web.UI.Page.ProcessRequestMain(Boolean, Boolean)
000000000879e170 000007feec8abf1b System.Web.UI.Page.ProcessRequest(Boolean, Boolean)
000000000879e1d0 000007feec8abeb0 System.Web.UI.Page.ProcessRequest()
000000000879e230 000007ff00761d54 System.Web.UI.Page.ProcessRequest(System.Web.HttpContext)
000000000879e290 000007feec8b3357 ASP.details_aspx.ProcessRequest(System.Web.HttpContext)
000000000879e2c0 000007feec87671b System.Web.HttpApplication+CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
000000000879e370 000007feecf63971 System.Web.HttpApplication.ExecuteStep(IExecutionStep, Boolean ByRef)
000000000879e410 000007feecf543b2 System.Web.HttpApplication+PipelineStepManager.ResumeSteps(System.Exception)
000000000879e5a0 000007feecf35df9 System.Web.HttpApplication.BeginProcessRequestNotification(System.Web.HttpContext, System.AsyncCallback)
000000000879e5f0 000007feed05dde1 System.Web.HttpRuntime.ProcessRequestNotificationPrivate(System.Web.Hosting.IIS7WorkerRequest, System.Web.HttpContext)
000000000879e710 000007feed05d9ab System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr, IntPtr, IntPtr, Int32)
000000000879e890 000007feed05cc14 System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr, IntPtr, IntPtr, Int32)
000000000879e8f0 000007fef111e0ba DomainNeutralILStubClass.IL_STUB(Int64, Int64, Int64, Int32)
000000000879f120 000007feed05df10 DomainNeutralILStubClass.IL_STUB(IntPtr, System.Web.RequestNotificationStatus ByRef)
000000000879f200 000007feed05d9ab System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr, IntPtr, IntPtr, Int32)
000000000879f380 000007feed05cc14 System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr, IntPtr, IntPtr, Int32)
000000000879f3e0 000007fef111e30b DomainNeutralILStubClass.IL_STUB(Int64, Int64, Int64, Int32)
How many websites are running in the app pool? If there are more than one put each one in its own app pool to see what one is causing the crash. What version of iis?
Actually i started from there. I found some ERRORs in the log and then i got it debugged. However i am not sure where to find the methods it complains about. :( Meaning my question is e.g. what this line means:
Did you ever figure out an answer to this? I'm faced with an almost identical issue on an app currently. Mine's IIS 6, but the stack in WinDbg looks very similar:
We see XML serialization libs show up a lot, but not sure yet if it's the cause or a symptom. !analyze -v in WinDbg also outputs things like this, but not sure if it's a complaint from WinDbg about symbols, or if the wrong symbols on the production server are
actually part of the problem:
End result is an OutOfMemoryException, a StackOverflowException, and an ExecutionEngineException, followed by the application pool crashing, leaving an entry in Event Viewer, etc.
In both our cases it's happening in Reflection, obviously. I've even reverted to an older revision of the code and still get the issue, which makes me wonder if something changed in the build environment (hence wrong symbols?)... maybe Windows Update, maybe
user error.
If you've solved it (or if anyone else has insight), it'd be much appreciated.
KulerMaster
Member
206 Points
326 Posts
How do you debug the AppPool crashing?
Apr 22, 2012 10:35 AM|LINK
I used WinDbg and i was able to extract the following error. However i do not know what's causing it? Do you guys understand these errors at all? THank you
Ken Tucker
All-Star
16797 Points
2608 Posts
MVP
Re: How do you debug the AppPool crashing?
Apr 22, 2012 12:34 PM|LINK
How many websites are running in the app pool? If there are more than one put each one in its own app pool to see what one is causing the crash. What version of iis?
Space Coast .Net User Group
KulerMaster
Member
206 Points
326 Posts
Re: How do you debug the AppPool crashing?
Apr 22, 2012 05:33 PM|LINK
Only one website. IIS version is 7.5 ... 64 bit ApplicationPool. OS is Win Server 2008 R2. Thank you
Ken Tucker
All-Star
16797 Points
2608 Posts
MVP
Re: How do you debug the AppPool crashing?
Apr 22, 2012 07:40 PM|LINK
Anything in the event log for the server?
Space Coast .Net User Group
KulerMaster
Member
206 Points
326 Posts
Re: How do you debug the AppPool crashing?
Apr 22, 2012 07:50 PM|LINK
Actually i started from there. I found some ERRORs in the log and then i got it debugged. However i am not sure where to find the methods it complains about. :( Meaning my question is e.g. what this line means:
Prophasi
Member
2 Points
1 Post
Re: How do you debug the AppPool crashing?
Aug 23, 2012 04:34 PM|LINK
KulerMaster -
Did you ever figure out an answer to this? I'm faced with an almost identical issue on an app currently. Mine's IIS 6, but the stack in WinDbg looks very similar:
We see XML serialization libs show up a lot, but not sure yet if it's the cause or a symptom. !analyze -v in WinDbg also outputs things like this, but not sure if it's a complaint from WinDbg about symbols, or if the wrong symbols on the production server are actually part of the problem:
PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS
BUGCHECK_STR: APPLICATION_FAULT_WRONG_SYMBOLS_CLR_EXCEPTION
End result is an OutOfMemoryException, a StackOverflowException, and an ExecutionEngineException, followed by the application pool crashing, leaving an entry in Event Viewer, etc.
In both our cases it's happening in Reflection, obviously. I've even reverted to an older revision of the code and still get the issue, which makes me wonder if something changed in the build environment (hence wrong symbols?)... maybe Windows Update, maybe user error.
If you've solved it (or if anyone else has insight), it'd be much appreciated.