IIS 5 & IIS 6
IIS 6.0 "the process cannot access the file because it's being used b...
Last post Nov 04, 2007 10:16 PM by qbernard
Nov 02, 2007 05:57 AM|brekelbende|LINK
I can't start my default website (IIS6.0 /win2k3 sp2) anymore.
It says "the process cannot access the file because it's being used by another process"
1. I ran netstat -ano and no process is listening on the specified port (80) no apache, no skype no nothing.
2. also ran tcpview + filemon > nothing special there.
3. I ran httpcfg query iplisten and IIS is listening to 2 ipadresses:
4. So i configured my default on 192.168.101.46:8080 but no go.
5. rebooted several times but no go.
6. the logs say it can't listen to the specified address but windows is lying.
The must be something else. like pemissions. I've granted 'everyone' full control > no go
7. The webroot is basic: c:/inetpub/wwwroot
8. I have apache 18.104.22.168 installed on 192.168.101.48 and not running (Listen 192.168.101.48:80 so no Listen *:80...)
9. Uninstalled SP2, ran registry mechanic, rebooted, installed SP2 again. It worked......for 5 minutes. Then the same problem occured.
10. There no ip conflict ( i access the server through mstsc on the specified ip)
What could be the problem here? I'm running out of options here..
IIS ListenerPort problem
Nov 02, 2007 11:40 AM|brekelbende|LINK
Ok, i figured it out
i used "httpcfg set iplisten -i 192.168.101.46:80" to bind port 80 to 192.168.101.46
but i also ran ""httpcfg set iplisten - 192.168.101.46:443" to bind the SSL port to 192.168.101.46
It sounded logical to me, but it is wrong
I just had to configure port 80 and not port 443. Probably the whole port thing is unneccesary but i can imagine someone would like to bind port 80 to IIS and port 443 to Apache; it could be a plausible configuration.
Anyway, when the site started i could reinstall the specific ceritficate and IIS then automatically binds to port 443.
PS: disabling/enabling socketpooling didn't do the job also
Nov 04, 2007 10:16 PM|qbernard|LINK
If I recall this correctly, this is the design behavior, when IIS bind on that IP, the 443 and 80 are reserved for it, even 443 is not being used. the socket pooling is for all unassigned binding only, from your explanation it is still the same with sp2