During the last several months, I have dealt with many users from both inside and outside of Microsoft who have debugging issues.I noticed that there are many common mistakes and problems that can be solved, if users are provided with proper diagnosis.Hence, I’ve written this document to provide you with this information which will help you if you run into any issues while using the debugger. If setup has been run verify that a valid URL has been specified.Your IIS application of IIS is not configured to use “integrated Windows authentication”. NET and ATL Server debugging topic in the online documentation. 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. If you have an XP Pro or W2K Pro machine, you may need to think about the order of installation between VS7 and IIS.Please make sure that the “integrated windows authentication” checkbox on the “authentication method” dialog box is checked. Verify there are no syntax errors in web.config by doing a Debug. Would you like to disable future attempts to debug ASP. Would you like to disable future attempts to debug ASP. "Error while trying to run project: Unable to start debugging on theweb server. If you install IIS after VS7, you will get this error.You do not have privileges to debug the web serverprocess. Would you like to disable future attempts to debug ASP. Error while trying to run project: Unable to start debugging on the web server. In this case, please register “aspnet_isapi.dll” with “aspnet_–i”.
Error while trying to run project: Unable to start debugging on the web server. Would you like to disable future attempts to debug ASP. or Error while trying to run project: Unable to start debugging on the web server. case 1: You may be the member of “Debugger users” group, but you don’t have the right to debug the aspnet worker process, because you are not the “aspnet” user account or the member of “Administrators” group.Please add your user account to the “Administrators” group on the machine.case 2: You need to make sure that your user account is admin or same user account of ASP. currently CLR debugging service has security restriction to allow only admin or same user to debug managed process.so unless you are admin or same user, you can't debug ASP.NET worker process(W3on IIS6-Windows 2003 or Aspnet_on other OSes).if you can't be admin on the server box, but you have Windows 2003 server, you have a work-around by using separate app-pool.