currently we seem to have the problem described here: https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=449469 on one of our production servers running Windows Server 2008 SP2. On average IIS crashes once or twice a day. So our web application is still usable but far from reliable. The problem only appeared since the installation of the OS SP2 and it becomes worse when more users are connected. The cause for the crashes are nullpointer exceptions. Some of these exceptions are not directly triggered by our code (maybe timeouts...) and therefore cannot be caught by our exception handling code. The only workaround listed on Connect is to uninstall SP2, which is something we really would like to avoid on that server now. Any ideas for a less brutal solution, or workarounds? We are currently considering disabling connection pooling as an interim solution. Paul

Hello,i suggest to use the IIS newsgroup:http://www.microsoft.com/communities/newsgroups/list/en-us/default.aspx?dg=microsoft.public.inetserver.iisBest regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.