Cloud

Prevent IIS from Terminating Your Debugging Session

One of the most irritating things that can happen while you’re debugging is this message:
iis1
When you sit at any one breakpoint for too long (longer than the ping maximum response time), this error will appear and terminate your session.
If you’re anything like me and my fellow team members, you’ll blindly click “OK” and start over with an extra dose of frustration. Luckily for us, our tech lead, Mike Becker, actually read this message one day and provided us with the solution. It’s so simple, you’ll kick yourself for ever having put up with this.
All you need to do is open the IIS Manager, locate your application pool, go into the advanced settings, and change “Ping Enabled” to “False.”
iis2
To maximize your efficiency a little more, you could throw this command into a batch file:

c:windowssystem32inetsrvappcmd.exe set apppool /apppool.name:%1 /processModel.pingingEnabled:false

.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode, .ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode pre
{font-size:small;color:black;font-family:consolas, “Courier New”, courier, monospace;background-color:#ffffff;}
.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode pre
{margin:0em;}
.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode .rem
{color:#008000;}
.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode .kwrd
{color:#0000ff;}
.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode .str
{color:#006080;}
.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode .op
{color:#0000c0;}
.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode .preproc
{color:#cc6633;}
.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode .asp
{background-color:#ffff00;}
.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode .html
{color:#800000;}
.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode .attr
{color:#ff0000;}
.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode .alt
{background-color:#f4f4f4;width:100%;margin:0em;}
.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode .lnum
{color:#606060;}
Then run it in PowerShell with the name of your app pool, e.g.

.iis “SharePoint – testSite.test.local”

.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode, .ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode pre
{font-size:small;color:black;font-family:consolas, “Courier New”, courier, monospace;background-color:#ffffff;}
.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode pre
{margin:0em;}
.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode .rem
{color:#008000;}
.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode .kwrd
{color:#0000ff;}
.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode .str
{color:#006080;}
.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode .op
{color:#0000c0;}
.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode .preproc
{color:#cc6633;}
.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode .asp
{background-color:#ffff00;}
.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode .html
{color:#800000;}
.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode .attr
{color:#ff0000;}
.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode .alt
{background-color:#f4f4f4;width:100%;margin:0em;}
.ExternalClassAF0B3C3A88D1472B9B9F393B4C7E9917 .csharpcode .lnum
{color:#606060;}
Keep that batch file somewhere handy and repeat whenever a new app pool starts bothering you.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Stephanie Hasz

More from this Author

Subscribe to the Weekly Blog Digest:

Sign Up
Follow Us
TwitterLinkedinFacebookYoutubeInstagram