Unable to Start Debugging on the Web Server

Tuesday, August 23, 2005 9:36 AM Filed under:

General

Unable to Start Debugging on the Web Server

I hate that, and it seems that every time I (or a co-worker) gets the error “Unable to Start Debugging on the Web Server” on a machine when attempting to debug an ASP.NET project, I have to scramble to remember what to look at. Here's a few things that has worked for me to get things working so you can debug your ASP.NET project when/if you ever get this error:

Make sure that IIS is configured to use Integrated Windows Authentication. Look for the checkbox on the Authentication Method dialog launched from the Directory Security tab of the site properties.
Make sure that HTTP Keep Alives are enabled. You'll find that checkbox on the Web Site tab of the properties dialog, in the connections section.
This one is strange, but it seemed to do the trick for many out there, add http://localhost to the trusted sites in Internet Explorer. To tell the truth, this seems to be a fix for the symtoms, not actually fixing the problem itself, but if it works it works. BTW, you'll have to uncheck the “Require server verification (https:) for all sites in this zone“ checkbox to add it as a trusted site.

Good luck.

Comments

BlackTigerX 8/23/2005 10:14 AM

I found this to be a very complete resource guide to solve this problem

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vstechart/html/vsdebug.asp
Ryan Farley 8/23/2005 10:18 AM

BlackTigerX,

Great link, thanks!

-Ryan
Phan 9/9/2005 3:17 AM

Hi

I have got a problem

"Unable to Start Debugging on the Web Server" on a machine when attempting to debug an ASP.NET project.

I am using WINDOWS 2003 SERVER. I have made some changes can any one help me.

Thanks
Phan
Phan 9/11/2005 9:24 PM

This is driving me nuts!

I read about 30 MS Knowlege Base documents and solutions from EE and can't make it works.

I am getting this error

"Error While trying to run project: Unable to start debugging on the web server. you do not have permissions to debug the server.
Verify that you are a member of the Debugger Users group on the server."

The facts:
-------------
- I am using VS.NEt 2003 on my computer(Windows 2003). I use c# to to asp.net on another server.
- Both are installed with the Framework SDK.
- Permission seems to be setup corectly (I am admin, I am in debugger groups)
- aspx is registered correctly on the remote server.
- A local standalone c# program will debug correctly.
- I have rereregistered the debugger on local and remote server.
- If i try to manually attch process, in asp_wp.exe, It work for Script ans MS T-SQL but not on Commun language runtime.

This Problem i got after installing Windows 2003 SP1.

Please Help!
Phan
Gayathri 10/26/2005 7:21 PM

Great link given by BlackTiger. thanks! It resolved my long pending problem.
doitlast 11/30/2005 1:18 PM

the last bullet works -- thx
Mike 12/1/2005 7:59 PM

Last bullet worked for me as well. Thx.
Daniel 12/7/2005 7:14 AM

I've have tried just about every possible solution in resolving this problem and I still am having this issue. I have restarted IIS by running iisreset in the command prompt. I have Authenticated the Web Site folders in IIS. I made sure the "HTTP Keep Alive is checked" and I tried the last bulleted item. Nothing works. Please let me know if there are any other suggestions.
Poindexter 12/7/2005 12:07 PM

Thanks Ryan. It was starting to look like a trip down the rabbit hole. I had disabled Keep-Alives to avoid occasional 403.9 errors I was getting. I'll take the 403's over no debugging!
fl0yd 12/16/2005 5:23 AM

HI guys,
I encountered a problem that I cannot solve... My settings on IIS are ok.
- Keep alive is enabled
- the ASPNET user under which the process runs has all the required write properties on the root web folder...
- I run the VS.NET with the admnistrator account, that is inserted in the Debugger Users group, in the VS Developers group, and in the Administrator Group.
- the debug option of the web.config is set to true
- the web.config is well formed and the application run without debugging

Can anyone help?

the message is: Unable to Start Debugging on the web server. Click Help for more information.

the help informartion is not useful.

thanks in advance
Mycroft 12/20/2005 5:16 PM

I was having the “Unable to Start Debugging on the Web Server” error on my localmachine when debugging simple local aspx apps (not web services). My initial resolution attempts included everything outlined under "Initial Attempts," and even reinstalling Visual Studio .NET and the .NET Framework 1.1 and 2.0 failed. But read on; I stumbled across a solution that might work for some of you.

Initial Attempts (taken from previous posts)
----------------------------------------------------
(1) Make sure that IIS is configured to use Integrated Windows Authentication. Look for the checkbox on the Authentication Method dialog launched from the Directory Security tab of the site properties.

(2) Make sure that HTTP Keep Alives are enabled. You'll find that checkbox on the Web Site tab of the properties dialog, in the connections section.

(3) This one is strange, but it seemed to do the trick for many out there, add http://localhost to the trusted sites in Internet Explorer. To tell the truth, this seems to be a fix for the symtoms, not actually fixing the problem itself, but if it works it works. BTW, you'll have to uncheck the “Require server verification (https:) for all sites in this zone“ checkbox to add it as a trusted site.

The Fix
----------------------------------------------------
(4) In IIS on the local machine, I brought up the web site properties. Under the tab labeled ASP.NET, I was using 2.0.5072. When I reverted back to version 1.1.422, the debug problems went away.
Christopher Weeks 12/20/2005 5:55 PM

changing the version back from 2.0.40607.0 to 1.1.4322.0 worked for me. But also note that you can do this on the properties dialog for the whole default web server and it hasn't caused a problem for me yet. Thanks for the info
Keval Solanki 12/22/2005 1:04 AM

hello,

1. go to the C:\WINNT\Microsoft.NET\Framework\<version dir>\Temporary ASP.NET Files

2. then rightclick it, select properties and then security tab

3. in that add the "ASPNET Machine Account" user and set the full reghts

so this will solve ur problem

just try this...

Regards,
Keval Solanki
Software Engg,Tatvasoft
Mycroft 12/22/2005 5:56 PM

Keval,

I tried your suggestion and it had no effect. The ASPNET Machine Account already had READ, EXECUTE & LIST rights. I elevated the rights and nothing changed. I then rebooted with no effect.

So far, the only "fix" for the “Unable to Start Debugging on the Web Server” error has been to revert back to using ASP.NET version 1.1.4322.

NOTE: On the same machine, ASP pages respond with "The Page Cannot Be Displayed." Changing the ASP.NET version does nothing to change this response.

WARNING FOR SHAREPOINT ADMINS
----------------------------------------------
I am using SharePoint Portal server and host both SPS and non-SPS web sites within IIS. The web site whose properties I was modifying was not a SharePoint virtual directory, runs under a separate application pool and uses a different identity. Despite this, when I reverted to the older ASP.NET version most of my application pools and web server processes stopped. It took SPS down fast, and the pools and sites did not auto-restart. So, I had to returned to using the newest ASP.NET version on the standard virtual directory and manually restart both the application pools and web services. It was a tremendous shock, but recovery was quick and simple.
Mycroft 12/28/2005 3:31 PM

Just to clarify some information about the situation, I am working with two different computers. After re-reading my previous submissions I realized it might have been confusing.

ANY RECOMMENDATIONS WOULD BE APPRECIATED. I WOULD LIKE TO USE ASP.NET 2.0 TOOLS, BUT CANNOT DEVELOP USING THAT ARCHITECTURE.

-- The first computer is the development environment workstation where ASP.NET version 1.1.4322 is being used. When we use the newer version of ASP.NET, Visual Studio.NET refuses to support the DEBUG mode by reporting “Unable to Start Debugging on the Web Server”.

-- The second is a server hosting SharePoint Portal Server 2003 which apparently requires the use of ASP.NET version 2.0.50727 on all web sites lest we crash the whole server by choosing a different ASP.NET version for any single site or sub-site. Also, this is a sensitive production server, so down-time is highly noticeable. The symptoms are: older ASP pages refuse to execute, AppSettings values from configuration files have intermittently refused to be available, and backing up the ASP.NET version is fatal.

CLARIFICATION (on the SharePoint Portal Server)
----------------------------------------------
-- On a standard web site, not a SharePoint Portal site though it is on the same server, ASP pages do not execute. It was reporting that the ASP pages did not exist, but something changed and now it reports "The Page Cannot Be Displayed" when one is browsed.

-- On these same standard web sites, ASP.NET code has intermittently refused to pull information from configuration files (such as web.config). They do not report failures; they simply do not return values (null). The problem has currently disappeared, but a cause is still not known.

CLARIFICATION (on the Development Workstation)
----------------------------------------------
This one is simple. Only VS.NET is affected; refusing to go into DEBUG mode when ASP.NET version 2.0.50727 is applied. Projects run but not in the VS debugger. When using ASP.NET version 1.1.4322, everything runs smoothly. This sounds like a simple solution -- simply use ASP.NET version 1.1.4322. If I do that, I cannot use the newer ASP.NET 2.0 coding improvements; some of which are significant.

<b>test</b>
RyanH 1/2/2006 5:22 AM

HTTP Keep Alives (solved my problem) - Thank you Thank you Thank you
danial 1/11/2006 10:35 AM

