Getting unable to start debuggin on the web server. Could not start ASP.NET debugging

Question

0.00/5 (No votes)

See more:

C# 2013. Web MVC app, Win 7/64 pro ISS 7, .Net 4.5

This morning I wanted to see if I could get this MVC app running locally outside the IDE.

Before I started I was able to run it within the IDE.

I published it to a folder a few days ago and today tried to run it locally. NG always get 503 errors. Tried some IIS restarting of app pools, etc., re-boots No luck.

So I went back to trying it in the IDE and not I cannot run it at all. Get
'Unable to start debugging on the web server. Unable to connect to the web server' when I run as Admin. (I do have admin rights) and 'Unable to start debugging on the web server. Could not start ASP.Net debugging.'

I get these messages run running in debug or release mode.

Nothing except debug to release and back was changed in the project.

I did create a new dummy web page and that came up.

Please Help, I am now dead in the water on this.

What I have tried:

Restart application pools
rebooting the system

Posted 19-Mar-16 3:00am

QuickBooksDev

Updated 19-Mar-16 4:15am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2016-03-19T04:15:00

Solution 1

You're not the first one to come up against this and there's a list of possible causes. I suggest you Google for "iis express unable to start debugging on the web server" and start reading. There's a lot of stuff to check.

Posted 19-Mar-16 4:15am

Dave Kreskowiak

Comments

QuickBooksDev 19-Mar-16 10:32am

Already did but they talk about basically new projects. It was working a few hours ago then it stopped. So I would understand if it was the first time or did some massive updates but that didn't happen. Just tried to enable the published app to run locally. I will keep looking but I looked for an hour already.

QuickBooksDev 19-Mar-16 10:40am

I have now tried deleting the IISExpress folder (no help)
I then started without debugging and now get a 503 the Service is unavailable.
All pools are started.