>You can use the KILL utility from the NT/Win2k resource kit. Very useful for killing stuck processes. The issue with stuck WWWC instances can occur if you have configuration problems or the Web server itself crashes... Usually Web COnnection Servers will clean up after themselves.

Yes, exactly, it was at the setup procedures. I forgot to do something and that caused a bad instantiation of the process. I'll keep that utility in mind if I ever run into that situation again when doing an install. Yes, once installed, there is no problem with loading/unloading the processes.

>Note that you can also go into the Admin.asp page and modify the script there on the bottom to show all of your WWWC server Exes. Once they show in the list you can optionally kill them from there. It's just some code using the WMI Process object, that's filtered by default.

Ok, good trick