>I have found that stopping iisadmin is best as it seems some of
the .dll's do not unload just stopping the web service. On my
authentication box I do this each morning so I can back up a
database that is also linked via the web service.
Exactly, that's the point: since iisadmin is always running (since
IIS4), stopping w3svc or msftpsvc won't unload the main program itself, so
the loaded dlls, isapis and threads will stay on memory. I find IIS4 more
"sensitive" than IIS3, though: as a developer, I find myself having to
"brute force" IIS from memory much more times, now...
Rubens
