Error while trying to run project: Unable to start debugging on the web server. The project is not configured to be debugged.
I have planned to share my experience on the various .NET errors which I have faced till now and the solution for the same. This is the first post in this series.
Error: Error while trying to run project: Unable to start debugging on the web server. The project is not configured to be debugged.
Cause: Either debug is not enabled in your web.config (OR) For some reasons IIS is not considering your web application as a virtual directory. Instead it is considering it to be a normal folder.
Solution 1:
Step 1: Open the web.config
Step 2: If debug is set to "false" change it to "True".
For ex:
In my web.config I have a line like this <compilation defaultLanguage="c#" debug="false"/>
I would change it to <compilation defaultLanguage="c#" debug="true"/>
If at all this doesn't work. Try out the next solution.
Solution 2:
Step 1: Start >> Run >> inetmgr
Step 2: Navigate to the virtual directory of the project which is throwing this error.
Step 3: Right click on the virtual directory and choose "Properties"
Step 4: Next to the application name there would be a button named "Create". Click on it. [After that, the button should read as "Remove"]
If at also doesn't work, try the next solution.
Solution 3:
If you are running Visual Studio 2003 (or ASP.NET v1.1) you should setup IIS to use ASP.NET v1.1 and not ASP.NET v2.0
May be you have installed .NET framework 1.1 as well as 2.0 in your box and trying to run an application via VS.NET 2003. If so, then do the following:
Step 1: Start >> Run >> inetmgr
Step 2: Navigate to the virtual directory of the project which is throwing this error.
Step 3: Right click on the virtual directory and choose "Properties"
Step 4: Choose the tab ASP.NET
Step 5: The first dropdown would read "ASP.NET Version", choose 1.1.4322
That's it. Hope this helps somebody sometime somewhere in the world :)
Error: Error while trying to run project: Unable to start debugging on the web server. The project is not configured to be debugged.
Cause: Either debug is not enabled in your web.config (OR) For some reasons IIS is not considering your web application as a virtual directory. Instead it is considering it to be a normal folder.
Solution 1:
Step 1: Open the web.config
Step 2: If debug is set to "false" change it to "True".
For ex:
In my web.config I have a line like this <compilation defaultLanguage="c#" debug="false"/>
I would change it to <compilation defaultLanguage="c#" debug="true"/>
If at all this doesn't work. Try out the next solution.
Solution 2:
Step 1: Start >> Run >> inetmgr
Step 2: Navigate to the virtual directory of the project which is throwing this error.
Step 3: Right click on the virtual directory and choose "Properties"
Step 4: Next to the application name there would be a button named "Create". Click on it. [After that, the button should read as "Remove"]
If at also doesn't work, try the next solution.
Solution 3:
If you are running Visual Studio 2003 (or ASP.NET v1.1) you should setup IIS to use ASP.NET v1.1 and not ASP.NET v2.0
May be you have installed .NET framework 1.1 as well as 2.0 in your box and trying to run an application via VS.NET 2003. If so, then do the following:
Step 1: Start >> Run >> inetmgr
Step 2: Navigate to the virtual directory of the project which is throwing this error.
Step 3: Right click on the virtual directory and choose "Properties"
Step 4: Choose the tab ASP.NET
Step 5: The first dropdown would read "ASP.NET Version", choose 1.1.4322
That's it. Hope this helps somebody sometime somewhere in the world :)
Comments
After 2 days of searching, finally found out that this was the problem!!!
http://www.gotdotnet.com/team/csharp/learn/whitepapers/_Toc49569439
I still have a separate issue with RPC Server not available when trying to debug with a remote machine, means for the time being I'll have to use debug on the server :¬[
Two wasted days fabricating excuses as to why I haven't done much. I Can't believe how @#!%$ fiddly it is to make some Micros*ft products work. A complete waste of time. Why doesn't software come with intelligable diagnosis to pin-point exact causes for such issues.
Rant Rant Rant, best of luck, you'll need it.
http://www.gotdotnet.com/team/csharp/learn/whitepapers/_Toc49569439
Try concatenating these two strings:
http://www.gotdotnet.com/team/csharp/learn/
whitepapers/_Toc49569439
You'll need to concatenate these two strings to get the complete url
http://www.gotdotnet.com/team/csharp/learn/
whitepapers/_Toc49569439
Hmm.. (GRRR!, rather), why does this not work with .NET 2?
-dan
:-)
Thanks a ton :)
Then I decided to go with the famous aspnet_regiis -i and that did the trick.
HTH
rite now its working but ..when i start debugging it showing an error like "unable to start debugging ..debugging failed coz integrated windows authentication is not enabled."
why i am getting this?How to check it out?
plz mail me at
shalni_raj7@yahoo.com
Sam from Germany
edit bindings: point to the newly created cert.
http://blogershub.com/Archive/2014/2/Unable-to-start-debugging-on-the-web-server-The-project-is-not-configured-to-be-debugged