Last post Sep 26, 2012 01:18 AM by rmdw
Jul 21, 2007 06:54 PM|xgene|LINK
When in debug mode (c#, asp.net, asp.net ajax, vista, iis7) if I don't finish stepping through the code within 90-120 seconds, the debugger seems to time out. It drops out of debug mode.
I thought the default debug timeout was quite long. As far as I know I have not changed this. Anyone know where or how this is set? Is there some other issue that could cause the debugger to time out on an asp.net page?
Visual Studio 2005
Jul 21, 2007 08:59 PM|pbromberg|LINK
It would seem to me that what is happening is your Page is timing out, not your debugger. You can increase the page timeout with the executionTimeout attribute of the httpRuntime element in web.config. Here is an example for a specific page:
Jul 22, 2007 11:42 AM|xgene|LINK
Tried adding this:
Seemed to have no effect. Debugger still drops at around 90 seconds.
Jul 24, 2007 03:44 PM|jshallard|LINK
In IIS 7 go to the Application Pools and select the Advanced Settings for the pool which you process runs in. In the Process Model section you can do one of two things;
* Set the Ping Enabled property to False. This will stop IIS checking to see if the worker process is still running and keep your process alive permanently (or until you stop your debugged process)
* If you prefer to allow IIS to continue the monitoring process then change the Ping Maximum Response Timeout value to something larger than 90 seconds (default value).
See the following article for further details: http://forums.microsoft.com/MSDN/rss.aspx?ForumID=56&Mode=0&SiteID=1
Feb 07, 2008 11:57 PM|brianedow|LINK
In your option, what effect does setting httpruntime executionTimeout = "500" have over disabling or setting the Ping Maximum Response Timeout? Based on this response, it seems that httpruntime executionTimeout has little effect? Or am I missing the point
here and this error only happens during debug mode, and not when the debug=“true.
Jun 17, 2008 04:26 AM|institute|LINK
Have you tried setting the timeout on the script manager? it sounds like it is the async request is being timed out on the client side.
<asp:ScriptManager ID="siteScriptManager" runat="server" AsyncPostBackTimeout="180" >
Sep 02, 2008 12:31 PM|FMastro|LINK
Did any of these things solve the problem? I'm having the same issues, but I don't see any clear cut solution. Everyone suggesting something different.
Never mind, the App Pool ping solved the problem.
Sep 14, 2008 02:12 PM|jshallard|LINK
Yes - App Pool ping was the problem. Set ping enabled = false, and that sorted it
Apr 02, 2009 03:00 PM|rahul786|LINK
Can you guide for IIS 6 HOW TO SET THE PROPERTY YOU EXPLAINED FOR II7..M SORT OF NEWBIE..(:
Apr 02, 2009 09:47 PM|jshallard|LINK
I have never had the debugger timeout with the default IIS 6 settings. From my experience, this setting adjustment is only nessesary for IIS7
Jun 09, 2009 05:27 AM|mark4asp|LINK
Aug 27, 2009 08:32 AM|gotmike|LINK
i am having this same problem (post: http://forums.asp.net/t/1463712.aspx)
i am also using the development server that ships with VWD 2008, so the ping adjustment in IIS did not work for me.
the error i am getting is:
Unable to start program
Element not found.
Aug 27, 2009 08:38 AM|gotmike|LINK
i found this link which seems to describe my exact problem...
Jan 05, 2011 01:47 PM|neutrino|LINK
I had this same issue with Visual Studio 2008. Setting Ping Enabled property to False in IIS 7 Application Pool as explained by jshallard solved it.
Jan 22, 2011 06:58 PM|rmdw|LINK
From what everyone is saying, jshallard's solution works if you have VStudio configured to use IIS 7 during debugging. But what to do if you want to just use the Development Server within VStudio itself?
Sep 26, 2012 12:47 AM|jfmjason|LINK
just choose the pool for youre website. just click advance settings and on the properties set ping to false.
Sep 26, 2012 01:18 AM|rmdw|LINK
Where in the VS2008 menu would I find the "pool" that you're referring to? Remember, IIS is not involved, just Cassini.