Cannot start debugging on the web server. IIS workflow for running URL is not currently running

Question

I have a website type project (not a solution) in VS2010. I also have this folder configured as a website in IIS7. I can go to my site when I go to http: //myproject.local

This proves that IIS serves the site normally.

Now when I try to start a project from VS2010, so I can debug it, I get the following error:

Unable to start debugging on the web server. The IIS workflow for the running URL is not currently running.

I have site properties set to invoke a custom server (IIS) with the correct URL. What is the reason that Visual Studio implies that the IIS workflow for the running URL is not running when the IIS core is the site server.

Answer 1

I managed to solve the problem using the following:

• Task Manager → delete IIS processes (IIS termination in the manager does not work)

• Go to IIS Manager

• Restart IIS

Answer 2

This is a very intermittent behavior. I usually get this problem once or twice a month. The following steps will help solve the problem easily.

Try iisreset before trying anything else

Step 1: >> Open Run (Ctrl + R) >> type iisreset

If this does not work, try step 2.

Step 2: Open the task manager >> Processes >> select the Process and right-click >> complete the task . This should kill the IIS workflow.

If step 2 does not work for you, go to step 3.

Step 3: Task Manager >> Services and restart IISADMIN.

Some of you may not have the IISADMIN service, so if you see IISADMIN, right-click and restart.

Answer 3

I had the same issue with IIS 8 (Windows 8 x64) and an ASP.NET MVC application hosted in IIS.

The solution for me was:

• clear solution in VS 2012
• run IIS Manager
• stop IIS (it took 3 minutes, I don't know why)
• restart the computer.
• rebuild solution
• start debugging

I am not sure what steps are needed; I (fortunately) cannot reproduce the problem. I don't know if this matters, but I have 7 application pools and 3 different websites in IIS, but 2 out of 3 are currently stopped.

Answer 4

i managed to solve the problem as follows:

• opened a command prompt with administrator privileges and ran IISRESET
• opened IIS Manager, stopped the IIS server
• will clear the solution in Visual Studio
• IIS server is running again.
• restored the solution in Visual Studio

I can’t say what exactly caused the problem, but with these steps I was able to start it again without rebooting.

Answer 5

I also had the same problem, and I fixed it simply by disposing of the application pool.

Answer 6

I had an animation site configured for different application pools. As stated in this answer , I deleted all other sites (which were stopped) in order to save only the one I need.

As mentioned in StuartLC: "if another site also maps to the same IP / port, even if it is disabled, it confuses VS"

Hope this helps ...

Answer 7

I had the same problem. The solution was to check the hosts file. There should be no rules for "localhost".

Answer 8

On my computer, the problem was that I had 2 bids on the same site, and Visual Studio was unable to contact the corresponding website.

I stop the “other” website (not the one that was the trigger for Debug), then the Debug action can begin.

Answer 9

I needed to enable windows authentication.

Turn on the window function: Control Panel → Programs → Programs and Features → Turn Windows Features on or off → Internet Information Services → World Wide Web Services → Security → Windows Authentication.

Open IIS Manager, go to your website, double-click the Authentication icon in the IIS category, and enable Windows Authentication.

Answer 10

I also ran into the same problem. He decided when I changed the application pool in IIS settings using Classic .NET AppPool to DefaultAppPool .

Answer 11

Just having finished the task, the IIS workflow resolved this for me.

Answer 12

Command line usage
Open a window with an elevated command prompt.
At the command prompt, type net stop WAS and press ENTER; type Y, then press ENTER to stop W3SVC.
To restart the web server, type net start W3SVC and press ENTER to start WAS and W3SVC.

link
https://technet.microsoft.com/en-us/library/b9339773-7eff-4313-a14b-00f2b9f94ead

or

https://msdn.microsoft.com/zh-tw/library/ms957500(v=cs.70).aspx

Answer 13

1) Close the browser.

2) Enter in CMD: iisreset

Answer 14

complete the entire iis process task and restart iis. it worked for me.