This problem can occur if there is some error in the web.config file. To resolve this check for the well-formedness of
For more details refer PRB: "Unable to Start Debugging" Error Message When You Send Debug HTTP Request
There is a possibility that there is no web.config file for the project or there is no Execute permission for the project.
If you already have a web.config file, double check it's well-formedness.
If the web.config file is missing, add one to the directory that contains the ASP.NET application. You can copy one
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
3.3 When I Debug ASP.NET Applications I get error message "Access Is Denied. Check the DCOM Configuration Settings for the Machine Debug Manager"?
3. Click Groups, and then double-click Debugger Users.
4. In the Debugger Users Properties dialog box, click Add.
5. In the Select Users or Groups dialog box, select the appropriate user, and then click OK.
6. Click OK to exit the Debugger Users Properties dialog box.
7. Close the Computer Management explorer.
3.4 On Trying to Debug an application, by the F5 key I get the error: "Error
while trying to run project: Unable to start debugging on the web server.
This issue occurs if the account that is used to run the ASP.NET Worker process (by default, the ASPNET user
account) is not assigned the "Impersonate a client after authentication" user right in the "Local Security Policy"
settings. This issue may occur when you install Microsoft Visual Studio .NET after you install Windows 2000 Service
Pack 4 (SP4) on the computer. In this situation, the ASPNET account is not assigned the "Impersonate a client after
authentication" user right in the "Local Security Policy" settings.To resolve it, please use the method at: To work
around the problem, manually assign Impersonate a client after authentication to the IWAM account. To do so,
follow these steps:
2. Click Security Settings.
3. Click Local Policies, and then click User Rights Assignment.
4. In the right pane, double-click Impersonate a client after authentication.
5. In the Security Policy Setting window, click Define these policy settings.
6. Click Add, and then click Browse.
7. In the Select Users or Groups window, select the IWAM account name, click Add, and then click OK.
8. Click OK, and then click OK again.
9. To enforce an update of computer policy, type the following command: secedit /refreshpolicy
Your ASP.NET project is not setup for debugging.
1. Open up the project's properties window and set the "Enable ASP.NET Debugging" option.
2. Open up your web.config file and make sure the Compilation tag's debug attribute is set to true.
This action might not be possible to undo. Are you sure you want to continue?