This post originated from an RSS feed registered with .NET Buzz by Paschal. Original Post: Unhandled errors Feed Title: help.net Feed URL: http://www.asp.net/err404.htm?aspxerrorpath=/pleloup/Rss.aspx Feed Description: .Net for mankind ! Latest .NET Buzz Posts Latest .NET Buzz Posts by Paschal Latest Posts From help.net

I don't know for you guys but I still have issues with unhandled errors in web projects. The most infamous one is the General Network Error.

It's really annoying because I can't catch this error, so it not looking good to have this on a user page.
More this error come totally random. The only thing I know it's seem to be totally dependant with the network between the SQL box and the web server.

It's quite incredible, but it seems that Google returns a huge lot of various posts, messages of developers who have the same issue.

My concern is that nobody really have a clear answer on what's going on, some blaming the SQL provider, some the Data Application Block, some .Net itself.

So the only thing which work for me but I am not sure it's a good idea is to disable the pools in the SQL connection string with something like this : pooling=false.
I would be happy to find not only a solution, but a clear explanation.

Do you know others unhandled errors ? Does Whidbey handle the General Network Error ?