under menu bar, whenever i clicked Web Site > ASP.NET Configuration, i will have these errors:

------------
ASP>NET Development Server failed to start listening on port 2536
Error message:
An invalid argument was supplied
------------

next about few seconds later, another error pop-up

------------
Unable to connect to Visual Studio's Localhost Web Server
------------

note: the port number is random, normally is in the range of 2xxx
what's the reason i get these error and how can i solve this problem?

by the way, i've just installed V.Studio 2005 in winXP pro sp2 with no prev v.studio installed. For better picture, you may also like to see my another unsolved problem; 'current identity does not have Write access to Temporary ASP.NET Files' which i posted at http://forums.asp.net/1127559/ShowPost.aspx

your help is seriously needed and much appreciated. Thanks!

By default the port is a random system port, so that behavior is expected.

The error about being unable to connect to Visual Studio's Localhost Web Server can be solved 90% of the time by opening the web site properties and turning off NTLM Authentication for the site.  If you are using IE and you rely on a proxy server, make sure that in IE Internet Options you check the option for 'bypass proxy for local addresses' in the LAN Settings page.

---

-Dan
This posting is provided "AS IS" with no warranties, and confers no rights.

I am not on a proxy server, so the IE solution doesn't work for me.

And NTLM is NOT checked. Other suggestions?

 

encounter the same problem....

everyone can help?

 

You are not alone. I've run into the same problem and went so far as to turn off Windows firewall, and my other virus protection. Still does not work. I have the same setup XP SP2. Howevr I have no problem on my home version of XP, nor on WIN2K.

Well, let's hope we will find a fix for it. It works good at work on my PC but I would like to do some work at home...

 

hello, guys

I found someone report this "bug ?" to MSDN feedback center, the address is:

http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=55e1d51c-ca5b-4343-8317-891ab94632cd

you may go and check the status (under review now).

hope the fix will be out soon...

 

I game several troubleshooting steps for this error in the following post

http://forums.asp.net/1058543/ShowPost.aspx

Keep in mind that the thread is more than one page.  The final solution in that thread was NTLM Auth, but there are other possibilities for that error.  Here are some things to check.  See the thread for more details.

Does the file webdev.webserver.exe exist in C:\Windows\Microsoft.NET\Framework\v2.0.xxxxx?

Is IE your default browser?  Make sure in Internet Explorer, Tools | Internet Options, Connections tab, LAN Settings, that you have 'bypass proxy server for local addresses' checked if you are using a proxy server.

If Windows Firewall is running check Windows Firewall settings. Turn ON the option on the Exceptions tab to "receive notifications when Firewall is running".  It's possible Firewall is blocking webdev.webserver.exe

What happens when you press Ctrl+F5 instead of F5 to run the site?  Ctrl+F5 is 'Run Without Debugging'

What do you see in your browser when you type the address http://localhost:80 

---

-Dan
This posting is provided "AS IS" with no warranties, and confers no rights.

thanks a lot for your response

1, Does the file webdev.webserver.exe exist in C:\Windows\Microsoft.NET\Framework\v2.0.xxxxx?    yes

2,Is IE your default browser?  Make sure in Internet Explorer, Tools | Internet Options, Connections tab, LAN Settings, that you have 'bypass proxy server for local addresses' checked if you are using a proxy server.    IE is the only browser used. I am not using a proxy server, but join in a domain.

3,If Windows Firewall is running check Windows Firewall settings. Turn ON the option on the Exceptions tab to "receive notifications when Firewall is running".  It's possible Firewall is blocking webdev.webserver.exe    I just turned off Windows Firewall

4, What happens when you press Ctrl+F5 instead of F5 to run the site?  Ctrl+F5 is 'Run Without Debugging'    Same error message come out,  "ASP>NET Development Server failed to start listening on port 2536
Error message:
An invalid argument was supplied", and a few second later, another error message, "Error Unable to connect to Visual Stutio's localhost web server"

5,What do you see in your browser when you type the address http://localhost:80     IIS installed in my machine, localhost works fine, welcome message shows.

When i use Windows command shell, try to launch webdev.webserver.exe manually:

