Finally, this is so resolved from the "Start" menu, select "Programs" and "Administrative Tools" in turn, and then click Internet Service Manager (Windows 2000) or "Internet Information Services". In the Internet Service Manager or the Internet Information Services dialog box, click Tree Control for your computer. In the Web Site folder, find the Default Web Site. Right click on "Default Web Site" and select Properties. In the Default Web Site Properties window, select the Directory Security tab and click Edit. In the Authentication Method dialog box, select "Anonymous Access" and "Integrated Windows Authentication" (if you haven't selected). Click OK to close the Internet Service Manager or the Internet Information Services dialog. Click OK.
Mainly through this article
Unable to start debugging on the Web Servera: If you encounter these errors, you need to consider the following questions:
To check the Web application on the remote server in the remote server stores in Visual SourceSafe and use the FrontPage server extension web application manually attached to the content to check, if you get "Unable to start debug on the web server" error, try check the following:
Are you running a Windows version that allows the Visual Studio debugger to automatically attach to a web application? If not, you need to start the application without debugging, and then attach it to it manually. (For more information, see Manual Addition and ASP.NET Debug: System Requirements.) Does your web application have a web.config file? Whether the web.config file enables debug mode by setting the debug property to True? For more information, see the debug mode in the ASP.NET application. Does web.config contain any syntax errors? You can check if there is a syntax error by running a web application without debugging. (From the "Debug" menu, select "Start (not debug)".) If there is a syntax error in the web.config, the details are displayed. Are you a member of the debugger user (Debugger users)? If you log in as an administrator, is the administrator in this group? Are you creating a project by specifying a specific IP address (such as 100.20.300.400)? Debug web server requires NTLM authentication. By default, the IP address is assumed to be part of the Internet, and NTLM authentication is not performed on the Internet. To correct this question: When you create an item, specify the name of your computer on the intranet. -or-
Add IP addresses (http://100.20.300.400) to the trusted site list on your computer. (From Internet Explorer's Tools menu, select "Internet Options" and select the Security tab). Does the computer running the IIS server have installed Visual Studio .NET remote components? Is IIS installed on a local computer (ie computer running Visual Studio .NET) after installation of Visual Studio .NET installed? IIS should be installed before installing Visual Studio .NET. If it is later installed, you may need to fix the .NET framework. Fix the .NET framework into the Visual Studio .NET CD and run
: /WCU/dotNetFramework/dotNetfx.exe / T: C: / Temp / C: "msiexec.exe / fvecms c: /temp/netfx.msi" - or -
Insert Visual Studio .NET Windows Components Update CD and run
: / DOTNETFRAMEWORK / DOTNETFX.EXE / T: C: / TEMP / C :"msiexec.exe / fvecms c: /temp/netfx.msi "Does the URL of the project start page correctly? Is the extension and project directory correct? Do IIS security settings correctly? To verify this, check the Default Web Site settings. Check IIS security settings for "default Web site"
From the "Start" menu, select Programs and Administrative Tools, then click Internet Service Manager (Windows 2000) or "Internet Information Services". In the Internet Service Manager or the Internet Information Services dialog box, click Tree Control for your computer. In the Web Site folder, find the Default Web Site. Right click on "Default Web Site" and select Properties. In the Default Web Site Properties window, select the Directory Security tab and click Edit. In the Authentication Method dialog box, select "Anonymous Access" and "Integrated Windows Authentication" (if you haven't selected). Click OK to close the Internet Service Manager or the Internet Information Services dialog. Click OK. For the ATL Server application, verify that the debug predicate is associated with your ISAPI extension. For ASP.NET applications, make sure that the application's virtual folder has an "application name" set in "Internet Service Manager" or "Internet Information Service". Specify virtual folders for web applications
From the "Start" menu, select Programs and Administrative Tools, then click Internet Service Manager (Windows 2000) or "Internet Information Services". In the Internet Service Manager or the Internet Information Services dialog box, click Tree Control for your computer. In the Web Site folder, find this web application. Right click on "Default Web Site" and select Properties. In the Default Web Site Properties window, select the Directory tab. Under Application Settings, click Create. The application name appears in this box.
Click "OK" to close the Properties dialog. Click OK to close the Internet Service Manager or the Internet Information Services dialog. Web applications on remote servers If the web application is on the remote server, check the following: Will you run the correct installer to install the ASP.NET/atl Server and Remote Debugger Components on the server? Are you a member of the debugger user (Debugger user "group on the server? Do you have access privileges necessary to debug the process running under the system account? According to the security settings, the ASP.NET application may run under the INetInfo.exe (IIS process), or it is possible to run in the ASP secondary process aspnet_wp.exe. By default, the ASPNET_WP.EXE process runs as a System. To debug applications running under ASPNET_WP.EXE, you need to have administrator privileges or edit the machine.config file for ASPNET_WP.exe so that ASPNET_WP.EXE is running under user accounts. To debug an application running under inetinfo.exe, you must be an administrator on a computer that runs in inetinfo.exe.
According to the security settings, the ATL Server application may run under inetinfo.exe or run under the ATL assist process Dllhost.exe. To debug an application running under inetinfo.exe, you must be an administrator on the computer that runs INetInfo.exe, or uses the public language Runtuance Application setting to configure DLLHOST to run as a specific user. Are you using the Terminal Server try to debug a web application on a remote computer? Under Windows XP, you support the use of "Terminal Server" to remotely debug the native web application. It is not supported in Windows 2000 or Windows NT. WEB applications stored in Visual SourceSafe and extended using FrontPage Server If the web application stores in Visual SourceSafe and uses FrontPage Server Extensions as its web access mode, check the following questions:
Does Visual SourceSafe are located on the same computer with the FrontPage Server / Web server? If so, you can use "Integrated Authentication" to debug. (To check "Integrated Authentication" settings, see this procedure to check the "default Web site" IIS security settings.) Solving another method of this problem is to change the web access mode from FrontPage to file sharing File Share). Change the web access mode to file sharing (File Share)
In the Solution Explorer, right-click the project name and select Properties from the shortcut menu. in"
In the Properties Page dialog box, open the General Properties folder, then select "Web Settings". Under "Web Server Connection", click Web Access Mode, then select "File Sharing" in the list box. Single "OK" to close "
Property Page Dialog. Manual Additional Action If you perform the appropriate action by following these troubleshooting steps, you still receive an error message when you start debugging, you may need to try to debug your application by manually attach.
Manual addition
Start the application without debugging. (From the "Debug" menu, select "Start (not debug)".) Additional IIS processes or auxiliary processes. By default, for the ATL Server application for inetinfo.exe; for the ASP.NET application as ASPNET_WP.EXE. Use the following procedure to determine which process is running under the ASP.NET or ATL Server application. Check which procedure running under the ASP.NET application Using the Visual Studio .NET or other text editor opens the application's Machine.config file. Find the following process model attribute: enable If the enable is set to True, the application runs under ASPNET_WP.EXE (this is also the default setting.)
If the enable is set to false, the application runs under inetinfo.exe.
Check which process of the ATL Server application is running
In the Solution Explorer, right-click the project name and select Properties from the shortcut menu. in"
In the Properties Page dialog box, open the Web Deploy folder, then select "General". View "Application Protection" settings. If this is set to "low (IIS process)", the application runs under inetinfo.exe If this is set to "Medium (Pool)", the application runs under the dllhost.exe process (same as those in the ATL Server application in the pool). If this is set to "High (independent)", The program runs under the DllHost.exe process (different from other ATL Server applications). Click "OK" to close "
Property Page dialog. See debug scripts and web: errors and troubleshooting
