Error: Can't start debugging on the web server See debug script and web: errors and troubleshooting When trying to debug the application running on the web server, sometimes you may get the following error message:
Unable to Start Debugging on the Web Server 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 Debugging: 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? See the debug mode in the ASP.NET application for more information. Does the web.config file 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. If the ASP.NET assist process runs under your own account, you must be a member or administrator of the "Debugger Users" group. If the ASP.NET assist process runs under any other user's account, you must be a member of the "Administrators" 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 installed later, you may need to fix the .NET Framework. Repair .NET Framework
Insert the Visual Studio .NET CD and enter the following line command at the command line:
Insert the Visual Studio .NET Requirements CD and enter the following line command at the command line:
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 the web application and select Properties. In the Properties window of the web application, 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 questions:
Whether to run the correct installer to install the ASP.NET or ATL Server and Remote Debugger Components on the server? Do you have access privileges necessary to debug the process running under the system account? If the ASP.NET assist process runs under your own account, you must be a member or administrator of the "Debugger Users" group. If the ASP.NET assist process runs under any other user's account, you must be a member of the "Administrators" group. (For specific operations, see Adding a debugger user and configuring DCOM.) By default, the ASP.NET application runs as an ASPNET. 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. (On Windows Server 2003, the name of the auxiliary process is w3wp.exe instead of ASPNET_WP.exe, you can use IIS to change the account.) To debug applications running under inetinfo.exe, you must be running inetinfo Administrator on the computer .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 you can use the public language runtime application setting to configure DLLHOST 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. IIS on Windows Server 2003 When you install Visual Studio .NET on Windows Server 2003, ASP.NET is not enabled by default. To develop web projects, you must run "Security Prevention Wizard" after completing the Visual Studio .NET installer.
If you run "Security Preventive Wizard" before completing the Visual Studio .Net installer, you may not enable the correct ASP.NET version. The Visual Studio .NET installer installs a new ASP.NET version. To ensure that the latest ASP.NET version is enabled, you must run "Security Preventive Wizard" after completing the installation.
Configuring IIS after running the installer on Windows Server 2003
From the Start menu, select All Programs. Select Administrative Tools and select Internet Information Services. Right-click on the name of the computer in the left pane, then select Security. On the first screen of "Safety Prevention Wizard", click Next. Verify that "http" is set to "Auto", and then click Next. In the Request Processor list, check each instance of ASP.NET and N: /Windows / Microsoft.Net/framework/
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 for ASPNET_WP.EXE (for the ASP.NET application under Windows Server 2003 for W3WP_WP.exe). Use the following procedure to determine which process is running under the ASP.NET or ATL Server application.
Check which process of the ASP.NET application runs under
Open the application's Machine.config file using the Visual Studio .NET or other text editor. Find the following process model attribute: enable If the enable is set to True, the application runs under ASPNET_WP.EXE or W3WP.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 the
If this is set to "Medium (Pool)", the application runs under the DLLHost.exe process (same as those in the Pool).
If this is set to "High (independent)", the application runs under the DLLHOST.EXE process (different from other ATL Server applications).
Click "OK" to close the
