Can't start IIS-6.0 Instance

Folks:

Intersting problem with IIS-6.0 I got it up and running,
turned on SSL, then used the HTTPCFG tool to turn off
socket pooling as I have another process that wants 80 on
one of the IPs on the NIC.

As soon as I did that (all of this via Terminal Services)
the website stopped and couldn't be restarted. From
within the IIS Service Manager (running locally on the
server) if I right click the site and try to start the
site I get an error message saying "The network location
cannot be reached. Blah blah blah"

I looked at the W3SVC1 log files and anything else I could
think of. I even tried uninstalling IIS, blowing away the
Inetpub dir and reinstalling; no dice. As soon as I
restart the site (or the IIS manager) the site somes up
with the "stopped" icon and gives the above error message
on start attempts. I'm running this on Win-2003 Server on
a 1U server w/ dual AMDs and a wad of RAM and storage and
not much else.

Anyone have any idea where to go next? Log files?
Something? I'd rather not have to reinstall the OS.

BTB, I have run this same application configuration w/ no
problems w/ II-5.0, I suspect something about the changes
in 6.0 + need to use serious voodoo to disable socket
pooling may be causing th problem.

Thanks,

Bill

I saw something like this myself when trying to use httpcfg. Try using
httpcfg delete iplisten -i xxxx:yy to remove what you added with httpcfg and
I bet it will start working again. Although that doesn't do you much good
since you need to disable the socket pooling, at least that will get you
back to having the sites start working.

When I was trying httpcfg today that's exactly what I saw. Then after
playing some more the error changed from the one you reported to one that
said that it could not access a resource because it was locked by another
process. Then used httpcfg to delete all entries for iplisten and the
errors went away. So the question remains is how can one use httpcfg as
documented to prevent socket pooling, without causing these other errors??

** What I really want to do is disable socket pooking entirely. **

I don't want to use iplisten and set up a list of all the IPs that IIS
should listen for and pool. Rather, I just want to tell IIS, "HEY, DON"T
USE SOCKET POOLING FOR ANYTHING!". Just like could be done under IIS 5 with
disablescoketpooling. Hey Microsoft gurus - is something like this
possible?? Please say so, as disabling socket pooling is something quite
different than eliminating IPs for IIS to listen to (which apparently is
what httpcfg does, not actually disabling socket pooling within the IIS
IPs...).


"Bill" <BillKatz RemoveThis @hotmail.com> wrote in message
news:5a5c01c3b2fb$21526810$a601280a@phx.gbl...
 > Folks:
 >
 > Intersting problem with IIS-6.0 I got it up and running,
 > turned on SSL, then used the HTTPCFG tool to turn off
 > socket pooling as I have another process that wants 80 on
 > one of the IPs on the NIC.
 >
 > As soon as I did that (all of this via Terminal Services)
 > the website stopped and couldn't be restarted. From
 > within the IIS Service Manager (running locally on the
 > server) if I right click the site and try to start the
 > site I get an error message saying "The network location
 > cannot be reached. Blah blah blah"
 >
 > I looked at the W3SVC1 log files and anything else I could
 > think of. I even tried uninstalling IIS, blowing away the
 > Inetpub dir and reinstalling; no dice. As soon as I
 > restart the site (or the IIS manager) the site somes up
 > with the "stopped" icon and gives the above error message
 > on start attempts. I'm running this on Win-2003 Server on
 > a 1U server w/ dual AMDs and a wad of RAM and storage and
 > not much else.
 >
 > Anyone have any idea where to go next? Log files?
 > Something? I'd rather not have to reinstall the OS.
 >
 > BTB, I have run this same application configuration w/ no
 > problems w/ II-5.0, I suspect something about the changes
 > in 6.0 + need to use serious voodoo to disable socket
 > pooling may be causing th problem.
 >
 > Thanks,
 >
 > Bill<!-- ~MESSAGE_AFTER~ -->