Why does debug time out in IIS7?

Question

When I debug my IIS7 machine for Windows 7, I get this error while debugging:

The web server process that debugging was terminated by IIS. This can be avoided by configuring application pool settings in IIS. see help for more information.

What am I doing wrong?

Answer 1

Dead link image

When you are debugging, IIS will not serve any other requests until you finish your code. This includes the ping request that IIS sends itself. Since IIS does not hear from itself, it decides to shut itself down, which quickly stops your debugging.

The solution is to increase the maximum Ping response time in the application pool settings from its default value of 90 seconds. Set it to something high enough to give you enough time to debug your code (e.g. 300 seconds).

Microsoft has a long entry here , or you can just take a look at the pretty picture.

-

Edit: Others suggested setting the “Ping Enabled” parameter to false. There are several reasons why I prefer to keep it in place, just at a wide interval, but most importantly, you (most likely) should do pinging processing for on-the-job processing, and you should strive to develop and debug the configuration as close as possible to production. If you do not use ping for production, be sure to disable it locally.

Answer 2

http://weblogs.asp.net/soever/archive/2009/06/18/debugging-sharepoint-asp-net-code-smart-key-codes-disable-timeout.aspx

Your application pool → Advanced settings → Ping Enabled to False

Answer 3

IIS has a health check function that periodically checks to see if any IIS workflow is visible or not. If the workflow is stopped in the debugger, it looks unhealthy from an IIS perspective, and IIS kills it and starts a new process.

To change this behavior (on your workstation dev - don’t want to disable it during production!), Go to the IIS management tool, select the node application pools in the left pane and right-click the application in which your application is located, and select "Additional settings". From there, in the Process Model section, set the Ping Enabled parameter to False. You can also set downtime as a very large number.

See this IIS.NET article for a more in-depth discussion of this issue and a screenshot. See this TechNet article on how to set these options using / script code outside of the administration tool.

Answer 4

If you have microsoft scom running and configured where you work (assuming that this is not a project for fun), you can create a management pack for it or know someone who can help you determine what is causing the problem. I understand his long shot, but if this describes your scenario, this is what I will do if no other solution is found.