Aspdotnet-Suresh

aspdotnet-suresh offers C#.net articles and tutorials,csharp dot net,asp.net articles and tutorials,VB.NET Articles,Gridview articles,code examples of asp.net 2.0 /3.5,AJAX,SQL Server Articles,examples of .net technologies

Unable to start debugging on the web server. The web server is not configured correctly. See help for common configuration errors. Running the web page outside of the debugger may provide further information

Jul 5, 2011
Introduction:

In this article I will explain how to solve unable to start debugging on the web server. The web server is not configured correctly problem in iis7.

Description:

In previous post I explained clearly about what WCF is and I explain how to create WCF sample and how to consume WCF service in our application. Now I will explain how to solve unable to start debugging on the web server. The web server is not configured correctly problem in asp.net. 

"Unable to start debugging on the web server.  The web server is not configured correctly.  See help for common configuration errors.  Running the web page outside of the debugger may provide further information."
This error causes because of your website stopped in IIS or some other properties missed in your application to solve this error follow below methods. 

First Method

In this method first check your particular website has started or not if not start your website
Open you’re IIS and select your particular website right click on that site and select Manage WebSite under that click start option.

Now test your application if it works fine then ok otherwise check another method

Second Method

1)    Open IIS and now select your application ---> Right click on that application and select Properties

2)    Now one window will open in that Select Directory tab ---> under that select Application settings  ---> Click on “Create” button (Once it created that button text will change to “Remove”)

After that click Apply and click OK button.

If you’re using IIS7 no need to do the first and second steps just select your application and right click on it and select option “Convert to Application

Now run your application and test it I hope it will work fine otherwise follow another method.

Third Method

1)      1) Open  IIS
2)      2) Select your website and right click and go to properties
3)      3) After that select  Asp.net tab
4)      4) Under that click on Edit Configuration
5)      5) Select Application Tab
6)      6) Under Select C# as default language and check the Enable Debugging checkbox

Some times that default language was set to vb. After set the above properties run your application now it will work for you  Still if it doesn’t work for your follow another method

Fourth Method

Open the command prompt and run ASPNET_REGIIS.EXE with -i parameter

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -i

Now test your application it will work for you. If not check another method

Fifth Method

1)      1) Right click on your project in VS2005 or VS2008 or VS2010.
2)      2) Click on Properties
3)      3) Click on Web tab
4)      4) Under Servers, click on the radio button Use Visual Studio Development Server
 5) Check Auto Assign Port radio button
5)      6) Uncheck NTLM Authentication and Enable Edit and Continue

Now run your application it will work for you. 

If you enjoyed this post, please support the blog below. It's FREE!

Get the latest Asp.net, C#.net, VB.NET, jQuery, Plugins & Code Snippets for FREE by subscribing to our Facebook, Twitter, RSS feed, or by email.

subscribe by rss Subscribe by RSS subscribe by email Subscribe by Email

6 comments :

Anonymous said...

I was trying to debug an old asp website with IIS 5.1 and Visual Studio 2010 and I was getting this anoying error message. Your fourth step worked for me, but changing the version of the framework to 4.0:
C:\WINDOWS\Microsoft.NET\Framework\v4.0.xxxxx\aspnet_regiis -i
(Replace the xxxx for your exact version)
Tyvm =)

Florin said...

My problem was that the virtual directories where not applications. After I converted them now I don't get this error anymore. Windows 7 64Bit IIS7.5

Victor vinoth said...

I'm trying to debug an issue with our website in Firefox. I'm using Visual Studio 2005 SP1, C# and ASP.Net. I've been using this installation for nearly a year with no problems. Yesterday I wanted to debug something in Firefox rather than IE so I changed my default browser to Firefox. I then hit F5 to begin debugging. The build succeeds, but nothing else happens. The debug never begins. Eventually the arrow turns green again so I click it again. The second time I get an error message: "Unable to start debugging on the web server." I click OK and get another message "Unable to start program 'Unable to start debugging on the web server. Click Help for more information.' The specified working directory does not exist or is not a full path."

I changed my default browser back to IE, but I get the same errors. I don't know if changing the default browser was the cause because I had not tried to debug that day prior to the change. If I select "Start without debugging," the app starts right up.

I've searched the net but have not found a definitive solution. Any ideas?

Sabih Khan said...

Thanks you so much this is the best :D

deweshpushkar said...

thanks a lot Sir

Anonymous said...

I was running into this issue in VS2008 after I did a "get latest" out of TFS. VS wanted me to create the virtual directory, although it already existed. I said no the first time, but then the solution wouldn't display in VS. So I said "go ahead and make the directory."

After the directory was created I started getting the "Unable to start debugging on the web server. The web server is not configured correctly. See help for common configuration errors. Running the web page outside of the debugger may provide further information" error message.

The suggestions above are very complete and thorough, however none resolved my error. For me it ended up being that when the new virtual directory was created automatically through VS, it created an incorrect IIS configurations.

There are multiple projects in my solution, and for each one I had to do the following steps:
1) right click the project.
2) select "properties".
3) select the "web" tab.
4) ensure that "Use local IIS Web server" was selected.
5) change the "Project Url" path to be what it should have been.

I also had to reconfigure the IIS settings because of the recreation of the virtual directory. I did the following for each directory created:
1) open IIS.
2) right click on directory.
3) go to "Manage Application"
4) go to "Advanced Settings"
5) corrected the "Physical Path", as that had changed to something that was not correct.

After I did these it worked correctly.

Give your Valuable Comments

Other Related Posts

© 2010-2012 Aspdotnet-Suresh.com. All Rights Reserved.
The content is copyrighted to Suresh Dasari and may not be reproduced on other websites without permission from the owner.