error while trying to run project; unbale to start debugging on the web server. the server dose not support debugging of asp.net or atl server application. runsetup to install the visual studio.net server compent setup has ben run verify tah valid url has been specified
Himanshu Patel 1/24/2006 6:54 AM

Last bullet point works .... hurray !!!!!! (Just add http://localhost to your trusted sites list) Thanks for your help
Boaz 1/25/2006 6:40 AM

I have tried absolutely all the above suggestions, including those in the MSDN URL - to no avail. Spent almost an entire day on this...

And then I found this: http://support.microsoft.com/?kbid=896861

I tried the first workaround (disable the loopback check), and
yes!!!!!!!!!!!!!!! That did it.
(Note that this solution is for the following cases: "if you install Microsoft Windows XP Service Pack 2 (SP2) or Microsoft Windows Server 2003 Service Pack 1 (SP1)").
Grant 1/26/2006 2:32 PM

In my case it was the "Enable HTTP Keep-Alives" that did it.

This resource is also useful:
http://www.gotdotnet.com/team/csharp/learn/whitepapers/_Toc49569437
Grant 1/26/2006 2:34 PM

D'oh. that was stupid, the link doesn't work.

The real link is:
http://www.gotdotnet.com/team/csharp/learn/whitepapers/howtosolvedebuggerproblems.doc
Wesley Shephard 2/3/2006 6:21 AM

I would like to thank Boaz for the loopback check fix. I was encountering this exact problem.
Wil.k 2/8/2006 12:19 PM

This was driving me NUTS. I tried everything, lots of stuff on the net about this.
The only thing that worked for me was to manually reregister mdm.exe

From command prompt:
%CommonProgramFiles%\Microsoft Shared\VS7Debug\mdm.exe" /regserver

Hope this helps ;-)
Jonathan 2/16/2006 7:14 AM

.NET asp app written under version 1.0. At some stage .NET v1.1 loaded on. App will no longer debug.

Tried all above, permissions, IIS tweaks etc. Nothing worked.
Ensured aspx/asmx in virtual directory were calling .NET v1.0 - nothing worked.

However, a newly created web app ran and debugged fine under .NET v1.1.
Hence I thought it must be a mapping problem.

So deinstalled .net v1.1 and v1.0. Reinstalled v1.0.
Still didn't work.
Backuped code and deleted IIS application virtual directories.
Then used Visual Studio to recreate project virtual directories in IIS (File - New Project) - in this way they should be setup okay. Tested dummy web service - worked okay.
Copied in application code - and it works!

So it seems there was some confusion somewhere with regard to calling the v1.0 .NET framework. I also noted that although the v1.1 update changes the IIS mappings all my visual studio project files still related to version 1.0.
Notaclue 3/20/2006 5:39 PM

(4) In IIS on the local machine, I brought up the web site properties. Under the tab labeled ASP.NET, I was using 2.0.5072. When I reverted back to version 1.1.422, the debug problems went away.

worked for me. Thanks!
sicc 3/29/2006 5:40 AM

For those that have tried all the stuff above and still have the problem, the way I solved it was to run:

C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i

I have found this fixes quite a few problems that i've come across in visual studio.
Mahesh 4/3/2006 2:53 PM

Thanks!

First solution worked for me.
Phil Morris 4/6/2006 1:41 PM

Unbelievable! Keepalives did the trick for me as well. Migrated a solid VS2003 site to VS 2005 (gotta luv the imporvments to the iDE etc) but struggled for a day trying to get the debugger to work. IIS is set up with NET 2.050727, and the website runs in an app pool set up specifically for VS 2005 (cannot run VS 2003 and VS 2005 website from the same app pool)
susanta 4/26/2006 1:47 AM

hi guys
really i'm facing such problem from last 1 week still i did not got any
solution,plz any body help to me on this situation Unable to Start Debugging on the Web Server

my mail id
susantacool@gmail.com
Renato Vizuet 4/26/2006 7:48 AM

Definitely you're the man.

Thanks for your complete and concrete help to solve this.
Shyamasundara K 5/22/2006 12:57 AM

Thanks

It is working!
Gustavo 6/1/2006 10:51 AM

I have been trying for months this problems... I need help. ASP.NET 2003 with Windows server 2003, trying to debug from a laptop in a network, a application in the server. I am frustated.
Ryan Farley 6/1/2006 10:59 AM

Gustavo,

I ran into a similar issue just this week. The problem was that the project files were on a second drive on the system and they did not have proper permissions to debug the files on the other drive location. I just moved the files to the local inetpub and all was good. So, basically, you'd want to start looking at permissions for the current location. Not sure if that is exactly your problem or not, but sure does sound like what I dealt with this week.

Good luck.
-Ryan
Dan Meineck 6/7/2006 1:13 AM

It could be that you are attempting to debug a v1.1.4322 site whose virtual directory or parent website is set to run under .NET 2 - thanks for the lack of explanatroy error message ms!
James E 6/14/2006 7:59 AM

Another possible solution if you can "attach" to asp_net and debug but it won't debug in the IDE it to verify that the "Debugging, HTTP URL" is correct. Creating a project in an existing solution will likely set the URL above to localhost/solution/project. However, the project will still deploy to localhost/project.
Victim393 7/4/2006 8:42 AM

Holy crap! I have looked for weeks and reinstalled many times VS.Net 2003 Pro and could not get the debugger working. Then, as a last ditch effort, I thought I would search one more time and came across your site. Saw "Make sure that HTTP Keep Alives are enabled" which I had not seen before and poof! now my debugger works! Awesome, thanks for the tip!
testal 7/10/2006 12:24 PM

Great. Changing the version of ASP.NET v2.0 to v1.1 worked.
I am using Windows XP with VS 2003.

--- Here is the procedure I took ---
1. Changed ASP.NET version by using IIS Property dialog box
2. Restarted iis with iisreset command
3. Run VStudio 2003 Debugger from IDE. WOhoo.
er 7/11/2006 1:33 PM

If none of the solutions worked, take a look at this article also.
You may find a solution as I did.

http://www.egilh.com/blog/archive/2005/03/17/602.aspx?Pending=true
Ravishankar 7/16/2006 8:00 AM

Solved the issue
Ravishankar 7/16/2006 8:06 AM

Guys, try this out and see...
1) go to IIS
2) right click the webapplication folder (which is not working)
3) Then, go to Prperties ->Directory ->Configuration ->debugging
4) check the two check boxes (client side and server side ebugging) to TRUE.
It worked for me.
Steve 7/21/2006 6:56 AM

The debugger used to work but doesn't now.

