Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post May 27, 2010 08:37 AM by Ramesh Babu.B
Aug 09, 2007 07:08 PM|LINK
I create a new ASP.NET Futures project in Visual Studio 2008 Beta 2, and run it without making any changes, and the WebDev.Webserver.exe fails...perhaps i have a missing instiallation component? The funny thing is that there was one time when it did run!
Aug 09, 2007 08:44 PM|LINK
What is the error message that you are getting?
Aug 09, 2007 08:50 PM|LINK
Sorry, it was in the title:
WebDev.WebServer.exe has encountered a problem and needs to close. We are sorry for the inconvienence"
It shows a dialog box with the above error, and then after that there is another dialog box saying, "Unable to connect to local server"
Again, i didn't touch anything, but i suspect that there is a component that i am missing, except for that one time that it randomly worked!
Aug 10, 2007 05:05 PM|LINK
Does it only happen when you create a new "ASP.NET Futures Web Site"? What if you just create a new "ASP.NET Web site"?
Aug 10, 2007 05:27 PM|LINK
Ok, i tested it with a regular ol' asp.net website, and i get the same problem! (in Visual Studio 2008)
I then created an asp.net project in 2005 and it ran fine.
Is 2008 using a different LocalHost webserver then 2005?
Or is the web.config for the 2008 version looking for components that i don't have?
This probably works for everyone else right? Maybe i should mention, my enviornment
I have Visual Studio 2008 Beta 2. .NET 2.0, 3.0, 3.5 (Pre-release version). Microsoft ASP.NET 2.0 AJAX Extensions 1.0. Microsoft ASP.NET Futures (July 2007). Is there soem other ASP.NET component perhaps that i could be missing?
Aug 10, 2007 07:02 PM|LINK
This article might help:
Aug 13, 2007 02:59 PM|LINK
ok, i read the article, and the file C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\WebDev.WebServer.exe is timestamped at december 2006 (the last time i installed it 2005)...so perhaps then Visual Studio 2008 is looking for an older version of the Webdev.webserver.exe?
Is there a newer version though?
Sep 01, 2009 10:33 AM|LINK
try to register asp.net components with IIS
using aspnet_regiis -i
for more details :
again if its not working try repairing the complete installation
Sep 16, 2009 12:35 PM|LINK
Hello - I have the same error message on one site but, when i open another web-ste (solution) I can compile for debug with no issues. So, it doesnt appear to be the environment/ install. Could be something to do with the solution itself that is different
from the one that is compiling...
Sep 16, 2009 01:06 PM|LINK
ok .. here is how to solve this problem
1/ go to your project file for the start up project - open it in notepad - scroll to the bottom - lookup the following
the 2891 should then be placed in the project properties under web
look for the section entitled "Servers" , under which, you will find radio buttons. select the Use "Visual Studio development server" radio button. Next, select the radio button "Specific port" - place the 2891 ( in my case, yours may vary ) in the adjacent
Save your project and give this a try.
This should fix the issue.
Cheers and good luck!