IIS 5 & IIS 6
ALL sites go down - IIS restart doesn't work - Connection Reset error...
Last post Jan 30, 2013 03:26 AM by timrobinson33
Aug 09, 2010 04:55 AM|DafOwen|LINK
On our Windows 2003 SP2, IIS 6 web server every couple of months or so we seem to get an error where it stops serving sites completely.
Last one happened on Saturday - Google Chrome gave the error : "Error 101 (net::ERR_CONNECTION_RESET): Unknown error" , IE7 just said it could not get the site.
There are about a dozen websites served from the box - most with their own application pools. Mostly ASP.Net (C#), some simple html but they ALL go down. Usually the application pools recycle themselves fairly well, and this issue happens very little.
Thing is - I can't seem to trace any errors and other services work.
Only thing I've found to fix it as yet is to restart the server.
Due to the nature of the problem i.e. a dozen or so live sites going down I obviously don't want to hang about investigating possiblities blindly, so wondered if anybody had ideas on what it could be and how I could investigate if/when it next happens.
Have seen similar issues in the forum mentioned before but no one obvious conclusion. Plus they usually only mention 1 site.
In one someone mentioned
"You have too many connections open to the server. The limit for the OS is around 4000? Change the appropriate registry settings and reboot."
Without qualifying this. Surley this would give an IIS standard "Service Unavailable" message instead ? How do I check number of open connections ?
I realise this may well be more a server/windows/network issue - but thought I might as well start somewhere.
Aug 09, 2010 05:24 AM|KristoferG|LINK
Have you checked if there is an update to your NIC driver (or replace the NIC)? I have seen similair things happen when the NIC is faulty (usually things go extremely slow and connections resets, so what differ is that you can connect and use Remote Desktop).
You may also try to disable the NIC, and then enable it. It might work, but if it doesn't we still cannot know if the NIC is okay.
Nov 03, 2010 12:45 PM|tenroc2o0o|LINK
Did you ever find a solution to this? We've been having the same problem on various servers, all running completely different websites and software. IISReset never works - only a complete reboot.
Nov 03, 2010 12:52 PM|DafOwen|LINK
Nov 03, 2010 12:55 PM|DafOwen|LINK
Apr 07, 2011 05:12 AM|DafOwen|LINK
Still getting this issue - roughly once a month.
Recent occurance it was at night so I was able to do a bit more testing.
Also my monitoring service (scheduled app on a machine at seperate location that just calls a page expecting the [OK] message will send me a message if it re-ocurrs - this has happened a few times - as if the issue happens, fixes itself, then returns.
Right - some more notes after investigation:
Any clues ? As usual - a reboot resolved it for now.
I'm a Developer not a Sys Admin so not sure where to look. I'm seeing a few tools mentioned around such as IIS Crash Hang agent and IIS Exception Monitor. Would any of these work ?
Or anything else to look at when it next happens ?
Apr 16, 2011 07:56 AM|russ_gillespie|LINK
Apr 16, 2011 07:37 PM|HCamper|LINK
Since you notice the problems after Applying Service Pack 1 for Hyper-V R2.
Have seen this Technet Deployment Guide http://technet.microsoft.com/en-us/library/ff817650(v=ws.10).aspx
A Blog Post with Hyper-V R2 posts and links here
Technet Article for Configuration here
You may find advise in the Technet Security Bulletin index for Issues and Resolutions for your problems.
Hope this helps,
Apr 17, 2011 12:58 PM|russ_gillespie|LINK
Jan 30, 2013 03:26 AM|timrobinson33|LINK
This is almost certainly the non-paged-pool problem. It's a very common thing and is not actually a problem in IIS; usually it's a device driver problem. just google for IIS6 NPP and you'll find out all about it