无法在 Web 服务器上启动调试。启动的 URL 的 IIS 工作进程当前未运行
我在 VS2010 中有一个网站（不是解决方案）类型的项目。 我还在 IIS7 中将此文件夹配置为网站。当我导航到 http://myproject.local 时，我可以正常浏览到我的网站，
这证明 IIS 可以正常为网站提供服务。
现在，当我尝试从 VS2010 运行项目以便进行调试时，出现以下错误：
无法在 Web 服务器上启动调试。启动的 URL 的 IIS 工作进程当前未运行。
我已将站点属性设置为在正确的 URL 处调用自定义服务器 (IIS)。 当显然 IIS 是该站点的服务器时，Visual Studio 暗示启动的 URL 的 IIS 工作进程未运行的原因是什么。
I have a web site (not a solution) type project in VS2010.
I also have this folder configured as a web site in IIS7. I can browse to my site fine when I navigate to http://myproject.local
This proves IIS is serving the site ok.
Now when I try and run the project from VS2010 so I can debug, I get the following error:
Unable to start debugging on the web server. The IIS worker process for the launched URL is not currently running.
I have the site properties set to invoke the custom server (IIS) at the correct URL.
What is the reason for Visual Studio implying that the IIS work process for the launched URL is not running, when clearly IIS is server the site.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（16）
这是一种非常间歇性的行为。我通常每个月都会遇到一两次这个问题。按照以下步骤可以轻松解决问题。
在尝试其他操作之前，请尝试 iisreset
如果这不起作用，请尝试步骤2。
步骤2：打开任务管理器>> 流程>>选择“进程”并右键单击>> 结束任务。这应该会终止 IIS 工作进程。
如果步骤 2 不适合您，请转到步骤 3。
步骤 3： 任务管理器>>服务并重新启动 IISADMIN。
This is a very intermittent behavior. I usually get this issue once or twice a month. Following steps would resolve the problem easily.
Before trying anything else, try iisreset
If this doesn't work, then try step 2.
Step 2: Open task manager >> Processes >> select Process and right click >> end task. This should kill IIS worker process.
If step 2 doesn't work for you then go to step 3.
Step 3: Task manager >> Services and restart the IISADMIN.
我设法使用以下方法解决了该问题：
任务管理器 ->删除 IIS 进程（在管理器中停止 IIS 不起作用）
进入 IIS 管理器
I managed to solve the problem using the following:
Task Manager -> delete IIS process(es) (stopping IIS in the manager didn't work)
Go into IIS manager
我能够按如下方式解决问题：
无法说出到底是什么原因问题，但通过这些步骤，我无需重新启动即可使其再次工作。
i was able to solve the problem as follows:
cannot say what exactly caused the problem, but with these steps i was able to get it working again without a reboot.
我在 IIS 8 (Windows 8 x64) 和 IIS 中托管的 ASP.NET MVC 应用程序中遇到了同样的问题。
我的解决方案是：
我不确定需要哪些步骤，我（幸运的是） ）无法重现该问题。我不知道这是否重要，但我在 IIS 中有 7 个应用程序池和 3 个不同的网站，但目前 3 个中的 2 个已停止。
I had the same problem with IIS 8 (Windows 8 x64) and an ASP.NET MVC application hosted in IIS.
The solution for me was:
I'm not sure which steps are required, I (fortunately) can't reproduce the problem. I don't know if that matters but I have 7 app pools and 3 different web sites in IIS, but 2 of the 3 are stopped at the moment.
我将多个站点配置到不同的应用程序池。正如在此答案中所述，我已删除所有其他网站（已停止），只保留我需要的网站。
正如 StuartLC 所提到的：“如果另一个站点也映射到相同的 IP / 端口，即使它被停止禁用，它也会使 VS 感到困惑”
希望它会有所帮助......
I had multiples site configured to different Application Pools. As stated in this answer, I have removed all other sites (which were stopped) to only keep the one that I needed.
As mentioned by StuartLC : "if another site is also mapped to same IP / Port, even if it is stopped disabled, it confuses VS"
Hope it will help...
我也遇到了同样的问题，只需通过回收应用程序池即可解决它。
I also had the same issue and fixed it simply by recycling the app pool.
我也有同样的问题。
解决方案是检查主机文件。 “localhost”不应该有任何规则。
I had the same problem.
The solution was to check hosts file. There should be no rules for "localhost".
在我的计算机上，问题是我对同一网站进行了两次出价，并且 Visual Studio 无法联系正确的网站。
我停止“其他”网站（不是我尝试调试的网站），然后停止调试
行动可以开始了。
On my computer the issue was that I had 2 bidding to the same site and Visual Studio could not contact the proper web site.
I stop the "other" web site (not the one I was triyng to Debug) then the Debug
action could start.
我必须启用 Windows 身份验证才能修复它。
打开窗口功能：控制面板->节目->程序和功能 ->打开或关闭 Windows 功能 ->互联网信息服务->万维网服务 ->安全-> Windows 身份验证。
打开 Internet 信息服务 (IIS) 管理器，导航到您的网站，双击 IIS 类别下的身份验证图标，然后启用 Windows 身份验证。
I had to enable Windows Authentication to fix it.
Turn on window feature: Control Panel -> Programs -> Programs and Features -> Turn Windows features on or off -> Internet Information Services -> World Wide Web Services -> Security -> Windows Authentication.
Open Internet Information Services (IIS) Manager, navigate to your web site, double-click Authentication icon under IIS category, and enable Windows Authentication.
我也遇到了同样的问题。当我将 IIS 高级设置中的应用程序池从 Classic .NET AppPool 更改为 DefaultAppPool 时，它解决了。
I also faced the same problem.It solved when I changed Application Pool in IIS Advanced Settings from Classic .NET AppPool to DefaultAppPool.
只需结束任务，IIS 工作进程就为我解决了这个问题。
Just end task the IIS Worker process resolved it for me.
使用命令行
打开提升的命令行窗口。
在命令提示符下，输入 net stop WAS 并按 ENTER 键；键入 Y，然后按 ENTER 键也可以停止 W3SVC。
要重新启动 Web 服务器，请键入 net start W3SVC 并按 ENTER 键启动 WAS 和 W3SVC。
参考
https://technet.microsoft.com/en-us/library/b9339773-7eff-4313-a14b-00f2b9f94ead
或
https://msdn.microsoft.com/zh-tw/library/ms957500(v=cs.70).aspx
Using a command line
Open an elevated command-line window.
At the command prompt, type net stop WAS and press ENTER; type Y and then press ENTER to also stop W3SVC.
To restart the Web server, type net start W3SVC and press ENTER to start both WAS and W3SVC.
reference
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
1）关闭浏览器。
2）在CMD中输入：iisreset
1) Close browser.
2) Enter in CMD: iisreset
结束任务所有iis进程并重新启动iis。
它对我有用。
end task all iis process and restart iis.
its worked for me.
停止/重新启动 IIS 进程对我来说都不起作用，相反，我遇到的问题是 IIS 管理器中有 2 个站点都在 localhost:80 上运行，即使 1 个站点被停止，它仍然与 VS 调试发生冲突。
所以我只是将停止的站点绑定更改为：8080，它解决了问题。
None of the stop/restart IIS processes worked for me, instead the problem I had was that there were 2 sites both running on localhost:80 in IIS Manager, even if 1 was stopped it still conflicted with VS debugging.
So I just changed the stopped sites binding to :8080 and it solved the problem.
我的问题是因为我上周更改了密码。
我进入我的 IIS 池 ->高级设置->导航到“身份”并输入我更新的凭据。
一旦我输入了这个，错误就消失了，我可以再次调试。
My issue turned out to be because I changed my password last week.
I went into my IIS pool -> Advanced Settings -> Navigated to Identity and entered in my updated credentials.
Once I input this, the error went away and I was able to debug again.