I have installed SQL Server Report Services Service Pack recently and suspect this is to blame (though I can't be sure).

Interestingly, if I log on as administrator I can still run the debugger.
When I log on as me, I get the usual error message. OS is Windows Server 2003.

"Error while trying to run project: Unable to start debugging... ...Verify you are a member of 'Debugger Users' group on the server."

Can I compare the rights of admistrator to my rights? I believe they're the same but I have nothing else to go on!

Many thaks.
Alex 8/2/2006 4:37 AM

I get this error:

Unable to start debugging on the web server. The debugger cannot connect to the remote computer. This may be because the remote computer does not exist or a firewall may be preventing communication to the remote computer. Please see Help for assistance.

I don't really understand this error since I'm able to create the application on the server.

My host is a windows XP pro sp2 with Visual Studio 2005 installed. The server is a windows 2003 server. I'm running windows 2003 server on VMWare with it's own IP on the network. I've configured the host file to accept an URL to the servers IP so the project is created with that URL.

Any ideas?
Alex 8/2/2006 8:29 AM

Yea, turning of the firewall will work, doh.... so, what ports do I need to open on the server more than 135?
efim 8/17/2006 6:36 AM

for machines that have both .net 1.1 and 2.0 and installed both ASP.NET versions you have to select the right framework version (1.1) in the virtual directory properties
EricTN 8/17/2006 10:34 AM

This happened to a guy in our shop. We have 2003/1.1 and 2005/2.0 installed on the dev workstations. He was trying to debug a 1.1 web service located in wwwroot. Turned out there was a web.config, at wwwroot, one level above the folder that contained his web service and his web.config. The upper web.config had some 2.0 elements in it like <connectionStrings></connectionStrings>.

When he renamed that 2.0 web.config to something else to neuter it, that got rid of the "Unable to Start Debugging on the Web Server" error.
suhesh 8/21/2006 10:40 PM

i too have the same problem of not being able to start debuggin on the web server.IIS is working fine......user account is working fine....when i start without debugging it shows "Server application unavailabe"..how can i solve this problem...plz help...
Steve Hebert's Development Blog 9/1/2006 11:05 AM

I love this error - it's truely hideous and the MSDN docs are worthless. Everytime I've run into
AlexB 9/8/2006 12:00 PM

Thank you Boaz for the Tip !!!
After two days of useless search.
This article helped:
http://support.microsoft.com/?kbid=896861

Disable the loopback check ... Go figure ...
Glenn 9/12/2006 8:49 AM

Thanks for this blog entry! Adding the http://localhost worked for me.
prav 9/17/2006 4:20 PM

Just and Info: I had this problem of "Unable to Start Debugging on the Web Server" - After lot of reading blogs and solutions i found that someone had changed the web.config file...

FROM:
<compilation debug="true" defaultLanguage="c#" strict="true" explicit="true" />

TO:
<compilation debug="false" defaultLanguage="c#" strict="true" explicit="true" />

This will stop you from debugging.

Cheer
youray 10/4/2006 2:04 AM

Unable to start debugging on the web server. (here comes some error messages with html tags (probably from iis)).

Make sure the server is operating correctly.. blablabla....

nothing helps, i've also reinstalled msvs and iis and nothing heeeelps me :(

any ideas?

youray
Punk-Coder Blog 10/4/2006 10:59 AM

I ran into this today and thought that I would put a like to it on my blog. ASP.net has a problem running the virtual server without windows authentication. So here is a link to the solution. Enjoy
IGNUS 10/6/2006 9:00 AM

(4) In IIS on the local machine, I brought up the web site properties. Under the tab labeled ASP.NET, I was using 2.0.5072. When I reverted back to version 1.1.422, the debug problems went away.

this one solve the problem.

Thanks everybody
Paresh Dhokte 10/8/2006 9:42 PM

Hi All..

I have tried almost all the solution i found here on this site..still I am having same problem..plz tell me how to resolve the above problem ??

Problem is :- When I try to run web application in VS 2003 it gives me error like : " Unable to debug on the web server.Click help for more information."

Regards,
Paresh D.
Nata 10/12/2006 1:20 AM

Hi

I've installed IIS after VS2005 and have had the same problems with debugging.
If you first installed VS and then IIS, you should reinstall .NET Framework using "Repair" option (you do not need to reinstall Visual Studio)

Hope it'll help in some cases
Ryan Farley 10/12/2006 6:46 AM

Nata,

No need to reinstall to fix that scenario (installing IIS after VS) to get ASP.NET to work, you just need to run aspnet_regiis from the appropriate .NET Framework folder with the "-i" switch.

For example, running the following would fix this (for .NET 2.0)

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

This just takes a few seconds to run and much easier than reinstalling the framework.
Rolf 10/12/2006 2:55 PM

Somebody give Ryan + Nata a cookie! After trying EVERYTHING I could find, that fixed it.
Bryan 10/20/2006 10:47 AM

The first item on your list worked like a charm. Thanks alot.
Jim 10/24/2006 12:58 PM

While trying to debug on my local box, I found something else that can cause the infamous "Unable to Start Debugging on the Web Server".

- I had been moving some things around on my box (Windows Server 2003, SP1), so I had inadverently broken the root website by removing the directory that it was pointing to.

- When I tried to debug a web service that was a virtual directory, I got the infamous "Unable to Start Debugging on the Web Server".

- When I reset the directory of the root website to a directory that actually existed, I didn't get an error message about the debugging. However, I get an error message about not being able to find a DLL.

- It took me a couple minutes to realize that this wasn't an error with the site I was trying to debug; instead, the directory that I had set as the home directory for the root website was referring to a DLL that I didn't have on the system. Once I took care of the problem in the root directory, I was then able to actually debug my web service.

HTH,
Jim.
Peter 10/30/2006 12:36 AM

Yes, I looked at various fixes for this error, but none mentioned the Keep-Alives being set. I un-set this on Friday at work, forgot about it on Monday and spent half an hour wondering what was going on!

Thanks.
chandramani 11/2/2006 12:53 AM

thanks a ton
Jerry T. 11/3/2006 10:46 AM

The DisableLoopbackCheck registry fix worked for me!
Igor Jerosimic 11/10/2006 2:13 AM

I resolved this issue by moving http://localhost from trusted sites to intranet sites in IE...
Pazu 11/20/2006 9:41 AM

My problem was wrong setting of "Local Intranet" security zone in IE, I had set "Promt for user and password"....
errantNite 12/5/2006 4:19 AM

I tried all the above and nothing worked. I removed the project from the solution, created a new virtual directory in IIS and re-added the project from the new site.
Mike Rustici 12/13/2006 12:19 PM

My solution to a half day's head banging was to add http://localhost to the Trusted Sites list. Additionally, I had to set that zone's security level back to Low. Somehow I had it set on Medium which blocked the debugging.
Dilip Nikam 1/1/2007 10:29 PM

Hi freinds.......

Its Working Perfectly On My Comp. just try it.

http://weblogs.asp.net/pgielens/archive/2004/08/20/217884.aspx

Open your Internet Information Services manager and from the [your machine]/Web Sites/ Default Web Site node select the virtual folder which stores your project. Right Click and select Properties to select the ASP.NET tab page. Make sure the correct version ASP.NET Version is selected.

I have VS.NET 2003 and 2005 beta 1 running side-by-side on my box and noticed ASP.NET Version 2.0 is targeted by default, even for VS.NET 2003 projects.
DanKline 1/2/2007 9:11 AM

Working with Vista and VS2005 with IIS 7.0

For those of you working with Vista and IIS 7.0, the IIS configuration Manager has a different look and feel. I was working with the companion software for Dino Esposito's ASPNET 2.0 Applications and was pulling my hair out. I had to set the Application Pool "Mamanged Pipeline" value to "Classic" rather than "Integrated".

I'm not sure why yet, but I believe it may have had to do with some of the modules in the compiled component library.
Jack Wu 1/8/2007 9:16 PM

My environments are:
1. Win2003 server
2. VS2005

I also experienced the same problem and I found this problem as following:

1. When you create a new WebSite project by VS2005 and do not change the default location the wizard created for you. For example, it will create a new WebSite1 on the directory C:\Documents and Settings\Administrator.JACK\My Documents\Visual Studio 2005\WebSites\WebSite1, then you can debug your web application successfully.

2. If you copy the exist web project to other directioy and add the project into the VS solution, then you will experiencing the debug error. For example, if I copy the WebSite1 to any other directory, then add this project into my new VS solution, then I will not able to debug this web project.

I do not know why it will be this result but if you create a new web site project by default location and keep it in the original location, then you will be able to debug your web project.
MANOJ - YEP FIXED!! FI 1/10/2007 7:53 AM

Unable to Start Debugging on the Web Server. The RPC Server is Unavailable

#######################

SOLUTION

#######################

I was getting this error but now fixed it, after trying everything it was very simple step that fixed it.

Solution: Go to "Network Connections" & go to connection properties and if you disable the FIREWALL IT WORKS FINE!!! :D

(or u might have other firewall?)

basically disable firewall or grant required permissions.

HAPPY DAYS!! i hope it works for you guys too LOL
proshad 1/23/2007 9:59 PM

hi friends,
while debugging i get an error message "unable to start debugging on the web server. the web server is not configured correctly. see help for common configurations errors. running the web page outside of the debugger may provide further information"

i configured IIS but it is not working.
plz help me

proshad from bangladesh
Chris 1/25/2007 7:35 AM

Thanks for the help - i now want to set my Debug start page to "trace.axd" and in VS 2003 it is clear: (Project, Properties, Configuration Properties, Debugging, Start Page) but in VS 2005 it is not the same... In fact, it seems to want to check out the project and change the Start Page for all developers using the project! This can't be correct- any help would be greatly appreciated, and in the meantime if I find the solution I will post it here.
John 1/25/2007 11:30 AM

I am using Visual Studio 6.

I am doing everything that you are saying and it still does not work.
Prasant Kumar Rout 1/25/2007 4:15 PM

Great Links,

Make more easy to solve this kind of typical problems

Thanks :)
Marthin Freij 1/29/2007 12:01 PM

Added http://localhost to "Local Intranet" in IE7 and problem was solved.
Shawn Englerth 2/1/2007 12:15 PM

here is an awesome solution!!!! I tried every other thing in a dozen posts but this is what worked for me!

http://www.aspmessageboard.com/forum/showMessage.asp?F=20&P=1&M=862991#863099
iyyanar 2/15/2007 10:20 PM

Server Application Error
The server has encountered an error while loading an application during the processing of your request. Please refer to the event log for more detail information. Please contact the server administrator for assistance.
Anbu 2/15/2007 10:23 PM

When i run asp.net project that time display the below message in explore.Please anybody give me the solution of this problem.
Server Application Error
The server has encountered an error while loading an application during the processing of your request. Please refer to the event log for more detail information. Please contact the server administrator for assistance.
James 2/17/2007 5:18 PM

RE: Igor Jerosimic
I resolved this issue by moving http://localhost from trusted sites to intranet sites in IE...

Thanks man, I've been going through all of these items and for each one I tried it made sure to back out the change before going on to the next one. This is what did it for me. I'm running IE7.
Jason 2/19/2007 10:44 AM

Just want to contribute one more case in case anyone had the same problem that I had.

I had both VS.net 2003 and 2005 installed on my machine, somehow in IIS the asp.net verion was messed up. After changing it back to correct version, it works just fine.
Phil 2/19/2007 1:19 PM

** MY SOLUTION **

