You probably want to ask this question in:
microsoft.public.inetserver.iis
microsoft.public.windows.server.general
If your server is hanging, I suggest you run IIS State when the server hangs
and post the log file to microsoft.public.inetserver.iis to diagnose the
underlying problem -- and hopefully there is a fix for it -- so that there's
no more hanging.
http://www.iisfaq.com/default.aspx?view=P197
Rebooting the server is not the solution; it is only a quick bandaid. IIS
can hang for a variety of reasons -- bugs in your application/webpages, bugs
in the 3rd party controls/libraries that your application uses, or bugs in
the Microsoft controls/libraries. The real solution is to diagnose the
hangs and then find patches for the bugs -- so that eventually, there are no
bugs/hangs in the code you run on the server, and then you won't need to
reboot the server as a crutch anymore.
If you keep rebooting, sure you get back online quickly, but you fixed
nothing and will have to keep rebooting.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
When I have installed the fix for the last virus Sasser, on the server 2000
I can't use anymore the commands "Shutdown.exe \\servername /y /r /c" or
"iisreset servername /rebootonerror". The server don't restart.
What can I do to solve this problem? How to reactivate this functionality?
I use this commands when the IIS hang-on.
Thank you
Milani Omar
