IIS STOPS REPONDING FOR NO REASON

[pingood]

On a NT 4 server with SP6a with Exchange server 5.5, IIS (whatever comes with NT) and SQL 7 server. Every 2/3hr, the IIS server stops responding. The only way to clear it is to restart the server. There aren't any messages in the Event logs nor can I restart the service because it doesn't respond to the Shutdown command for the Web service.
Help, please!

 

[Whitemtntn]

You are not supposed to run IIS, Exchange, and SQL on the same BOX! They should each be on separate machines, as each is a complex and resource-intensive program.
Maybe that doesn't help you with your problem, but thats a fact, jack...

-WhiteMtntn

 

[ShackDaddy]

Have you noticed how much memory SQL left for the rest of the applications on the server to use?

ShackDaddy

 

[FilthPig]

While I agree that you're running too much on that box, here's an idea for getting the

http://WWW publishing

back without restarting. Use the kill.exe command from the resource kit to kill inetinfo.exe, and restart your

http://WWW and

FTP publishing services. Are you by chance also running proxy server 2.0? Terrible combo. Marc Creviere

 

[Whitemtntn]

It looks like even to use KILL to restart the service won't help you.. you say that even after you restart the server this happens again. I say after you restart, just for curiousity, keep a close eye on Task Manager to see which of the 800 pound gorillas on that server is using up the most memory, and which process is peaking the CPU.
But really, there's nothing to really say to help you except to separate your BackOffice products. Just having Exchange and SQL together is unfathomable in any real network environment-- they are both beasts.....then throw IIS on top just because its fun to watch a computer become hysterical and turn into a molten mass of muck.

(if this is a home project, then hey, reinstall IIS)
-WhiteMtntn

 

[ShackDaddy]

Actually, SQL will take most of the memory from the get-go, even if it isn't using it. That will leave you, typically, with around 20% of your memory to run everything else, unless you reconfig SQL.

IIS can be buggy if it's told to invoke unreliable COM components. We sweated through the sort of trouble you describe for almost a year until we finally found the source of the problem in a component that a channel partner was having us make calls to to retrieve data from them.

ShackDaddy