Hi,

This just started happening recently. IIS shuts down by itself. When I open up the IIS folder, all of my websites have the phrase "(stopped)" listed beside them.

I am using Windows 2000 Server. Here is something I wanted to include from the System Log in the Event Viewer...

------------------------------------
W3SVC (Error)
------------------------------------
The service could not bind instance 11. The data is the error code.
For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.
------------------------------------
IISCTLS (Info)
------------------------------------
IIS stop command received from user NT AUTHORITY\SYSTEM. The logged data is the status code.
For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.
------------------------------------
SMTPSVC (Error)
------------------------------------
The server was unable to register the administration tool discovery information. The administration tool may not be able to see this server. The data is the error code.
For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.
------------------------------------
Browser
------------------------------------
The browser was unable to retrieve a list of servers from the browser master \\INSTALOGICPC on the network \Device\NetBT_Tcpip_{69105FDA-F8EA-4B6D-AD19-73A91BB0B9BC}. The data is the error code.
------------------------------------

I'd really appreciate it if you can help. Thanks!

KMALIK

I know that IIS sometimes stops itself when memory usage gets too high. It may or may not be related to this exact problem.

Give the Event ID# as well... Can get more information from that than just the event logs alone.

One instance... Seen that with Exchange and Windows 2000... updated to latest service pack was the resolution for that one.

Browser: Make sure that a master browser exist for the domain. If you don't have a domain network, remove NetBios from your network bindings.

Hope that helps a little.

Yes, the event id# could be very useful. Go to start -> programs -> administrative tools -> services and select the IIS admin service properties. Check in the log on tab to make sure that the radio button for Local System Account is selected. Often what happens is people will switch this to another user account, change the password for that user account, and then forget to change the password that the service uses. Thus, the service can't authenticate and cant' start.
Hope that may help some.

Try updating the server with latest patches (not all) as suggested by tbnguyen. The unchecked buffer overrun in ISAPI application bug was found to be a problem for this on one of the servers I maintain.

Also, this could be due to a high CPU Utilization. Do the following to single that out:

-> Click the Process tab in Task Manager, and then click the CPU column header to sort the list based on CPU utilization.

-> Verify that Inetinfo is the process that is using the CPU.