13

I am running Visual Studio 2008, IIS 7.5 on Windows 7 x32. I am able to run the ASP.NET web site in IIS 7.5 without debugging just fine, but when I press F5 to debug it, I get:

Unable to start debugging on the web server. Unable to connect to the webserver. Verify that the web server is running and that incoming http requests are not blocked by a firewall..

Improve this question
0

8 Answers 8

Reset to default
15

In VS, right click on your web project --> Properties Go to the Web tab.

Make sure the appropriate radio button is selected (Use VS Dev Server, Use Local IIS Web Server, etc)

After a computer freeze I've had that value change on me.

Another thing to try:

Run "iisreset" from an administrative command prompt (basically just restarts the IIS service)

Improve this answer
Sign up to request clarification or add additional context in comments.

3 Comments

"Make sure the appropriate radio button is selected" - this worked! I think is the first thing to check.
What appropriate button... Make sure the appropriate radio button is selected.. this is vague..
(Use VS Dev Server, Use Local IIS Web Server, etc) For whichever web server you want to start, that the app will run in. It's mid-way toward the bottom of the page. VS Dev Server used to be called IIS Express.
6

Check if your IIS is running, if isn't try to initialize him and run again on VS.

Improve this answer

2 Comments

I went to the Services control panel, and found my World Wide Web Publishing Service was not running. I hit "start" and was able to debug.
In my case IIS was paused. Restarted and the error "unable to start debugging on the web server verify that the web server is running and incoming http request are not blocked by a firewall" went away
2

Try the following:

  1. Open IIS > Add a new Application (not a virtual folder) to the Default Website.
  2. Make sure the application runs under the right .net framework version (i.e. DefaultAppPool ussually runs under .Net 4.0)
  3. Map the application in IIS to the right project folder (where your bin and obj folder appear after a build)
  4. In IIS, right-click the application, and click 'Manage application' > 'Browse'. This will launch an internet exploreren to the right path. This could be localhost:80/Shop instead of the expected localhost/Shop (caused by for example a reservation for other applications of the direct localhost/ location)
  5. In Visual Studio > go to the application properties > Web > check Use local IIS > and set the correct location of your application in IIS (you should know this from step 4)
Improve this answer

Comments

0

Verify that your web.config has the following entry:

<compilation debug="true" targetFramework="2.0" />

Note: If you are targeting framework 1.1, then obviously change the 2.0 to 1.1.

UPDATE:

The `targetFramework` attribute is new in .NET 4.0 and later, so to enable debugging on .NET 2.0 and earlier, then you cannot use the `targetFramework` attribute, like this:

<compilation debug="true" />
Improve this answer

1 Comment

Ah sorry my fault, in .NET 4.0 they added the targetFramework attribute to the compilation element in web.config, just remove the targetFramework="2.0" attribute and value, answer updated.
0

Just to check: See if Windows Authentication is enabled or not? It should be enabled. Internet Information Services (IIS) Manager > Expand PC/Server Name > Expand Sites > Select Default Web Site > Select Authentication. It should be enabled.

Improve this answer

2 Comments

it's showing a error msg(unable to start debuggin on the web server. the server committed a protocol violation. Section=ResponseStatusLine)
It happens if some other application(like skype) take the port 80/ 443.
0

Make sure that the port defined in the Project Url under the Web tab of the properties of the web project is the same one as defined in the IIS Manager.

I had this issue and fixing the port solved the problem for me.

Improve this answer

Comments

0

I had a case, where I could load the site in chrome, but deugger could contact the server. Turns out Chrome auto-maps .localhost addresses, but VS does not.

Adding the localhost address to my hosts file solved the issue.

Improve this answer

Comments

0

In my case I was unable to debug the application. I also get same error: "Unable to debug application", "Unable to connect to remote server". The issue occurs when API doesn't match with IIS when creating virtual directory; it just creates a path but it will never match if you've deleted something.

Solution:

  • Open IIS service manager
  • Start default website by right click on icon and click on start enter image description here
  • If it's already running, then right click on sites and click on Add Website enter image description here
  • Add the path of the WebApi and fill the fields
Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.