WebDev.WebServer.EXE /port:80 /path:"C:\Inetpub\wwwroot" /

error message: "ASP>NET Development Server failed to start listening on port 2536
Error message:
An invalid argument was supplied"  come out. it seems that asp.net development server does not start on my machine........

more details about system on my machine: IE version 6.0.2900.2180; Windows XP Pro with SP2, IIS Version 5.1, I have both Framework 1.1 (v1.0.3705 & V1.1.4322.0) and Framework 2 (v2.0.50727)

any help is much appreciated.

wentao, Do you see these error messages (Unable to connect to VS localhost web server...) even with a new file system web site?  And you made sure there is NO check in the checkbox for NTLM Authentication in web site properties?

When you tried to launch it manually you said you used the arguments:

WebDev.WebServer.EXE /port:80 /path:"C:\Inetpub\wwwroot" /

which are missing the vpath argument.  You also tried to start the web server listening on port 80 which is already in use by IIS.  Try using VWD to create a new web site at the location C:\mySites\TestSite, make sure NTLM Auth is unchecked, and try a Ctrl+F5.  If it doesn't launch then try to launch manually with a port other than 80, such as 5020. The command line would look like

WebDev.WebServer.EXE /port:5020 /path:"c:\mySites\TestSite" /vpath:/TestSite

---

-Dan
This posting is provided "AS IS" with no warranties, and confers no rights.

I found a solution to at least my situation. Our standard company XP build includes "Black Ice" from Proventia.  The buffer overflow intrusion protection was causing errors.  Verify that you do not have this or similar software running.

I have this same problem, but not the same solution...

I am running XP64. I have webdev.webserver.exe in the 32 bit framework but not in the 64 bit version. Might this be a problem with the distribution files for xp64? Or did I miss a file. I have tried reinstalling/repairing the install a couple of times now.

Thanks,

Bill Ross

---

http://bibleshockers.com

Good question, norisk.  While there are two Framework versions installed on a 64-bit machine (32-bit and 64-bit native), there is only one ASP.NET Development Server: the 32-bit version.  Visual Studio 2005 itself is 32-bit (devenv.exe).  So no, you are not missing a file.

ASP.NET Development server was tested throroughly on 64-bit machines and should work.  I'm on a 64-bit machine right now. I installed a new copy of Windows 2003 x64, and VS 2005 Pro yesterday and I can launch a file system web just fine.  The troubleshooting steps on a 64-bit machine are the same.  First, try run (not debug) a new web site with one page.  If that doesn't work, try running webdev.webserver.exe manually.  After that, follow all the troubleshooting steps above.

---

-Dan
This posting is provided "AS IS" with no warranties, and confers no rights.

Thanks for the clarification.

To clarify my problem...it is not that I cannot develop or run websites, which I can do. What is a problem is choosing "Website" and then "ASP.NET Configuration." It is then I get the "unable to connect' message.

Ok, I made 2 test websites of one page each - 1 using file system, the other using localhost. I was able to run from the command line and from the IDE but was not able to run ASP.NET configuration.

Bill Ross

 

---

http://bibleshockers.com

I too am having the same problem.  The same project works fine and allows the 'ASP.NET Configuration' option on a normal XP machine, but fails on a x64 machine.

I used sysinternals filemon program to watch what devenv was doing when the option was chosen and I wrote a 'interceptor' that intercepted the call to execute the WebDev.Webserver.exe file and report the parameters.

Basically on a x32 system, devenv executes WebDev.WebServer.exe twice, the first instance starts up the website as if you were debugging it:

1st)  WebDev.WebServer.EXE /port:3119 /path:D:\WebProj\Websites\WebProj /vpath:/WebProj

Then the second instance starts up the asp.net configuration website

2nd) WebDev.WebServer.EXE /port:1310 /path:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\asp.netwebadminfiles /vpath:/asp.netwebadminfiles

Now, on a x64 system, the 1st call to webdev.webserver.exe is executed correctly, but then the second call to start the configuration web site never occurs.  Instead the 32 bit version of aspnet_isapi.dll is loaded and right after that the "XP critical Stop" sound is played...

