Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Web Development
  3. ASP.NET
  4. How can I do to fix the error "Unable to start debugging on the web server"

How can I do to fix the error "Unable to start debugging on the web server"

Scheduled Pinned Locked Moved ASP.NET
helpcsharpsecuritydebuggingquestion
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    R Offline
    rockxuyenmandem
    wrote on last edited by
    #1

    When I Debug any ASP.NET Applicaion 1.1, It is unable to Debug with the message below: "Error while trying to run project: Unable to start debugging on the web server" I have checked all of guides below however all of it not solve my problem, However I can Debug any ASP.NET Application 2.0, I found that When I have installed Visual Studio 2005, I unable to Debug any ASP.NET Application 1.1 Are there any conflict? How can I do to Debug ASP.NET 1.1 ??? Please help me!!! Thanks Alot Things to Check If you get an "Unable to start debugging on the Web server" error, try checking the following things: * 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 and ASP.NET Debugging: System Requirements.) * Does your Web application have a Web.config file? o Does the Web.config file enable debug mode) by setting the debug attribute to true? For more information, see Debug Mode in ASP.NET Applications. o 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. * You need to be a member of the Debugger Users group or an administrator if the ASP.NET worker process runs under your own user account. * You need to be a member of the Administrators group if the ASP.NET worker process runs under any other user account besides your own. * Did you create the project by specifying a specific IP address (100.20.300.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: o When creating the project, specify the name of the machine on your intranet. -or- o Add the IP address (http://100.20.300.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). * Does the machine running IIS server have Visual Studio .NET Remote Components installed? * Was IIS installed on the local machine (the machine running Visual Studio .NET) after Visual Studio .NET was installed? IIS should

    R 1 Reply Last reply
    0
    • R rockxuyenmandem

      When I Debug any ASP.NET Applicaion 1.1, It is unable to Debug with the message below: "Error while trying to run project: Unable to start debugging on the web server" I have checked all of guides below however all of it not solve my problem, However I can Debug any ASP.NET Application 2.0, I found that When I have installed Visual Studio 2005, I unable to Debug any ASP.NET Application 1.1 Are there any conflict? How can I do to Debug ASP.NET 1.1 ??? Please help me!!! Thanks Alot Things to Check If you get an "Unable to start debugging on the Web server" error, try checking the following things: * 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 and ASP.NET Debugging: System Requirements.) * Does your Web application have a Web.config file? o Does the Web.config file enable debug mode) by setting the debug attribute to true? For more information, see Debug Mode in ASP.NET Applications. o 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. * You need to be a member of the Debugger Users group or an administrator if the ASP.NET worker process runs under your own user account. * You need to be a member of the Administrators group if the ASP.NET worker process runs under any other user account besides your own. * Did you create the project by specifying a specific IP address (100.20.300.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: o When creating the project, specify the name of the machine on your intranet. -or- o Add the IP address (http://100.20.300.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). * Does the machine running IIS server have Visual Studio .NET Remote Components installed? * Was IIS installed on the local machine (the machine running Visual Studio .NET) after Visual Studio .NET was installed? IIS should

      R Offline
      R Offline
      rijjjesh
      wrote on last edited by
      #2

      Hi mesage indicates that the issue is with the IIS. Try Reseting the IIS by typing "iisreset" in the command prompt.... Even if the issue continues, u may reiinstall the IIS and check if it helps... regds rijesh

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups