The web server process that was being debugged has been terminated by IIS. Dead image link. When you are debugging, IIS will not service any other requests until you are done stepping through your code. That includes the "ping" request that IIS sends to itself. Since IIS doesn't hear back from itself, it decides to shut itself down, which promptly terminates your debugging.
Tips and Tricks in a world of Mix
The solution is to increase the Ping Maximum Response Time in the application pool settings from its default value of 90 seconds. Set it to something high enough that will give you enough time to debug your code like maybe seconds. Microsoft has a long-winded write-up here , or you can just look at the pretty picture. Others have suggested setting "Ping Enabled" to false.
There are several reasons why I prefer to keep it in place, just with a larger interval, but the most important is that you will most likely have worker processing pinging enabled on production, and you should strive to develop and debug under a configuration that is as close to production as possible.
IIS Web Server
If you do NOT have ping enabled on production, then by all means disable it locally as well. IIS has a health-checking feature which periodically checks to see if an IIS worker process is hung or otherwise unusuable. If a worker process is stopped in the debugger, it looks unhealthy from the perspective of IIS, and IIS kills it and spins up a new process. To change this behavior on your dev workstation-- don't want to disable this in production! This article provides you with all the information you need and the steps you must take to configure application pools.
The essential modules and handlers ought to be installed on the Web server and enabled at the level where you carry out the process.
Be aware that you can enable Modules at only the Web server, site, and application levels. However, you can enable handlers at all levels. If you carry out these operations with the use of Appcmd. You can create an application pool with the use of the user interface UI.
- visual studio - Why does debugging keep timing out in IIS7? - Stack Overflow.
- app game maker free online.
- The web server process that was being debugged has been terminated | Greg Kai on the Fly;
You can as well do it by running Appcmd. Alternatively, you can create it by editing configuration files straight-on, or through WMI scripts. To do this, navigate to the. NET Framework your managed apps, modules, and handlers need. Alternatively, choose No Managed Code. This is particularly useful; when the apps you run within this specific application pool do not need the. NET structure. Navigate to the list on the Managed pipeline mode , choose one the options presented below:.
NET request- processing channel.
Enabling Worker Process Pinging Through User Interface (UI)
NET request-processing modes differently. Straight after choosing your option, click on the Start application poo l to launch the application pool anytime the WWW service is initiated. This usually gets selected by default. To integrate an application pool to a Web server with the use of preset values make use of the language rules below:. The variable string is the name that you intend to give to the application pool.
IIS integrates an application pool that operates in integrated mode and uses. NET Framework version 2. If your intention is to incorporate an application pool that operates a separate version of the. NET Framework or that makes use of classic mode. You can designate the. To integrate an application pool to a Web server with the use of settings that differ from the default settings, you can make use of the syntax below:. The element managedRuntimeVersion string is the version of the. NET Framework that you want the application pool to run.
All in all this means that If your application pool has hung for some reason it will be recycled and everything will return to normal. This is not a new feature, but it can, however, cause some problems while debugging.
When you hit a breakpoint all execution stops, pending requests are not served and the worker process freezes completely. It will not respond to the health monitoring ping and if it doesn't continue execution within this window it will be terminated. There are three settings you can tweak with to resolve this.
How To Configure Idle Time-out Settings For An Application Pool (IIS 7)
This means you can either turn off health monitoring altogether by setting "Ping Enabled" to false, or you can tweak with the response time or the interval. Please note that the settings are there for a reason, so once you're getting close to production you really should return them back to their default values. I personally think the settings are excellent. An application pool that has hung will be reset within a maximum of 2 minutes.
With a decent out of process State Server setup your clients will probably notice an unusually long response time for one request, but think nothing else of it. You must be logged in to post a comment.