I have a ASP.NET 4.0 application which connects to MSSQL through WCF and then Stored Procedure layers.
For some reason, with these layers, whenever I access a SP that is missing, or returns an error message, it causes my application to hang, because the application pool is stopped. Locally in debug mode, this causes by web server to crash.
Why does this happen? Is there a setting I can change to cause "better" behavior than a crash, or stoppage of the Application Pool?
UPDATE: I actually discovered that the app pool was stopping, not crashing. And it was stopping in IIS7/Windows Server 2008 R2 because it experienced too many errors in a short window. I adjusted the application pool setting to prevent it from stopping, and all works well. The errors were negligible.
The app pool wasn't actually crashing, but stopping.
This was the solution:
Turn off rapid fail protection for the app pool.