I am running Windows 7 RC1. I have multiple issues getting IIS to work on my system and today when I installed a new application and I tried to load it using http:\localhost\MyApplication I get absolutely no errors and I get no page load. Just a pretty, white blank page.

I did some digging and I found something about some other process listening on port 80 so I did a scan using netstat -aon | findstr 0.0:80 and discovered that PID 4 was listening on that port.

PID 4 does not show in task manager so I fired up Process Explorer and it showed me that PID 4 is the System process. (Multiple google searches seems to indicate that System always uses PID 4).

Since then I am basically stuck. I have no idea why System needs port 80 and what to do about it.

If you google the following strings you will find two helpful Experts-Exchange articles at the top of the search results and you can read them for some helpful information.

(If I gave the direct URL to the pages then Experts-Exchange would ask you to pay...but when you click on the results from a google search you can scroll all of the way to the bottom to read the exchanges.)

Here are the google searches...
"System Process is listening on port 80 (Vista)"
"SYSTEM Process is listening on Port 80 and Preventing IIS Default Website from Running"

The last entry from the first result showed how to do a trace of http.sys at the following URL:

http://blogs.msdn.com/wndp/archive/2007/01/18/event-tracing-in-http-sys-part-1-capturing-a-trace.aspx

Trace showed nothing useful. Any thoughts?

link|improve this question

50% accept rate
Same problems here, except, I tried all answers as suggested and nothing. I can't just start shutting down services because this is an off-site cloud server. – Jerry Dodge Apr 2 at 6:30
feedback

5 Answers

up vote 4 down vote accepted

This post on Getting Apache to run on port 80 on Windows 7 describes your point.

It seems the 'http.sys' (Windows Remote Management?) service is enabled by default in Windows 7.
Run through the comments on that link for some more notes...

the hypen-site does not necessarily have the only answers.

link|improve this answer
feedback

'Wed Deployment Agent Service' runs on port 80 through system. You might have this running if you are using 'WebMatrix'.

link|improve this answer
Related link: eat.cheezburger.com/author/johnc. I uninstalled the two porgrams listed: "Microsft Web Deploy 2.0" and "Web Deployment Tool" (as well as WebMatrix itself) – Frank Schwieterman Oct 3 '11 at 20:51
Related link: remkoweijnen.nl/blog/2012/01/02/… – Remko Jan 10 at 10:12
feedback

I have tried EVERYTHING, and this worked for me:

  1. Right click on My Computer
  2. Select Manage
  3. Double click Services and Applications
  4. Then double click Services
  5. Right click on "Sql server reporting services(MSSQLSERVER)"
  6. Select Stop ...and voila, port 80 was released
link|improve this answer
+1. It was indeed SQL Server in my case. – Assaf Levy Jan 3 at 10:53
feedback

telnet localhost 80 returns HttpAPI/2.0 which in turn means to "Sql server reporting service". Stopping the same releases port 80.

link|improve this answer
I found that SQL server reporting services was also the culprit. – J.T. Apr 6 at 20:12
feedback

Take ProcessExplorer, run it, open TCP/IP properties of every process (service), find process (service) that listening to http (80) port and switch it off.

I found Autodesk EDM Server was listening to http (80) port.

link|improve this answer
1  
This doesn't work for services running inside system (ie, with a PID of 4) – Nathan Reed Sep 4 '11 at 11:46
feedback

protected by studiohack May 15 '11 at 0:41

This question is protected to prevent "thanks!", "me too!", or spam answers by new users. To answer it, you must have earned at least 10 reputation on this site.

Not the answer you're looking for? Browse other questions tagged or ask your own question.