Definately some kind of problem with running VS 2005 under x64...

Thanks for the extra info.  I'll take a closer look on my x64 machine.

---

-Dan
This posting is provided "AS IS" with no warranties, and confers no rights.

Hello All,

I experienced the similar (Unable to connect to Visual Studio's Localhost Web Server) error too, after I installed/uninstalled various versions of .Net redistributable binaries. After much trial and error, I figured the cause of the problem-

1. First check the number of .Net (redistributable) versions you have installed within the Windows directory.

2. Then make sure that you repair or reinstall each of those run-time versions. For example, in my case I had the versions v2.0.50215 and v2.0.50727 on my machine; but, version v2.0.50215 had some issues.

Since my web site was originally compiled using this older version, IIS was looking for that version's runtime and hence the could not launch WebDev.WebServer.EXE successfully.

3. So, I reinstalled the v2.0.50215 redistributable on my machine; since, I am able to run my web site without any issues. So, just make sure that you have the correct version of the redistributables installed on your machine.

Note: I may be wrong here but, techinically, if I got rid of my web site's binaries and recompiled my web site, my web site would probably work as it would use the latest .Net version (v2.0.50727).

Hope this helps!

ciao,

mags

Dan,

I also have an x64.  I am also unable to go to the ASP.NET configuration.  I get that very unhelpful message with no other errors.  I have followed all the suggestions and items you have listed on the other threads and post on this group.

It just doesn't work.  It used to work, I know I had it working a month ago when I first installed the new visual studio 2005.  But now, it has stopped working.  The only difference on my machine is that I installed SQL2005 Developer edition, and I choose to "upgrade" the SQL Express version.

I'm wondering if something I did there could have caused the problem

Matthew

---

Matthew C. Hintzen
Senior Technology Consultant
Long Cloud Technologies, Inc.
Long Cloud Technologies, Ltd.
www.LongCloudTech.com

Some more information:

This is a rare one, and I think I?m about to use one of my incidents from my MSDN subscription on it.  I don?t think it is SQL developer edition on top of SQL express because my co-worker did the same thing and his stuff still works.  The only difference between our machines is I am x64 and he is 32 bit windows xp. 

Working with my co-worker I think I may know what the root of the problem is, but not what is causing it.

When he clicks his ASP.NET Configuration button for the first time TWO (2) instances of the ASP.NET Development Server (built-in web server) start up. One of them points to the project he is working on, and the other points to the ASP.NET configuration tool.

When I click mine, I  only get ONE instance of the ASP.NET development server.  It points to the project that I am working on, and I can click and run the project from it, but the second one doesn?t start up.  That is the problem I am pretty sure.  Any ideas?

Btw, We installed VS 2003, sql server 2003 SSRS 2003, VS 2005, Sql Express, then upgraded SqlExpress Instance to SQL Developer edition, in that order.

---

Matthew C. Hintzen
Senior Technology Consultant
Long Cloud Technologies, Inc.
Long Cloud Technologies, Ltd.
www.LongCloudTech.com

This may be due to missing ASP.NET registry keys. The reason could be if you had installed ASP.NET after the IIS metabase setting Enable32bitAppOnWin64 had already been set to 1. Because IIS had already been switched to 32-bit mode, the ASP.NET installation did not create the ASP.NET registry keys in the "64-bit" registry, only in the "32-bit" (redirected) registry.

To resolve this issue,

From a command prompt enter the following commands:
1>cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs set
w3svc/AppPools/Enable32bitAppOnWin64 0
2>%windir%\microsoft.net\framework64\v2.0.50727\aspnet_regiis.exe ? i
3>cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs set
w3svc/AppPools/Enable32bitAppOnWin64 1
4>%windir%\microsoft.net\framework\v2.0.50727\aspnet_regiis.exe ? i

What this does is switch IIS to 64-bit mode, run the installation of 64-bit
ASP.NET, switch back to 32-bit mode and then re-install 32-bit ASP.NET. Doing this
causes the right registry keys to be created. This allows Visual Studio to
correctly locate the path to WebDev.WebServer.exe so the Visual Studio dev web
server can be launched.

Let me know if this works,

Hotfixer