We have been trying to resolve this issue for a few years about the ASP service "hanging" and "timing out" We have a Windows 2003 Web Server that runs about 300 websites. There is no pattern or timeframe but in the range of a few days. So for example the server will hang on Monday and not have to be reset "IISRESET" again until Friday or maybe even two weeks. When this does happen all ASP and ASPX stop serving up on all websites on the server. The HTML pages come up fine, and when an IISRESET is done or more specific reset the ASP service it will "recycle the Application pool" and start working again. I ran across a asp programming FAQ "http://classicasp.aspfaq.com/general/why-does-iis-hang-and/or-stop-serving-asp-pages.html
" today that caught my attention and I'm attempting to resolve the issue or at least find out what is going on. To be honest I'm not sure if this is one site with bad code that "locks" up the app pool or what. The most information I found so far is that Microsoft in all it's glory made the Access database only stay "stable" at 10-15 connections. So running Ecommerce websites with Access and ASP, they state that this is a well known issue that after many connections it "locks up the service" and ASP pages stop responding. So to resolve this is to upgrade to use MS SQL so as to accept an unlimited amount of connections. What is the best way to attempt to resolve this issue? Any more questions or suggestions will be helpful, thanks again for reading this post and your time.