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