Check that you have applied all the service packs and hotfixes for IIS
and NT. I'm pretty sure that, unless you have a particularly unruly app,
this memory leak thingy was cured quite a while ago and the ASP deadlock
was fixed in sp5 or 6a I forget which. If you're running an oop app that
crashes, you can't stop IIS from MMC  until it's finished cleaning up
the crash, but if you don't touch MMC, net stop generally works (though
slowly).If the service has actually crashed, you get that service cannot
be controlled message (or if you try through MMC and then use net stop).
There is a reg edit for allocating more worker threads and pool threads
if the box is working very hard. Also a hotfixes for leaks caused by
DCOM and ODBC (service pack).

To kill it, as Jonathan says, use reskit kill. If it won't die for you,
use at to schedule kill so it runs as local system. As a last resort,
bounce the box.
K
----- Original Message -----
From: <John.ksi(at)webplus.net>
To: <hwg-servers(at)hwg.org>
Sent: 11 April 2001 12:44
Subject: net stop w3svc


> According to the NT task manager, memory used by inetinfo.exe
> (aka IIS) keeps on growing.  So I try to restart it based on
> some MS Q-doc I saw someplace which suggest a series of
> "net stop ..." commands.
>
> But "net stop w3svc" doesn't always work.  I forget the exact
> error message, but it was usual MS vagueness.
>
> Stopping the inetinfo.exe process in task manager kills it OK.
> But "net start w3svc" reports that it's not in a state that
> can be controlled.  (Sounds like a 2-year old kid.)
>
> Ideas on what's the cleanest and most reliable way is to restart
> IIS from the DOS prompt?  (I may want to "at" this.)
>
> -John
>
>

• Web Designer Courses
• Off the Shelf Training Courses

HWG: hwg-servers mailing list archives, maintained by Webmasters @ IWA