Guest Rich Posted September 12, 2007 Posted September 12, 2007 Hello-- I have recently converted .Net 1.1 Web App to 2.0. There are approx. 25 Users that use the Application some are Citrix-ing and VPN-ing from a distance (many states away). The App is running on a Win2Ksp4 Server, and using a Sql Server 2K sp4 (and Reporting Services sp2). This also means that our WebApp running on 2.0, will sometimes in a dynamically generated link provide a link to a Reporting Services report in the 1.1 framework. Ever since the conversion we periodically enter a "Stuck" State ... What we currently know about the "Stuck" state: - If caught early it seems that non-WebServer Services are responsive. - When Stuck, the system exhibits no CPU strain and no Memory problems (at least initially, I have only been on the Server once in this state). - Over time (maybe 10 mins???), other Services start dropping. - Eventually, all Services will freeze, and The Server becomes completely unresponsive. - The only way to get out of this State is a Hard Shutdown (using the power button on that machine). - The earliest indication that we are entering this state, open a new browser to http://nw-app/nwintranet/ ... if it loading very slowly (and never finishes)... It is Stuck. - If caught early enough (under 10-15 mins???), a Shutdown command will work from The Server . - If caught too late (greater than 10-15 mins???), a Shutdown command will not work. This insidious state is entered and the event log really does not consistently show a repeated error. Any Ideas about what and how to best monitor this Server to get down to the nitty-gritty? Regards, --Rich
Recommended Posts