Yeah I had run across that document when trying to solve this myself. It doesn't seem to apply, I don't have any "open connections that aren't established".
I'm probably showing some ignorance here :) but why does the System have port 80 open, and can more than one process open a port?
Looks like Help in 2010 is provided by a webserver that opens up on port 80. I just happened to have hit F1 before trying to serve my site from port 80.
Of course once I serve my site from Port 80, Help in VS2010 no longer works :).
Hope this can help someone else.
Marked as answer by IanSul on Jan 04, 2010 11:23 PM
In my case it was because Web Deployment Agent Service (remote agent service for Web Deploy 2.0) was running. Unfortunately it's hard to track down which service/app has port 80 open the reported PID is (SYSTEM) because all services who use HTTP.SYS will
show up as SYSTEM having port 80 open.
IanSul
0 Points
5 Posts
Unable to launch the ASP.NET Development Server because port '80' is in use.
Dec 31, 2009 01:12 AM|LINK
Subject says it all.
Running Windows 7, VS 2010 Beta 2
When I try to run my website at port 80 I get that error. It works fine on another port, like 81.
If I run VS2010 NOT as admin I get a different error.
Failed to start ASP.NET Development Server on Port:80
Error:An attempt was made to access a socket in a way forbidden by its access permissions
Netstat shows that the system is using port 80.
Proto Local Address Foreign Address State PID
TCP 127.0.0.1:80 IANSUL1:0 LISTENING 4
> ps -id 4
Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName
------- ------ ----- ----- ----- ------ -- -----------
645 0 108 180 3 4 System
TIA
-Ian
bcanonica
Contributor
3082 Points
595 Posts
Re: Unable to launch the ASP.NET Development Server because port '80' is in use.
Dec 31, 2009 01:48 AM|LINK
Try this to start, seems to be a known issue.
http://www.microsoft.com/products/ee/transform.aspx?ProdName=Windows%20Operating%20System&ProdVer=5.1.2600.2180&EvtID=4226&EvtSrc=Tcpip&LCID
Thanks,
BC
Blog Void Impossible
IanSul
0 Points
5 Posts
Re: Unable to launch the ASP.NET Development Server because port '80' is in use.
Dec 31, 2009 08:22 PM|LINK
Yeah I had run across that document when trying to solve this myself. It doesn't seem to apply, I don't have any "open connections that aren't established".
I'm probably showing some ignorance here :) but why does the System have port 80 open, and can more than one process open a port?
IanSul
0 Points
5 Posts
Re: Unable to launch the ASP.NET Development Server because port '80' is in use.
Jan 04, 2010 05:29 PM|LINK
Still hoping to get an answer here.
IanSul
0 Points
5 Posts
Re: Unable to launch the ASP.NET Development Server because port '80' is in use.
Jan 04, 2010 11:22 PM|LINK
Finally figured this one out.
Let me introduce you to MSHelp 3.0 :)
Looks like Help in 2010 is provided by a webserver that opens up on port 80. I just happened to have hit F1 before trying to serve my site from port 80.
Of course once I serve my site from Port 80, Help in VS2010 no longer works :).
Hope this can help someone else.
guenavan
Contributor
4306 Points
1695 Posts
Re: Unable to launch the ASP.NET Development Server because port '80' is in use.
Jan 05, 2010 05:00 AM|LINK
How can this problem be reproduced?
I do not observe anything similar
Is not port 80 default one?
to server by default ASP.NET development server or by IIS?
IanSul
0 Points
5 Posts
Re: Unable to launch the ASP.NET Development Server because port '80' is in use.
Jan 05, 2010 06:08 PM|LINK
I was able to reproduce this problem by.
stefanne
Member
6 Points
2 Posts
Re: Unable to launch the ASP.NET Development Server because port '80' is in use.
Jan 27, 2012 08:32 AM|LINK
In my case it was because Web Deployment Agent Service (remote agent service for Web Deploy 2.0) was running. Unfortunately it's hard to track down which service/app has port 80 open the reported PID is (SYSTEM) because all services who use HTTP.SYS will show up as SYSTEM having port 80 open.
priyanka1212
Member
38 Points
30 Posts
Re: Unable to launch the ASP.NET Development Server because port '80' is in use.
Jan 22, 2013 08:01 AM|LINK
I had same issue and wasted my time in resolving it....
May be this solution could help others....
Right Click on project - Select 'Properties' - Select Tab 'Web' - In this tab under 'Servers' select option Auto-assign port .
Then save changes.. close you project and again open it.
and now try building and running the solution.
This worked for me.
India