This post has been republished via RSS; it originally appeared at: IIS Support Blog articles.
Symptoms
=========
In the world of application development, encountering unexpected exceptions can be a common and frustrating experience, especially when these errors lead to the stoppage of the application pool. One particular issue that developers often face is when an application throws an exception and triggers Just-In-Time (JIT) debugging. JIT debugging is a feature that allows Visual Studio to automatically launch and debug an application running outside of the Visual Studio environment whenever it encounters an error or crash. While this can be a powerful tool for diagnosing issues, it can also disrupt the normal operation of the application, causing downtime and hindering productivity. In this blog, we will explore the implications of JIT debugging, understand why this exception occurs, and discuss strategies to manage and prevent application pool interruptions.
While working on a web application, you may encounter the below exception that also stops the application pool.
Troubleshooting Steps:
====================
Review the Application event logs.
Faulting application name: w3wp.exe, version: 10.0.17763.1, time stamp: 0xcfdb13d8
Faulting module name: clr.dll, version: 4.8.4645.0, time stamp: 0x648f6f63
Exception code: 0xc0000005
Fault offset: 0x0000000000002cad
Faulting process id: 0x1914
Faulting application start time: 0x01da79eee4b4c819
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: a2b6cfb0-72b7-4589-b027-21aa3222a83f
Faulting package full name:
Faulting package-relative application ID:
Review the System event logs.
Application popup: Visual Studio Just-In-Time Debugger : An unhandled Microsoft .NET Framework exception occurred in w3wp.exe [6420]. Just-In-Time debugging this exception failed with the following error: No installed debugger has Just-In-Time debugging enabled. In Visual Studio, Just-In-Time debugging can be enabled from Tools/Options/Debugging/Just-In-Time.
Check the documentation index for 'Just-in-time debugging, errors' for more information.
This issue happens when Just-In-Time debugging can launch Visual Studio automatically when an app running outside Visual Studio errors or crashes. With Just-In-Time debugging.
Solution:
=======
remove jit debugging from the registries below.
- HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\DbgManagedDebugger
- HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugge