Error: unable to start debugging on the Web server (from msdn)

When you tryProgramThis error message may sometimes be obtained during debugging:
Unable to start debugging on the Web Server
If the error message you get is longer than this message, the subtopic under this topic describes it.

If you encounter this error, consider things to check and consider other projects based on the hardware and software configurations of your machine.

• Things to check

• Web applications on remote servers

• Web applications stored in visual sourcesafe and using FrontPage Server Extensions

• Manually attaching

• Debug request cocould not be processed by the server due to invalid syntax

Things to check

Try checking the following things:

Try to perform the following check:

• Review the procedures for setting up ASP. NET or ATL server. For more information seeGetting ready to debug ASP. NET Applications.
  Review the process of installing ASP. NET or ATL server. For more information, seeGetting ready to debug ASP. NET Applications.

• Do you have the necessary access privileges for debugging? For more information seeSecurity requirementsSection inASP. NET debugging: System Requirements.

  Do you have the debugging permission? For more information, seeASP. NET debugging: System RequirementsSecurity requirements section.

• Are you running a version of Windows that allows the Visual Studio debugger to automatically attach to a web application? If not, you need to launch the application without debugging and manually attach to it. (For more information, see manually attaching andASP. NET debugging: System Requirements.)

  Are you using the Windows version that allows the Visual Studio debugger to automatically attach to a web application (bind a web application? If not, you need to start the application without debugging and manually bind it. (For more information, see Manual binding andASP. NET debugging: System RequirementsPart)

• Does your web application have a web. config file?

  Does the Web application have a web. config file?

• • does the Web. config file enable debug mode by setting the debug attribute to true ? For more information, see How to: Enable debugging for ASP. net Applications .

    in the web. is DEBUG = "true" set in the config file "? For more information, see...

  • does the Web. config file contain any syntax errors? You can check for syntax errors by running the web application without debugging. (From the Debug menu, choose Start without debugging .) if there are syntax errors in web. config, detailed information will be displayed.

    Web. is there a syntax error in the config file? Run F5 to check for syntax errors. If any syntax error occurs, its details are displayed.

• Did you create the project by specifying a specific IP address (100.0000300.400, for example )? Debugging a web server requires NTLM authentication. By default, IP addresses are assumed to be part of the Internet, and NTLM authentication is not done over the Internet. To correct this problem:
  Did I specify an IP address when creating a project? NTLM authorization is required for Web Server debugging. by default, IP addresses are part of the Internet, but NTLM authorization cannot be performed over the Internet. the solution to this problem is as follows: (when there is this problem, the system will prompt: unable to start debugging on the Web server. the project is using a web site that is configured with IP adress ....)

  • When creating the project, specify the name of the machine on your intranet.

    Specify your host name in the Intranet when creating a project.

    -Or-

  • Add the IP address (http: // 100.0000300.400) to the list of trusted sites on your computer. (from the Internet Explorer Tools menu, choose Internet Options, and then select the Security Tab ).

    Add the IP address to the trusted site on your computer. (select option> security from the tool menu in IE browser ).

  Are the necessary extensions registered on the server machine? If not, re-register ASP. NET as described in the procedure below.

  Are Necessary extensions registered on the server? If no, register ASP. NET again.