IIS crash and server does not respond

[Caoman]

I have multiple Windows 2000 servers with IIS and SQL 2000 installed. Every week the servers will crash around noon. The symptoms are; IIS dies, you can not terminal to the server, you can not telnet to the server but you can still ping the server. We have many servers with this configuration but only a handful has this problem. Has anyone experience this before?

 

[dankelt]

What kind of messages do you have in your event viewer at around Noon?

Also, is it every day? or just once a week? Do all the servers with this problem crash at the same time and same day? or is it random?

 

[Caoman]

There is no unusual error message in eventviewer. I just get the usual "the previous system shutdown was unexpected." message. The system would crash once a week but the problem is not on all servers. Of the 15 servers that has the exact same configuration, 3 are having the same problems. And they are occurring at different remote locations but usually around noon at their local time.

 

[vicroz]

When you say they "crash", what do you mean? Are they bluescreening? or are they rebooting because you have them set to automatically reboot after a system crash in Start-up and Recovery options?

You may actually be bluescreening but you don't realize it because the system is automatically rebooting itself. If this is true, uncheck "automatically reboot" and wait for the next event. If you bluescreen, get the Stop code and the memory.dmp (make sure you are set for a Complete Memory Dump) and call MS support with the file zipped up.

hth Vic Rozumny, MCSE
Microsoft Corporation

 

[Caoman]

There is no bluescreen. The server is operating but IIS is not functioning. Users are not able to login to the web. The screen is either black or the desktop is frozen. The only option is to do a hard boot and everything is okay afterwards.

 

[koquito]

what i would first do is check Event Viewer asd dankelt suggest. Did you check also if the service was runing after the crash? A+, MCP, CCNA
marbinpr@hotmail.com

Keep fighting for your knowledge!

 

[Caoman]

Check the Eventviewer on many occassions but did not find anything relavent to the problem. I can not verify if the service is running since there is no access to the server.

 

[koquito]

I meant Event viewer on the server...when you say hard boot, and access event viewer, where is that (workstation or server)?
A+, MCP, CCNA
marbinpr@hotmail.com

Keep fighting for your knowledge!

 

[vicroz]

Caoman,

There is something else going on here. Also we need a better explanation of what you are seeing. If IIS is "crashing" (you still have not defined this), it should have no effect on the operation of the OS itself, to include Terminal Services (unless you are using the TSAC client). If IIS is "crashing", then you should be generating a Drwtsn32.log entry and a User.dmp file. The suggestion to check your event logs when the system comes back up is a valid one. We need more information. Also, what has changed in your environment recently? How long was IIS up previous to these recent crashes and what changed? Have you added any new device drivers? any new software? etc? Are you running AV on the server? What happens if you disable AV and reboot the server? Does IIS stay up then?
Any other 3rd party services that may be running?

Also how long does IIS stay up after you reboot? an hour? a day? a week? If IIS is in fact Watsoning, then your best bet (unless you are familiar with debugging) is to get the User.dmp and the Drwtsn32 log to MS for analysis.

hth
Vic Rozumny, MCSE
Microsoft Corporation