I opened the website in IIS and clicked the "Create" button to create the application and that fixed it.

what a pain in the ass!
abs 2/20/2007 1:56 AM

with special thanks
Hi to all
i install ie7 then this problem occured.
to resolve error, i uninstall ie7 and then removing http://localhost to "Local Intranet" and problem was solved.
mahmood 2/25/2007 10:55 PM

thanks god
thanks Ravishankar

I was getting the error: "unable to start debugging on the web server. the project is not configured to be debugged"

bellow method solved that :

> Guys, try this out and see...
> 1) go to IIS
> 2) right click the webapplication folder (which is not working)
> 3) Then, go to Prperties ->Directory ->Configuration ->debugging
> 4) check the two check boxes (client side and server side ebugging) to TRUE.
> It worked for me.
sait 2/27/2007 5:03 AM

Unable to create the web'Http://website'. Server error:unable to process request.
<img src="http://teknikdesign.co.uk/vs05/vs05error.jpg" border="0" alt="" />
sait 2/27/2007 5:06 AM

Unable to create the web'Http://website'. Server error:unable to process request.
<img src="http://teknikdesign.co.uk/vs05/vs05error.jpg" border="0" alt="VS05 Error" />

I get this error with asp.net 2.0 / VS05 , but not with 1.4.net vs05. I have looked at MS website but have not seen any solution
karri 3/7/2007 10:09 PM

hi,
i have a problem,

i have a dll installed on remote machine and the development project on different machine.

from the development machine i want to debug this project using aspnet_wp.exe process of the remote machine. how can i do it?

your valuble suggestions are very much regarded.

thanks & regards
karri
email: nivas_s_k@yahoo.co.in
TheEagle 3/13/2007 12:32 PM

I had this error for the whole day then after returning to msdn I found that I should re-register asp.net for IIS as following:

To re-register ASP.NET
From a command prompt window, run the following command: systemroot\Microsoft.NET\Framework\ versionNumber \aspnet_regiis -i
Soulsick07 3/13/2007 5:27 PM

Really thanks everyone, i tried all this, and nothin, but NOW, here i read "move the LOCALHOST of trusted sites to Intranent" and u know what, works great.. thanks again, i hope u can fix it too.
vasanth 3/18/2007 2:53 AM

thanks man that links gives me the full details hands of bugs
sandra 3/19/2007 3:26 PM

I had the same problems. I found that logging into the machine with an account other than the built in Administrator account works fine. Probably security-related - the root user after all...
Andrade 3/22/2007 4:22 AM

http://msdn2.microsoft.com/en-us/library/0y3b8byc(VS.80).aspx

This article solves the problem brought about the following message:

---------------------------
Microsoft Visual Studio
---------------------------
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.

Click Help for more information.
---------------------------
OK Help
---------------------------

andracom[at]terra.com.br
Miszou 3/31/2007 9:51 AM

I haven't read all these comments, so someone else may have already said this...

On Windows Vista with Visual Studio 2005, I had changed the web application to use the "Classic .NET AppPool" application pool, and it started working immediately... Good Luck ;)
Firas 4/4/2007 11:50 AM

Like Mycroft mentioned on #3 the fix for me was moving localhost from trusted zone to intranet.
Himani Sharma 4/16/2007 7:22 AM

Thanx sicc

I tried every single given solution,including the bulleted points,changing the version(rcvd errors upon changing)...but the only one that worked for me was this.

C:\WINDOWS\Microsoft.NET\Framework\<version number>\aspnet_regiis.exe -i
migu 4/20/2007 8:51 AM

Also had same problem,

the "C:\WINDOWS\Microsoft.NET\Framework\<version number>\aspnet_regiis.exe -i" COMMAND fixed it
Manoj 4/22/2007 10:15 AM

Unable to Start Debugging on the Web Server. Click Help for more inormation.

#######################

SOLUTION

#######################

How i got this error:-
1) installed VS.NET 2005 on fresh xp copy (worked fine) LOL read on
2) installed most of the xp upgrades sp2, ie7 etc.
3) later decided i want 2003 too so i installed VS.NET 2003

now i couldn't debug using VS 2003
tried different thing but the one that fixed the error was: -

### SOLUTION ###
Right click on the virtual director of your project in IIS and go to ASP.NET tab. AND SELECT ASP.NET Version 1.xxblaxx

and it'll work!

Hope that helps
Pranil 4/25/2007 10:02 AM

hey Mycroft

that was the solution for me

Thanks
Seng 5/8/2007 12:13 PM

Karen Friend of mine just come and help me out. remove virsual directory from IIS, from VS2005 project select web tab and let VS2005 creat visual directory. After that you need to check IIS and refresh and make sure Virsual Directory , application name point to the project you want if not click remove and add. After that Directory Security, Edit authentication mode make sure select Integrate Window Authentication. Last thing Document tab you need to add Default.aspx etc..

Hope this help
Mike H 5/9/2007 6:07 PM

In my case the problem was that .Net 2.0 was the settings for default site, but the app I wanted to debug was a 1.1 site.

I used Denis Bauer's ASPNetVersionSwitcher tool to change the .Net version for the site in IIS, and VS then started debugging happily!

Cheers!
Skippo 5/25/2007 1:00 AM

I tried many things (including re-reginster .net 2.0 to IIS) but nothing worked.

It looked like the mapping webapp to .NET 2.0 was the problem.

I check-out the solution from SVN to completly new directory, created new virtual directory on IIS for that new directory and - it worked!

Somehow VS,.NET,ISS (dunno) didn't like my prev directory (and virtual directory probably too).
Andy 5/29/2007 6:51 AM

I have 2 sites set up both with local IP address access. Neither worked when I added them into the trusted sites zone. But did when I added into the Local Intranet Zone. There seems to be a difference for some reason.
Richard Fisher 6/5/2007 6:06 AM

One small aspect not to overlook is:

In your Web.config file, in the compilation attribute, is Debug set to "True"?

This one had me pulling my hair out!!

Hope it helps.
Joe Shmo 6/13/2007 9:25 AM

<compilation defaultLanguage="vb" debug="true" />

wow that was it...
ivan 6/21/2007 11:33 AM

The other thing to know you may debug the following frameworks in the following VS

VS 2002 - .NET 1.0 ---- only
VS 2003 - .NET 1.1 ---- only
VS 2005 - .NET 2.0 ---- only

There is no cross version debugging available.
Graham 6/26/2007 4:28 AM

Is anyone else having problems Profiling on Windows 2003 Server?

I am using ProfileSharp, and it works fine on my local machine, but now I am load testing the server and it just doesn't pick up the process.

It looks for the aspnet_wp.exe process, which is running as ASPNET on both machines.

Has anyone experienced similar, or knows what this could be? I have tried all the stuff in this post and nothing seems to help.
feline 6/29/2007 9:37 PM

hi

I am using Visual Studio 2003 on vista home premium, it kip showing this error : Unable to start debugging on the web server. Debugging failed because integrated windows authentication is not enabled.

wad shld i do?

plz help..

thx
Mahbub 6/29/2007 11:44 PM

I have got a problem

"Unable to Start Debugging on the Web Server" on a machine when attempting to debug an ASP.NET project.

I m using MS SQL Server 2000 with windows XP Proffessional

Thanks and Regards
Mahbub
New Delhi
mohdmo 7/3/2007 3:45 AM

check the IIS configuration for your application, check the asp.net tap the version you r using, and check the authentication on the directory security tap; it must be integrated windows authentication...

hope this help
Claudio 7/10/2007 9:26 PM

*** THANKS MANOJ!!!! Spot on your solution below:

#######################

SOLUTION

#######################

How i got this error:-
1) installed VS.NET 2005 on fresh xp copy (worked fine) LOL read on
2) installed most of the xp upgrades sp2, ie7 etc.
3) later decided i want 2003 too so i installed VS.NET 2003

now i couldn't debug using VS 2003
tried different thing but the one that fixed the error was: -

### SOLUTION ###
Right click on the virtual director of your project in IIS and go to ASP.NET tab. AND SELECT ASP.NET Version 1.xxblaxx

and it'll work!
abi.exdream.com - Benjamin Nitsc 7/13/2007 3:59 PM
Adriana 7/16/2007 1:07 AM

go to IIS, properties, ASP.NET tab, edit configuration, Application tab and check "enable debugging"
Raj 7/23/2007 9:38 PM

Hi all,
Error:

Error while trying to run project: Unable to start debugging on the web server. Server-side error occurred on sending debug HTTP request.

Make sure the server is operating correctly. Verify there are no syntax errors in web.config by doing a Debug.Start without debugging. You may also want to refer to the ASP.NET and ATL Server debugging topic in the online documentation. Would you like to disable future attempts to debug ASP.NET pages for this project?

The above error will come if your web.config or webinfo file got error.

You must read the error carefully before you are finding the solution.

Please read the below URL to may help you:
http://support.microsoft.com/kb/306172
But after I read the article still I cant able fix my issue.

