The Web Server Could Not Find the Requested Resource

Question

I have a .NET 3.5 Web application on VS 2008 SP1 running on Vista Ultimate 32 SP1. I created an Application under the Default Web Site. So the url to the app is "http://localhost/mysite". The application folder is pointing to the solution folder and it is outside the iisroot folder. Anonymous and Integrated Auth (Windows) is enabled in IIS7 for this web application "mysite".

I gave full permissions to "Network Service" user to the application folder (which is outside of iisroot).

When I hit F5 to star debugging, I get the "Unable to start debugging on the web server. The web server could not find the requested resource." error.

Does anyone have any ideas why?

thanks

Answer 1

That should not be an issue - what do you have as your startup page? Also, in the 'Start Options' for the web (under properties page), make sure that you have 'Start URL' selected and put in the Url you mentioned above.

The error you are having should not be permission specific, so i would look elsewhere - also check if you can hit the url successfully before debugging (manual put the url in your browser) "http://localhost/mysite".

Answer 2

I can hit the URL "http://localhost/mysite" without a problem. That web application is set up to be the start up project and Default.aspx is the start up page.

There is an .asmx service in the prject as well. The Default.aspx is making use of that asmx service. The AutoCompleteExtender (From the AJAX Control Toolkit) is using this asmx service.

Everything works by the way. The issue is the debugging... I suspect the asmx service is causing this but i don't know. This is driving me nuts...

Answer 3

Have you tried:

• Turn of UAT
• Add the user the website is running under (and/or yourself) to the Debuggers or Administrators group (temporarily)
• Turn on IIS logging

Answer 4

Just to make sure, have you set up Debug=true in your web.config. Generally when you are using VS's inbuilt web server, then it is able to detect that you are trying to debug but debug flag is off and it warns you. But in your case you have setup IIS and VS might not be able to do this check.

Another point is you are running on Vista. In vista even if you are the admin of system, Vista does not treat you as Admin. Your security tokens are created as of normal user. In order to do the debugging IIS hosted website (note: when using inbuilt web server, VS 2008 manages the debugging), run the VS 2008 as administrator. That could solve the issue.

Answer 5

@Pradeep: I am running Visual Studio as Admin. In fact, it would not run a web application under IIS of you are not running VS in admin user. And yes debug=true in the web.config file.

@Robert: What do you mean by UAT? Do you mean UAC? If so, it has nothing to do with this issue. IIS logging is on by default.

Answer 6

I fired up TcpView (Sysinternals) to see what app is actually running and keeping an handle on that port and I found out there is no app listening on that port. This is really wierd... Any creative ideas?

Answer 7

TcpView in Vista crashes when "show unconnected endpoints" to show all ports so I used "netstat /a" to see what is listening and again; that port (42880) is not used by any runnig app.

I am completely at a loss...

Any ideas are welcome...

Answer 8

I am having the same problem, but am able to debug if I go via the Tools -> Attach to Process menu then select the aspnet_wp process.

Answer 9

Just managed to fix this on my dev machine: I've got UrlScan installed and had to add DEBUG to the list of AllowVerbs. Hopefully this might give you something else to go on?

Answer 10

I had same problem and solved it. You can try following: navigate to the root folder of your web application and find file that has ".csproj.user" extension ad delete it. Then hit F5. Otherwise hit CTRL+ALT+P and attach to w3wc.exe process. Hope it helps.

Answer 11

Installing Urlscan and changing the urlscan.ini with these changes solved the problem.

In ALLOWEXTENSIONS Section add .aspx and in ALLOWVERBS Section add DEBUG.

Don't forget to restart IIS.

Answer 12

I had the same problem with XP sp3 and I have been struggling for days. Adding .aspx and DEBUB to urlscan.ini solved the problem.

Thanks guys.

Answer 13

I currently have the same error as sahina but am running Windows Server 2003.

I received this error after converting my web application from 2.0 to 3.5.

I installed urlscan and it returned the different error that the webserver is locked down and does not allow debugging.

So I added DEBUG and .aspx to the urlscan.ini file but this problem is happening.

Does anyone have any advice?

Thanks

Chris

Answer 14

In my case, I had to fix Web Service Extentions

Adminitrative Tools -> Manage my server -> IIS - > Web Service Extensions

ASP.NET 2.0 was prohibited somehow, fixed that and it started working.

Cheers!

Vishal Seth