Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

PRB: "The Project Is Not Configured to Be Debugged" Error Message When You Debug ASP.NET Applications

View products that this article applies to.


When you debug an ASP.NET application in Visual Studio .NET, you may receive the following error message:
Error while trying to run project: Unable to start debugging on the web server. The project is not configured to be debugged

For ASP.NET projects, verify that you have a valid project file called 'Web.config' for the URL specified and 'debug' is set to 'true' in that file.
For ATL Server projects, verify that the 'DEBUG' verb is associated with your ISAPI extension.
Would you like to disable future attempts to debug ASP.NET pages for this project?

↑ Back to the top


This error can occur primarily because:
  • The ASP.NET Application does not have a Web.Config file.
  • The Execute Permissions property for the current project folder in Internet Services Manager is set to None.

↑ Back to the top


To resolve this problem, use one of the following methods, depending on your circumstances:
  • If your project does not have a Web.config file, add a Web.config file to the directory that contains the ASP.NET application. If you are working in Visual Studio .NET, right-click the project in Project Explorer, click Add New Item, and then click Web Configuration File.
  • If your project already has a Web.config file, and if the debug attribute is set to true in the <compilation> section of the Web.config file, follow these steps to set the Execute Permissions property for the project folder:
    1. Start Internet Services Manager, and then click the project that you are trying to debug.
    2. Right-click the project, and then click Properties.
    3. Click the Directory tab.
    4. If None is selected in the Execute Permissions list, click Scripts only, and then click Apply.

↑ Back to the top

Keywords: kbconfig, kbdebug, kberrmsg, kbprb, kbweb, KB306156

↑ Back to the top

Article Info
Article ID : 306156
Revision : 7
Created on : 1/17/2004
Published on : 1/17/2004
Exists online : False
Views : 408