Sangeetha

Question: Ok I'm getting this above error, now I've read You receive a "The process cannot access the file because it is being used by another process" error message when you try to start a Web site in the Internet Information Services 6.0 MMC snap-in and I've found that there is a process listening on port 80 it has a PID of 1968 and I'm damned if I know what that is, a trawl through google didn't shed much light, or maybe it's just me and I'm to tired to see. Anyway I'd love to know what it is. This is a new install of Win 2003 R2 with exchange 2003, I need the default website up and running for OWA and I really don't relish re-installing the whole lot to solve this problem. Any help gratefully received :-)

This is what netstat -ano showed:

Proto Local Address Foreign Address State PID
TCP 0.0.0.0:25 0.0.0.0:0 LISTENING 600
TCP 0.0.0.0:42 0.0.0.0:0 LISTENING 1684
TCP 0.0.0.0:53 0.0.0.0:0 LISTENING 444
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 1968
TCP 0.0.0.0:81 0.0.0.0:0 LISTENING 1968
TCP 0.0.0.0:88 0.0.0.0:0 LISTENING 860
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 1284
TCP 0.0.0.0:389 0.0.0.0:0 LISTENING 860

And no listenonly key is present in the registery hence the 0.0.0.0

Sangeetha

Well blow me, I sorted it, but think I'll leave this up as it may help someone else. Anyway I did some thinking and some noseing around as to what may be listening on Port 80, and I can up with two programmes. Non critical must haves. One was the Adaptec Storage Manager and the other was the SuperMicro Monitor. All I did was un-install and all was up and running, hurray.. Anyway Can anyone answer how would I know whihc app it was from the PID? And no real rushon this as I'm off to bed happy the damned server is up and running

AntonioChagoury

I just wanted to add to the above finding.

I ran a netstat -ano and found that port 80 was being used by another application with a process ID of 1976. (So IIS 7.0 was right to tell me that the process was already in use).
So I then opened the Task Manager (add the PID column to the view) and found that the process using port 80 was SKYPE!!!.

Turned off Skype (no need to uninstall) and everything worked.

Hope this helps someone else.

Antonio Chagoury
Inspector IT, Inc.
cto 2.0 - A Blog by Antonio Chagoury