Finally I found error in Webinfo file. The following things need to do:
1). Change your webinfo file
2). Delete your Virtual Directory and Re Create.
Yoga 7/26/2007 1:14 AM

Hi all,
If you get error "Unable to start debugging on the server" and if you are using vs.net 2003 and installed .net 2.0 follow the steps to solve.

1. IIS
2. Right click your web application
3. Go to properties
4. ASP.NET tab
5. change the version from 2.0 to 1.1
6. Now start debugging

thanks,
yoga
smash_pants 8/2/2007 9:42 PM

This isn't the firs time that i have received the"The project is not configured to be debugged" error.
It may have been a visual studio crash that caused this one.

none of the solutions here or at http://geekswithblogs.net/timh/archive/2005/09/14/53756.aspx
helped me.

However, the post by Skippo gave me a hint that it could be virtual directory at fault.

i deleted and recreated the Virtual directory but it didn't help.
I tried creating an exact copy of the virtual directory (path, permissions etc.) with a different name.
IT WORKED!

all i needed to do was change the address in my .webinfo file to the new virtual directory name.

However I'd still like to get the original virtual directory name working so i appreciate any suggestions you might have.
Neil 8/17/2007 9:35 AM

We had this error pop up all of a sudden. It turns out it was the security permissions on the web.config file. the ASP.NET process needs read access to this file. For some reason it was not inheriting it from the parent directory. Can't figure out why. All worked again once the "ASP.NET machine account" was added.
Susan 8/20/2007 6:36 AM

I am still getting this error message. I have tried everything that I found in this blog. We converted an application from 1.1 to 2.0 and don't want to revert back. We want to run in 2.0.

Could it be that the conversion wizard left something in 1.1?

These are all the steps I have taken:
- in Users, we have ASP.NET Machine account
- deleted and recreated the virtual directory but that didn't help
- created an exact copy of the virtual directory with a different name
- debug="true" in web.config
- execute permissions = scripts only in virtual directory properties
- virtual directory name should be the same as the physical directory name
- ran C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -i
- in IIS, the correct version of ASP.NET is selected--it's 2.0, which is what I want. This application has been recently converted from 1.1 to 2.0
- web.config looks good
- HTTP Keep Alive is checked
- IIS is configured to use Integrated Windows Authentication
- added http://localhost to the trusted sites for local intranet
- in C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files, I set full rights to "ASPNET Machine Account"
- disabled the loopback check
- verified we had Windows XP service pack 2 installed
- in IIS, verified that client side and server side debugging set to true
- verified that firewall turned off
- in IE, set security level to low.
- changed web pool to be the "Classic .NET AppPool"
- verified that in IIS properties, Document tab, I had Default.aspx

Any advice would be greatly appreciated!
Thanks
MEXICAN 9/12/2007 10:33 AM

IF YOU ARE USING VISUAL STUDIO,
YOU MUST TO UNCHECK THE "ASP Debugging" IN THE PROJECT PROPERTIES IN VISUAL STUDIO ON "Debugging" option.. under the "ASP.NET Debugging" check box

AND in the IIS

YOU MUST GIVE THE CORRECT RIGHTS FOR YOUR VIRTUAL DIRECTORY FOR THE ""ASP.NET" ACOUNT...

SALUDOS
byrru 9/18/2007 7:17 PM

Yes, just remove http://localhost/">http://localhost/ from Trusted Site on Internet Options > Security.. and you can adding the http://localhost/">http://localhost/ on Local intranet..
Work for me.. :D
Joe 9/20/2007 6:29 AM

dont know what happen to me ? after i choose asp.net tab from 2.0 to 1.1 to debug in vs 2003

the default website is stopped and i start it but it show a error : the service didnot respond to the start or control request in a timely fashion . please help me
Raj 9/20/2007 11:27 PM

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…….

I tried all possible fixes but nothing worked. Finally I checked web.config and found that debug option was set to false.

<compilation defaultLanguage="vb" debug="false">

I just changed it to True and problem was fixed.
Mircea Dunka 10/3/2007 5:35 PM

After swtching my project's properties from "use Visual Studio Development Server" to "Use IIS Web Server" (and clicking "Create Virtual Directory" button, I started to receive this error. Obviously, smth went wrong in IIS5.0 config.

What was it?

Load IIS Management Console, go to your web site's properties (I know, everything seems OK, go to "ASP.Net" tab. You will find an "Edit Configuration..." Click on it, and under "Application" tab you should check "Enable Debugging"... :D

I found this after reading this thread until somebody said something about changing ASP.Net version from 2.0 to 1.1. In my case, that is not a good idea, since I DO USE ASP 2.0... But thinking of ASP configuration and remembering I saw smth. somwhere inside those dialog boxes... ead me to this solution.

Hope this helpes. Cheers!
girishlal 10/16/2007 9:34 AM

I had same problem. I think it was due to installing IIS after VS.NET was installed ( I had to re-install IIS for some other reasons)

I did the following

1) In IIS Default Websites properties, select ASP.NET tab. The ASP.NET version was 2.0.50215.0. I changed that to 1.1.4322.0

2) Restarted IIS

Debugging started working afterwards
Blackboard 11/4/2007 7:03 PM

I don't know if this is covered in any of the above posts or not, or even if it is related but i thought of writing it anyway.

If you're getting "Unable to start debugging on the web server. The web server is not configured correctly" then you could do the following to fix it:

> Open IIS > Right click your directory > Properties > In the "Directory" tab click "Configuration". Under the tab "Mappings" look for ".aspx" application extension and see if it has the verb "DEBUG" associated to it. You can select .aspx application extension, click on edit, and then write "DEBUG".

This solved the problem. It's self explanatory why it did so!
Jerry E. Ely 11/11/2007 1:50 PM

About errors running ASP.NET programs locally in DEBUG mode. The problem for me has been the same everytime it happens. It's not a permissions issue, but for some reason certain things cause all local websites to run in the Internet Zone, rather than Local Intranet Zone. I don't know how to change that and putting http://localhost in trusted sites doesn't help.
I have to go to IE, tools, internet options, security tab, click custom level for internent zone and at the very bottom if you scroll down, I'll find i'm set to allow 'Automatic login only in local intranet zone'. I change it to 'Automatic login with current username and password' and all of my ASP.NET websites work in debug mode just fine. <br>
The problem now is, how do I control if a site runs in internet or local intranet zone. I can't seem to find this info which seems like it would be common. I've never thought about it and am still a student of .NET and windows programming to a large degree.

Hope this helps someone.
Thanks,
Jerry
Jerry Ely 11/11/2007 2:06 PM

Steve,
I just posted but noticed Steve's post afterward.....about thinking installing SSRS had something to do with it. I KNOW that is what caused it for me. I'm running XPSP2, IIS 5.1, SQL Server 2005 Express Advanced with Reporting services. After I configured the reporting services, is definately when my ASP.NET debugging stopped working and giving that error.
My fix was as stated, for now. Set security for Internet Zone in IE 7 to Automatic login for current username and password. Obviously this will work since it was set to Automatic login only in local intranet zone and all of my ASP.NET websites started running in internet zone.

Anyone know how to change zone your website runs under? I guess I already asked that, sorry. I feel stupid for not knowing this. It is the answer for the problem for me (a BETTER answer that is than to change security in the internet zone which i did not want to do, but it works to get debugging working again for now)

Jerry
Avinash 11/12/2007 11:39 PM

reset permission for iisprocess in www$
software development outsourcing 11/19/2007 4:29 AM

i also got this type of problem
plz use it

<compilation defaultLanguage="vb" debug="false">

i think u can understand it
nick 11/22/2007 2:57 AM

I also had this problem but it was quickly solved by deleting the project name from the \Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\<project name> folder. lucky me
Martin Eyles 11/22/2007 7:47 AM

Setting the trusted sites security to low fixed it! Thanks to all those who gave comments that pointed me in the right direction
Pooja 11/28/2007 12:18 AM

Hi All,

I have tried all the solution i found here on this site..still I am having same problem..plz tell me how to resolve the this problem ??

My Problem is: Whenever i Run my project them i got this problem:
Unable to Start Debugging on the Web Server. U do not have privileges to debug the web server.

Thanks
Pooja
mangal.pooja@gmail.com
Scott 12/2/2007 9:35 AM

This will probably wind up getting posted twice or not at all. I just posted and it didnt show so.

Make sure Enable Debugging is checked. I just installed 2003 to work on an old project and I could not debug.

I went into IIS Web Server properties and cliced the ASP.Net tab. Selected 1.1 and clicked "Edit Configuration" On the Applicaiton tab is a little check box that says "Enable Debugging." Checked that box and it works now.

Happy programming.
minik peri 12/2/2007 2:23 PM

check the IIS configuration for your application, check the asp.net tap the version you r using, and check the authentication on the directory security tap; it must be integrated windows authentication...

hope this help
JosephBurton 12/3/2007 12:47 PM

I'm running a XP Pro machine and what did it for me was choosing the correct ASP Version.

There was two version installed. ASP.Net Version 1.1 and 2.0.
I am using VS 2003 and the version was set to 2.0.
Once I changed the ASP.Net version to 1.1 it worked.

