Re: Unable to start debugging on the webserver
- From: bruce barker <nospam@xxxxxxxxxx>
- Date: Wed, 31 Jan 2007 17:56:55 -0800
the problem is caused by installing ie 7.0
try adding localhost to the trusted sites, or upgrade to vista (the only enviroment i use ie 7.0).
-- bruce (sqlwork.com)
1388-2/HB wrote:
This is happening on a WinXP Pro SP2 machine with Visual Studio 2005 & local IIS as the debugger. Everything was working fine this morning (and had been working for weeks/months prior). After a trip to windows update (where I installed IE 7, .NET 3.0, VS 2005 SP1 and misc updates for XP such as timezone changes & a new sound driver) I can no longer debug my web app on IIS. I now receive this message:.
"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."
I can visit the website without debugging directly at http://localhost/ in IE 7 (or FireFox 2.0) and the website functions 100% as expected, no errors. I have not changed any of the authentication methods for the website in IIS. Windows Authentication is enabled. IIS shows framework version 2.0 on the ASP.NET property tab of the website (as it always did) and the website code itself is still referencing objects from the 2.0 framework (no change). debug="true" in web.config (no change), VS 2005 still references a custom webserver url of http://localhost/ (no change). I cannot figure out what has changed but obviously something very critical has in fact changed.
It was not getting this error message this morning before the updates. Any ideas?
- Prev by Date: Re: Request for the permission of type 'System.Data.SqlClient.SqlClientPermission [.....]' failed
- Next by Date: Re: best way to keep persistence of a dataset?
- Previous by thread: Re: Client side changes not reflected in page
- Next by thread: Re: best way to keep persistence of a dataset?
- Index(es):
Relevant Pages
|
