ASP.NET 2.0 "Quiet" Exceptions are killing IIS?
Install an 2.0 web app in IIS 6 and the process pool was going down every 5 minutes with the wonderful red label that we all hate learn to love.
What to do next, I check the Event View to find some Hex there. Install debuggers for IIS without any sucess. At the end I had to enable legacyUnhandledExceptionPolicy on the asp.net config file. I learn from this article that you can actually put it on the app.config file:
http://www.julmar.com/blog/mark/PermaLink,guid,f733e261-5d39-4ca1-be1a-c422f3cf1f1b.aspx
Now I know there is a problem in my application, but what kills me is that I won't be able to find it if is “so quiet“.
I am writing a HttpModule to detect it, if I find the error I'll be posting it here. I cannot believe that Microsoft does not raise the exception and output the error on the browser instead, goes into a event viewer in plain hex.