I went to IIS and found my project. I right clicked and went to properties; went to the ASP.Net tab and in the dropdown list chose the correct version, applied it and the error went away.
Barry 12/6/2007 10:16 AM

OK I tried everything - what finally worked for me was to put http://localhost in">http://localhost in the local internet sites (not Trusted sites) I believe that it is stated in some of the dialog on this site, but I thought I would make it explicit! (I had been working on this problem for 4 hrs)

In Explorer
Tools / Internet Options / Security / Locol Intranet / sites (button) / Advanced (button) / Enter http://localhost

This moved http://localhost from the Trusted Sites to the Local Intranet and now the debugger works!
Victor 12/12/2007 7:26 PM

Can anyone help me out on this issue "Unable to Start Debugging on the Web Server"

Victor
SRIKANTH REDDY 12/14/2007 9:28 AM

Change the version of ASP in your IIS for the project.
It will work. It did for me.
Sreekanth S 12/14/2007 10:12 PM

This is for those who cannot resolve issue after trying all the above points.

Here we go,

Create a virtual directory for your site.

Now open your site as FileSystem (Not from IIS).

Right the Solution to get Property Page,

Select start options:

Set Start URL to the virtual directory URL on that we have created for the site.

In the Server section, select Use custom server option, set the Base URL same as that of the Start URL.

Click OK, and Build your site.

It worked for me. Thanks Vinod Sir for this work-around.
Upendra 12/18/2007 10:51 AM

My problem was silly, the 1.1 site was actually configured to use 2.0 framework.

Dont know how it got changed. But changing this back to 1.1 worked for me:-)
Fareed 1/1/2008 7:07 AM

"HTTP Keep Alives" did it for me.
Tercüme 1/7/2008 8:53 AM

Setting the trusted sites security to low fixed it! Thanks to all those who gave comments that pointed me in the right direction..
Sonali 1/9/2008 11:50 PM

Adding http://localhost to trusted sites works!
George 1/24/2008 6:34 AM

Hi,

for me works the checkbox in visual studio settings (having vs 2005 on an windows xp machin):

Debugging\activate SQL Debugging !!!

Don't know whay ???

Bull Sh.. MS IIS ASP things !!
Bugaboo 2/1/2008 5:54 AM

changing the version back from 2.* to 1.1* worked for me. Thanks
Cristian 2/14/2008 7:55 AM

changing the version back from 2.* to 1.1* worked for me too
But I had to run

C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i

Because 1.1 option was lost after instalation of VS2005 on the same machine. This thread is a superb team work, thanks again
Hari 2/14/2008 10:11 PM

C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i

Run this.
you need to register your asp 2.0 again if you install IIS after installing .net framework
cory 2/24/2008 5:32 PM

its better to switch to apache server less debugging problems there
Simeon 2/26/2008 9:43 PM

Reverting from 2.0.50215.0 to 1.1.4322.0 solved my problem real quick.
However i would like the debug to work in 2.0.50215.0.

If any of you find how to make it work since i've tried most of the recommendations but with result of non-effect.
çeviri 2/27/2008 12:56 PM

thank you very much, i was looking for this..
http://www.oynabitir.com 2/27/2008 2:11 PM

It could be that you are attempting to debug a v1.1.4322 site whose virtual directory or parent website is set to run under .NET 2 - thanks for the lack of explanatroy error message ms!
Kral oyunlar.
Andrea 3/5/2008 11:01 PM

My application was lacking the web.config file. I added one and it was all set!
Bijay Maurya 3/9/2008 11:25 PM

Hi All,

I have tried all the solution i found here on this site..still I am having same problem..plz tell me how to resolve the this problem ??
My Problem is: Whenever i Run my project them i got this problem:
Unable to Start Debugging on the Web Server.

Thanks,
Bijay
Bijay Maurya 3/9/2008 11:31 PM

I have Open my Internet Information Services manager and from the [our machine]/Web Sites/ Default Web Site node i have select the virtual folder which stores our project. i have Right Click and select Properties to select the ASP.NET tab page but ASP.NET tab is not present here.

plz tell me how i can resolve this problem?

Thanks,
Bijay
bijay.maurya@gmail.com
Ashwin Kavale 3/10/2008 10:12 PM

Everytime i run asp.net file by pressing F5 i get the folloeing error:
Error trying to run the project.Unable to start debugging on the server.You do not have permissions to debug the server.
Please give me detail step to resolve this problem..
samir 4/4/2008 12:34 PM

YOU MUST UNCHECK THE "ASP Debugging" IN THE PROJECT PROPERTIES IN VISUAL STUDIO ON "Debugging" option.. under the "ASP.NET Debugging" check box --- THIS DID IT FOR ME
samir 4/4/2008 12:39 PM

And thank u MEXICAN for that solution
Karlos Kolley 4/7/2008 7:32 AM

When you install VS 2005 it changes your IIS settings. For to be able to debug multiple .NET versions do the following:

C:\WINDOWS\MICROSOFT.NET\FRAMEWORK\V2.0.50727\aspnet_isapi.dll -- DEBUG for NET 2.0

C:\WINDOWS\MICROSOFT.NET\FRAMEWORK\Vv1.1.4322\aspnet_isapi.dll -- DEBUG for NET 1.1

How to change:

1. Go to properties of Default Web Site.
2. Go to Home Directory TAB
3. Click Configuration
4. Select .aspx from the file list
5. Click Edit
6. On executable change the path to connect to cpecific aspnet_isapi.dll from .NET 1.1 or NET 2.0

C:\WINDOWS\MICROSOFT.NET\FRAMEWORK\V2.0.50727\aspnet_isapi.dll -- DEBUG for NET 2.0

C:\WINDOWS\MICROSOFT.NET\FRAMEWORK\Vv1.1.4322\aspnet_isapi.dll -- DEBUG for NET 1.1

Do it not copying that path but usibg Browse button. Changing back and forth gives you ability to debug either .NET 1.1 or 2.0 apps but not both
Charles Irwin 4/14/2008 12:08 PM

Nothing was working so I called Microsoft. They had me register asp.net 2.0 and it worked.

You do this by popping up the Visual Studio 2005 Command Prompt and entering the following:

aspnet_regiis -i

I would definitely do this before rolling back to 1.1.
Nads 5/8/2008 12:30 AM

1. Open up IIS dialog window.
2. Expand Websites folder
3. Expand Default Websites
4. Find Your Solution and right click on it.
5. Select Properties.
6. Select ASP.NET Tab
7. Select ASP.NET Version. (If you using .NET2.0 and .Net1.0 you will have to manually set this property to the version the websites is compiled in.)
elmedesa 5/16/2008 7:56 AM

Gracias por el articulo.
bilard 5/19/2008 6:59 AM

Great and excellent article it’s realy helpful. Thanks again.
Bubba 5/27/2008 11:34 AM

Yahoo! I'm up and running at last!

Here is what I did to get running:

VS 2003, IIS 5.1, XP, IE 7

1) added http://locahost to trusted sites

2) lowered trusted sites security level zone to low
Andrea Scurci 5/28/2008 5:27 AM

check to have

<compilation debug="true">
cj 5/31/2008 9:36 PM

thank you. installed a new machine and forgot to click integration with Window authentication.
Sibi 6/3/2008 10:42 PM

Hi Igor Jerosimic,

Your solution helped me
eva 6/14/2008 10:13 AM

In IIS on the local machine, I brought up the web site properties. Under the tab labeled ASP.NET, I was using 2.0.5072. When I reverted back to version 1.1.422, the debug problems went away.

Thanks this worked for me. Am using Windows 2003 server.
Brian Leszczynski 6/20/2008 11:09 AM

Thanks to Igor! His tip solved the problem for me.
Gnanasambandham Anbazhagan .. 6/24/2008 8:43 AM

You may encounter this situation if you recently change your windows password. you can try the following steps and you can overcome this problem.

1. ) If you are using .net 2003 Search for your machine.config file in the below folders

C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\CONFIG
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\CONFIG

2.) choose the machine.config file under C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\CONFIG. Better have a backup before modifying.

3.) Search for your user name for example. if your user name is "Gnanasambandham" and next to that u can see your old windows password.
change it to recently changed windows password.

<processModel enable="true" timeout="Infinite" idleTimeout="Infinite" shutdownTimeout="0:00:05" requestLimit="Infinite" requestQueueLimit="5000"
restartQueueLimit="10" memoryLimit="60" webGarden="false" cpuMask="0xffffffff" userName="companyname\Gnanasambandham" password="password"
logLevel="Errors" clientConnectedCheck="0:00:05" comAuthenticationLevel="Connect"
comImpersonationLevel="Impersonate" responseDeadlockInterval="00:03:00" maxWorkerThreads="20" maxIoThreads="20"/>

4.) Restart your machine. Load your .net project and run. It will work.
DNN 7/28/2008 4:42 PM

I've got this error but could not fix it:
"Error while trying to run project: Unable to start debugging on the web server. Could not start ASP.NET or ATL Server debugging.Verify that ASP.NET or ATL Server is correctly installed on the server."

