Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Oct 07, 2008 07:17 PM by Mikhail Arkhipov (MSFT)
Dec 04, 2007 01:34 AM|LINK
I downloaded VWD 2008 Express, and whenever I try to run any ASPX page to debug it or test it .. it gives me the following message in a messagebox:
"Unable to connect to the ASP.NET Development Server"
Anyone has an idea about it?
by the way VWD2005 works fine!
Feb 09, 2008 08:15 AM|LINK
me too,look at the ports they are not the same,when they are same then I have that error that you write..I have that error with visual studio 2008,but visual studio 2005 works just fine...
Feb 09, 2008 05:38 PM|LINK
This thread may be useful http://forums.asp.net/t/1209387.aspx
Feb 09, 2008 06:51 PM|LINK
Feb 26, 2008 09:15 AM|LINK
You probably have already solved as your post is about one year old but it may be useful to share my experience with other people who have the same issue, as there is no much on the web, and as someone said it is quite a rare issue. In my opinion there is
no bug, problem or anything like that, simply a conflict.
I have had the same problem and it was due to the fact I had Oracle® Database Express Edition 10g installed on my machine. Oracle once installed, gives you the possibility to access the XE database homepage directly via your browser. The url used to access
the XE database homepage typically takes one of the following forms:
As you can see your port 8080 (HTTP alternate port) is busy. I suspect that the standard Development Server for VWD 2008 for default works on the same port, differently for example from VS 2005 which random and automatically select one of
the unassigned port for you. Well I could uninstall Oracle or stop its XE services on my machine but I needed the DB GUI for another project so I worked round and forced my project to use a Development Server which works on another port and I did this way:
Step 1: Select the “Tools->External Tools” menu option in VS or Visual Web Developer.
This will allow you to configure and add new menu items to your Tools menu.
Step 2: Click the “Add” button to add a new external tool menu item.
Name it “WebServer on Port 8010” (or anything else you want).
Step 3: For the “Command” textbox setting enter this value:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\WebDev.WebServer.EXE (note: this points to the web-server that VS usually automatically runs).
Step 4: For the “Arguments” textbox setting enter this value:
/port:8010 /path:$(ProjectDir) (or any port you like)
Step 5: Select the “Use Output Window” checkbox (this will prevent the command-shell window from popping up.
Once you hit apply and ok you will now have a new menu item in your “Tools” menu called “WebServer on Port
8010”. You can now select any web project in your solution and then choose this menu option to launch a web-server that has a root site on port
8010 (or whatever other port you want) for the project.
You can then connect to this site in a browser by simply saying
All root based references will work fine.
Step 6: The last step is to configure your web project to automatically reference this web-server when you run or debug a site instead of launching the built-in
web-server itself. To-do this, select your web-project in the solution explorer, right click and select “property pages”.
Select the “start options” setting on the left, and under server change the radio button value from the default (which is use built-in webserver) to instead be “Use custom server”.
Then set the Base URL value to be: http://localhost:8010/
Obviously I don't know if this is the problem you had but definitely it is something similar, essentially the problem should be that the same port used by your Development Server is not available because it is
already used by another web server.
P.S. I used 8010 in my example as this port normally is unassigned.
Feb 28, 2008 03:04 PM|LINK
check your firewall settings maybe you forget to give permission
Feb 29, 2008 02:31 PM|LINK
I have Windows Vista Home Premium Edition. I installed VWD 2008 and after creating a test.aspx, I tried to start the server. I got this same error. Horrible!!! It is a killer. On my machine it connects to port # 49716. I tired spending several hours,
googling and tried all options. I could not get the server running.
Mar 06, 2008 11:48 AM|LINK
Finally I found the problem. I edited the hosts file which had an entry for local host like ::localhost. I commented this line out and it started working.
Jun 16, 2008 09:13 PM|LINK
I had the same issue w VS2008. My solution wasnt found on the web. After using sysinternals process monitor I found the path VS was using to execute the server was incorrect. I guess MS didnt take into account my system was a 64bit system. So I had to move
my DevServer folder to C:\Program Files\Common Files\microsoft shared\DevServer dir. In its present C:\Program Files (x86)\Common Files\microsoft shared\DevServer it was usless since MS was looking in the wrong location.
I hope this saves some other poor sap the time it took me to figure it out.
Jun 17, 2008 03:45 PM|LINK
I solved my problem,I uninstalled my eset nod 32 security suite that was blocking him and now everything woks perfect...