Project worked fine on XP and IIS 6. Once moved to new Vista box with IIS 7, it kept throwing the error above when I open the project.

Please help. Thanks a lot.
pab 7/30/2008 6:15 AM

Hi,

I have a hint for those who are still trying to resolve the issue. After trying all (I believe) solutions described on this site I found a small checkbox that must be checked to allow debuging on IIS. Just follow my instructions below:

1) Run Internet Information Services
2) Right click and select 'Properties' on the web site node you want to debug.
3) Go to the 'ASP' tab and push the 'Edit configuration' button (Remember! As it is written somwhere on this page, you have to be sure that correct version of ASP.net is selected!)
4) Go to 'Application' tab and ...
5) Check the 'Enable debugging' checkbox

It has been working with my web project and I hope someone will find it usefull.

Regards,
Pawel
ASP Net 2.0 Migration 9/4/2008 12:15 AM

Nice point wise explanation... thanks for the solution...
Herrmaan 9/11/2008 7:18 AM

Super , fixed it !!
Lyners 9/11/2008 11:14 AM

Same problem as everyone, nothing is fixing it. I have the debug problem. I had a desktop that has been working for about 2 years with VS 2003 and VS 2005 on it. I left work for 3 months, came back and I have a new PC. I had to install IIS 5.1, .NET Framework and VS 2005 (We no longer have the need for 2003). I went into Visual Source Safe to try and load up my web applications. That seemed cumbersome and was not working correctly, so I copied everything under the inetpub directory to the new machines inetpub directory, and I copied my projects to the My projects on the new machine. I can load the application into VS 2005, but I cannot debug or start without debugging. I am able to create a new project, and debug.

What am I missing?

Thank you.
Lyners 9/12/2008 8:33 AM

I got the debugger working. I went into properties for the project, selected the Web tab, then selected Use Visual Studio Development Server, Ato assign Port. That worked. So that tells me my IIS on my desktop is not setup correctly, buit at least I am able to debug now.

I forgot to mention in my last post, my configuration:

Windows XP Pro
VS 2005 Pro

Hope this helps someone else.
Edwin 9/19/2008 12:15 PM

Error while trying to run project: Unable to start debugging on the web server. You do not have permissions to debug the server.

Verify you are member of the 'Debugger Users' group on the server...............

Bueno, despues de andar buscando en internet, el "bendito" error, leer varios articulos, leer varios foros de personas que tenian este mismo problema, consultar el sito de soporte de microsoft, etc. nada de esto me funciono, toda la consfiguración del IIS, de la serguridad de usuarios de windows (2003) , todo lo tenia segun las recomendaciones expuesta en todos estos sitios de información antes mencionados.

Para no hacerles muy larga la historia de lo que pase, la solución la encontre yo mismo ahi probando y algunas cosas. En uno de estos sitios lei que el servidor debe estar registrado en una zona de seguridad en los sitios de confianza que se registran en el Internet Explorer, bajo el siguiente URL: http://localhost, esto hace que todos los proyectos desarrollados localmente al ejecutarse le indiquen al explorer que proviene de un lugar seguro y se pueda mostrar sin problemas.

Bueno esto yo ya lo habia hecho y asi estaba, pero buscandole por ahi (y esto es lo que no encontre en ningun lado en internet), estube probando con las opciones de seguridad del Explorador y asi fue como encontre la solución.

Solución.

OJO: esta solución aplica para IE version 7.0 que es donde me estaba dando el problema.

En opciones de internet, en el Internet Explorer 7.0. en el tab de "Seguridad", en la zona de "Intranet Local", y luego presiondo el botón de Sitios, ahi es por defecto (o por lo menos asi lo tenia yo) la opción de "Detectar redes intranet de forma automatica" esta chequeado y hay otras tres opciones que dependen de esta que estan chequeadas, pero deshabilitadas. Lo unico que hice yo, fue deschequear la opcion mencionada y dejar chequeada las otras tres opciones.

Cuando compile el proyecto, ya no me mostro el error y pude "debugear" la aplicación sin problemas.

Espero que esta información les siva de algo, porque la verdad en internet no encontre ningun lado mencionando esta solución en especifico para IE 7.0.

Saludos a todos,
Alex 9/25/2008 1:25 PM

I tried several things to make it work and the final fix was, after adding http://localhost to the Trusted Sites list, I had to set that zone's security level from Medium to Low.

Thanks to Mike Rustici for suggesting that!
Stephen 10/1/2008 7:54 AM

Make sure that you have the correct version of ASP.NET selected in IIS. I am using VS 2003 and this was the source of my problem.

Regards
Smooth Coder 10/3/2008 8:51 AM

Tried all three, no help to me.
Amit 11/5/2008 4:15 PM

And also make sure to selected that appropriate ASP.NET version.

-Amit
Rick Mossguy 11/10/2008 5:31 PM

I have been doing SharePoint development and added a workflow website and could not debug because of this error. I'm on IIS 6.0 and using VS 2008 on Windows Server 2003 R2 with Service Pack 2. It took editing the registry to disable the loopback check as described at http://support.microsoft.com/?kbid=896861 to clear up the problem for me.
Estetik 11/19/2008 8:26 PM

Relativamente alla domanda, di come ci si senta quando si è un blogger, le mie sensazioni su questo sono ambigue. Io sono certa che c’è qualcuno che pensa che io non sia una vera blogger perché raramente pubblico più di un testo alla settimana e non mi avvolgo giornalmente nelle discussioni con i commentatori del mio blog. Ritengo che la risposta a queste persone sarebbe una domanda:’Voi non avete una vita/ occupazione/ qualcos’altro da fare?’ E finora non esistono regole per i blogger, né un loro sindacato.
Ryan Farley 11/19/2008 9:25 PM

@Estetik, grazie per il commento. Buono detto.
-Ryan
thedudewhotriedeverything 12/1/2008 3:40 PM

OK TRIED EVERY single comment here until i got to Barry's comment and it worked !!! gosh .... three days into this.
My problem is : winxp sp2 .net 1 and 1.1 and 2 and 3 and 3.5 , iis5 , everything running local, trying to run a .net 2003 project got the same lame message everybody got and after trying most obvious the one that worked for me was to add http://localhost to the LOCAL SITES (INTRANET) not the trusted sites. thanks dude
Ali 12/15/2008 11:54 PM

Nice solution for debugging error i got the solution here from comments. its nice and helpful stuff.
Regards.
Samantha 1/21/2009 6:19 AM

Changing the .net version on IIS worked for me! Thanks very much!!!!
Alain 1/23/2009 12:31 AM

One more that was not mentioned in this page, if you recently installed urlscan or maybe .net framework 3.5 it will disable debugging by default.

After long resource i tracked the url scan log files and found:
2009-01-23 07:17:36 127.0.0.1 1 DEBUG myurl.aspx Rejected verb+not+allowed HTTP+method - -

So i looked in the UrlScan.ini file found that i should add
DEBUG under [AllowVerbs] where UseAllowVerbs is set to 1

this setting allowed the debug verb to pass through the url scan.

UrlScan.ini is found in "\System Root\System32\Inetsrv\Urlscan\"

you shoud search for allowvers then it will be like this:

[AllowVerbs]

GET
HEAD
POST
DEBUG

Hope this will helps you.

Alain
chlin431 1/26/2009 9:14 AM

It works for me. THANK YOU.
Guy 2/17/2009 1:41 PM

I have been stuck with this problem for about 1 week, i am not able to debug a asp.net application in VS. I can start it using Start without debugging.

But when i click on start I get this error :
Unable to start debugging on the web server. The server threw an exception.

and in my Debug window i have this message:

Auto-attach to process aspnet_wp.exe on machine xxxxx failed. Error code 0x80010105 (The server threw an exception.)

Please Help...

Thanks in advance
Alex 2/18/2009 7:13 AM

In the project properties, set the Server to Use Visual Studio Development Server.

Boom.
vanslly 3/16/2009 12:52 PM

As per aforementioned suggestion, I resolved this issue by moving http://localhost from trusted sites to intranet sites in IE!
Rob 3/18/2009 10:49 AM

I don't know if this helps you or not, but I was having the same issue, and the error was giving me the additional message that webserver wasn't found. I'm using VS2008 with Silverlight.

It turns out that I was playing with deployment settings the night before, and forgot that I had changed the "Server" settings just before I finished up for the day. To make sure this is not the cause of your problem Right Click on the web application folder (MyApplication.Web) in the "Solution Explorer" tab, select "Properties" then in the MyApplication.Web properties window select the "Web" tab on the far left. Select "Use Visual Studio Development Server" and then specify whatever port you feel like using (example: 5000).
divine 3/23/2009 11:08 AM

thanks this is helpful :-)
lazer epilasyon 5/12/2009 8:44 AM

nice page! thanks for sharing
david 6/7/2009 1:31 PM

Rob (3/18/2009 10:49) you solved my issue with debuging. Many thanks for your comment.
hong 6/17/2009 1:21 PM

Great. I needed to work on a very old Visual studio 2003 asp.net 1.1 application and got this error message. Http Keepalive worked for me. I have windows xp. The check box is found on IIS Manager, "default web site" properties, connections section.
Thanks.
tawani 6/17/2009 4:14 PM

Thanks man!
big time thanks...
CHRIS 6/25/2009 11:44 PM

Please make sure the version of asp.net which you choose is correct.
if it's VS2003,you shouldn't choose .net v2.0 in IIS config
Prerak V. SHah 7/9/2009 1:46 PM

It worked for me... Thanks a lot.
ckluczyk 7/14/2009 5:08 AM

register all the dll files in C:\Program Files\Common Files\Microsoft Shared\VS7DEBUG with regsvr32 - especially msdbg#.dll... It worked for me.
STinUT 7/15/2009 6:44 AM

I went through most all of the above without luck, then found this on another site that fixed my problem so figured I'd post here in hopes of helping others.

In IIS, check the local path to the home directory and make sure there is not a trailing "\" at the end of the path.

I changed my local path for the root website from "c:\dev\" to "c:\dev" and it fixed my problem with the "Verify that ASP.Net or ATL is correctly installed" error.
Mark Schultheiss 7/22/2009 11:42 AM

I inherited a machine with unknown past, multiple users etc.
I had to unregister the v1.1 AND the 2.0, then re-register the 2.0 for this to work for me, (did not have the .aspx etc) under the configuration until I did this.
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322>aspnet_regiis.exe -u

THEN
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis.exe -u
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis.exe -i

to diagnose: check IIS, right click vitual web name, then choose Properties
Then click the Virtual Directory tab Configuration button - did not have the .aspx extension listed until I did the above.

Executing JUST the 2.0 register did NOT work as it did not add the .aspx extension (or several others).
Hopefully someone else finds this useful.
Jon 7/29/2009 8:58 AM

I'm getting this error on my and a developer's machine. We're now both out of action because we can't debug. I could do with a definitive checklist of things that might be causing the error & possible solutions...can anyone help?
I'm tired of tralling through everybody elses trial & error!
Surendar 9/10/2009 11:10 PM

Hi all

check out whtether your aspnet account is locked in your developer machine. If so then unlock the aspnet account and make a iisrest and try
Roger Farley 10/5/2009 7:56 AM

I know this post is a little old, but ran into it today and I wanted to add my own fix to the list.

I have .NET 1.1, 2.0.... 3.5 installed. The site is 1.1 and IIS had defaulted the .NET version to 2.0. Once I fixed that, it worked.

Great last name Ryan!
Web developers 10/23/2009 7:49 AM

Hey,
There are some many annoying problems that debugging uncovers and it drives me nuts, thanks for your resoultion,
Keep up the good work.
noblesilence 10/26/2009 11:58 PM

Thank you so much, Marthin. >> Added http://localhost to "Local Intranet" in IE7 and problem was solved.
Larry Aultman 10/28/2009 7:31 AM

Had this problem (Win7/IIS7) with very simple project with an .asmx web service and a single page test website to consume the service.

Tried all the suggestions at top didn't work for me. My solution... don't know why it works but it does.

1 Removed the web service from the "Default site" and made it a regular site in IIS. I gave it a host name of service1.local
2 Added a record to my "hosts" file in C:\Windows\System32\drivers\etc to resolve my host name above. Looks like this:
127.0.0.1 service1.local
3 Restarted IIS to force read of hosts file.
4 Removed the old web service project from my VS solution.
5 Added the now relocated web service to my VS solution.
6 Deleted references to old web service from my test application.
7 Added a web service reference to the new relocated web service.

Now it works.
So the simple answer seems to be the web service needs to be run in IIS as its on instance rather than as an application under the DefaultSite.

Good luck
Larry
L.lo 12/8/2009 3:30 PM

I had this problem, and I had not realised that IIS was stoped :S

Thanks for all :)
leyenda 12/10/2009 1:14 PM

hello Alain, man you safe me i tried everything and the solution are this tk so much

Para los colegas que hablan el idioma el problema era:
S.O. WS2003
VS 2003
ASP.NET 1.14xxxx

A la hora de correr el visual studio y debuggear una aplicacion mandaba un error que decia: "error while trying to run project unable to start debugging on the web server could not start asp .net or ATL server debuggin"

Bien intente lo siguiente segun lo investigado en muchos foros y soluciones de microsoft:
* Agregar a los sitios de seguridad en IE el http:\\localhost
* Cambiar los permisos de seguridad en el IE Automatic logon whit current user name and password
* Me asegure que estubiera bien seleccionada la version del ASP.NET a la 1.14 en el proyecto dentro del IIS
* Me asegure que en las propiedades del directorio en el iis en la pestaña de directorio->Application settings-> boton de configuracion en la pestaña de debugging estubieran marcadas las dos checkboxs ahi mismo en la pestaña mappings en la extension .aspx que estubiera haciendo referencia a la version correcta del ASP.NET y que aparte de eso los verbos incluyeran Debuger.
* Me asegure que la carpeta de los temporales de la version del ASP.NET tubiera permisos FULL.
Sin embargo nada de esto solucionaba mi problema hasta cambiar el archivo UrlScan.ini que se encuentra en \System Root\System32\Inetsrv\Urlscan\ en la parte de [AllowVerbs] se tenia que verificar que estubieran estos verbos:
*GET
*HEAD
*POST
*DEBUG

Bien cuando yo abri este archivo y ubique [AllowVerbs] no tenia el ultimo verbo DEBUG asi que lo escribi y guarde el archivo y se soluciono el problema.

La causa imagino es la que menciona Alain es producto de instalar la version de ASP.NET 3.5

Saludos y espero sirva esta informacion

Nota:Por cierto inverti casi una semana encontrando esta solucion pero que bien se siente solucionarlo al fin
rm 1/5/2010 6:37 AM

THIS WORKED FOR ME.
Yes, just remove http://localhost/">http://localhost/ from Trusted Site on Internet Options > Security.. and you can adding the http://localhost/">http://localhost/ on Local intranet..
Work for me.. :D
Russ Marano 1/22/2010 2:07 PM

for me I'm using many different web.config's...so renamed a saved one to web.config like always and suddenly the error started showing up. After much thrashing about I saw the problem, I had renamed the file to wweb.config......
emaurojas125 3/17/2010 9:58 AM

Another thing that yo can try is change the security options in your internet explorer.

In the IE Menú: Tools/Internet Options/Security TAB/Custom Level. In the user autentication option, change it to "log on intranet zone" (or something like that, i have the spanish version)

This works for me.
Pankaj Tahiliani 3/21/2010 9:52 PM

HTTP Keep Alives (solved my problem) - Million Thanks
MT 3/22/2010 5:46 AM

Excellent page. Saved me more than once. Thanks
arbingersys 4/29/2010 1:40 PM

Excellent! (but stupid) -- putting 'http://localhost' in Trusted Sites fixed it for me.
siva 6/3/2010 4:30 AM

unable to start debugging on d web server.an authentication error occured while communicating with the web server plz see help for assistance
i am getting this error when i press f5 in asp.net .plz provide me a good solution.
withregards
siva
BeNNeS 6/14/2010 7:32 AM

Tried a lot of solution but finally it was in Internet Service Management in the Default Website Property.

Yes you have to put it at "All Unassigned" like it was said before but that didnt do the trick for me i had to click on the advanced button and remove the value of the "Host header value"

after that everything worked like a charm!

Ben
Raviraj 6/22/2010 12:44 AM

follow below steps, it should work (for VS 2005).
1. Right click on your project
2. Select properties
3. Go to "Web" tab
4. Select radio button "use visual studio development server" under server tab.
5. Select debugger "ASP.NET" under debuggers tab
6. save changes
7. debug your application.

Thanks,
Raviraj
Armando Daniel 6/29/2010 10:36 AM

Hi Ryan, BlackTigerX

Your link helped me out a lot! (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vstechart/html/vsdebug.asp)

I had this issue: "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." and executing command "aspnet_regiis.exe –i" prevented me from going crazy.

Thanks guys, your blog is pretty interesting
8/20/2011 4:31 PM

Unable to Start Debugging on the Web Server | Stage
8/6/2012 3:09 AM

Unable to Start Debugging on the Web Server | My Blog
6/25/2013 7:18 AM

error while trying to run C# project un able to start the program with debug but works fine without debug | Q Sites
8/2/2015 7:23 PM

unable to start debugging on the web server windows 7 visual studio 2010 | Webserver Tutorial
5/21/2016 3:03 AM

The Web Server Debuggin Failed Because Integrated Windows | Marioosava
12/8/2016 1:10 PM

Computers Programming Internet Asp Aspnet Web Hosting S | Great at WebHosting
12/14/2016 10:36 PM

2016 Annual Visitor Survey
8/28/2022 5:04 AM

?????????????? ?????????????? ?????????????? ?????????? ???????????? ?? ?????????????????? ???????????????????? ????????: ???????????????????????? ????????????????????????, ?????? 26, ???????????? 12 Emhj ???????????????????? 26 2020 - Showbox