blocks|key|3212744|text|丹|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3212745|除了Aaron的建议之外，还可以尝试以下建议|3212746|3212747|检查是否在IIS网站中选择了集成的windows身份验证|unordered-list-item|3212748|您是否可以使用Cassini而不是IIS进行调试？|3212749|3212750|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|O|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|P|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|Q|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|L|$]]

Dan,

In addition to Aaron's suggestions, try the following

<ul>
<li>Check that integrated windows authentication is selected in your IIS website</li>
<li>Can you debug using Cassini instead of IIS?</li>
</ul>

blocks|key|286191|text|原来，罪魁祸首是IIS重写模块。我定义了一个规则，将对Default.aspx+(设置为网站的起始页)的调用重定向到站点的根目录，这样我就可以拥有一个规范的主页URL。然而，VS显然对此有问题，并对此感到困惑。当我使用Helicon+ISAPI_Rewrite时，这个问题没有发生，所以我甚至没有想过要检查一下。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|286192|我最终从头开始创建了一个全新的网站，一点一点地将项目/文件移植到我的解决方案中，并重新构建我的web.config，直到我发现这一点！好吧，至少现在我有了一个使用.NET+4.0的稍微干净一点的站点(到目前为止，希望我不会碰到任何障碍)--但这是多么痛苦的事情！|286193|entityMap^0|R|C|1B|31|0|0|3N|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

Turns out that the culprit was the IIS Url Rewrite module. I had defined a rule that redirected calls to Default.aspx (which was set as the start page of the web site) to the root of the site so that I could have a canonical home URL. However, apparently VS had a problem with this and got confused. This problem did not happen when I was using Helicon ISAPI_Rewrite so it didn't even occur to me to check.

I ended up creating a whole new web site from scratch and porting projects/files over little by little into my solution and rebuilding my web.config until I found this out!
Well, at least now I have a slightly cleaner site using .NET 4.0 (so far, hopefully I won't run into any walls)--but what a pain!

blocks|key|282941|text|尝试转到IIS并检查以确保您正在使用的应用程序池已启动。很多时候，你会产生一个关闭应用程序池的错误。您只需右键单击并启动，就可以开始了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|282942|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Try going to IIS and checking to make sure the App Pool you are using is started. A lot of times, you will produce an error that shuts down the app pool. You just need to right click and Start and you should be good to go.

blocks|key|3212824|text|在实现重写模块后，我遇到了完全相同的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3212825|如果我从web.config文件中删除重写条目，调试就能正常工作。|3212826|为了解决这个问题，我只想在调试时注释掉重写标签，就像这样……|3212827|<rewrite>
++++<rules>
++++++++<rule+name="LowerCaseRule_1"+stopProcessing="true">
++++++++++++<match+url="[A-Z]"+ignoreCase="false"+/>
++++++++++++<action+type="Redirect"+url="{ToLower:{URL}}"+/>
++++++++</rule>
++++++++<rule+name="RedirectDefault.aspx_1"+stopProcessing="true">
++++++++++++<match+url="(.*)default.aspx"+/>
++++++++++++<action+type="Redirect"+url="{R:1}"+redirectType="Permanent"+/>
++++++++</rule>
++++</rules>
</rewrite>|code-block|syntax|javascript|3212828|然后，我在调试后删除注释。|3212829|一定是visual+studio+2010中的错误。|3212830|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|T|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I have exactly the same problem after implementing the rewrite module.

If I remove the rewrite entries from my web.config file, debugging works perfectly.

To get around this, I just to comment out the rewrite tags while debugging, like this...

<pre><code>&lt;rewrite&gt;
 &lt;rules&gt;
 &lt;rule name="LowerCaseRule_1" stopProcessing="true"&gt;
 &lt;match url="[A-Z]" ignoreCase="false" /&gt;
 &lt;action type="Redirect" url="{ToLower:{URL}}" /&gt;
 &lt;/rule&gt;
 &lt;rule name="RedirectDefault.aspx_1" stopProcessing="true"&gt;
 &lt;match url="(.*)default.aspx" /&gt;
 &lt;action type="Redirect" url="{R:1}" redirectType="Permanent" /&gt;
 &lt;/rule&gt;
 &lt;/rules&gt;
&lt;/rewrite&gt;
</code></pre>

I then remove the comments after debugging.

Must be an bug in visual studio 2010.

blocks|key|282966|text|Visual+Studio在启动时将(出于某种原因)尝试访问URL：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|282967|282968|+/debugattach.aspx|blockquote|282969|282970|282971|如果您有一个重写规则来重定向(或以其他方式捕获)，比如.aspx文件，那么您将收到此错误。解决方案是将此部分添加到web.config的<system.webServer>/<rewrite>/<rules>部分的开头：|offset|length|style|CODE|282972|<rule+name="Ignore+Default.aspx"+enabled="true"+stopProcessing="true">
++++<match+url="%5Edebugattach\.aspx"+/>
++++<conditions+logicalGrouping="MatchAll"+trackAllCaptures="false"+/>
++++<action+type="None"+/>
</rule>|code-block|syntax|javascript|282973|这将确保捕获这个特定的请求，什么也不做，最重要的是，停止执行，这样您的其他规则都不会运行。这是一个健壮的解决方案，因此请随时将其保存在您的配置文件中以供生产使用。|282974|entityMap^0|0|0|0|0|0|R|5|1L|A|1W|10|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Y|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|11|8|@$J|12|K|13|L|M]|$J|14|K|15|L|M]|$J|16|K|17|L|M]]|9|@]|A|$]]|$1|N|3|O|5|P|7|18|8|@]|9|@]|A|$Q|R]]|$1|S|3|T|5|6|7|19|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|V|$]]

Visual Studio, when starting up, will (for some reason) attempt to access the URL:

<blockquote>
 /debugattach.aspx
</blockquote>

If you have a rewrite rule that redirects (or otherwise catches), say, <code>.aspx</code> files, somewhere else then you will get this error. The solution is to add this section to the beginning of your <code>web.config</code>'s <code>&lt;system.webServer&gt;/&lt;rewrite&gt;/&lt;rules&gt;</code> section:

<pre><code>&lt;rule name="Ignore Default.aspx" enabled="true" stopProcessing="true"&gt;
 &lt;match url="^debugattach\.aspx" /&gt;
 &lt;conditions logicalGrouping="MatchAll" trackAllCaptures="false" /&gt;
 &lt;action type="None" /&gt;
&lt;/rule&gt;
</code></pre>

This will make sure to catch this one particular request, do nothing, and, most importantly, stop execution so none of your other rules will get run. This is a robust solution, so feel free to keep this in your config file for production.

blocks|key|2999494|text|以下是我为清除您注意到的错误所做的工作。在文件系统中找到应用程序的web文件夹，单击高级按钮，然后单击+owner+选项卡，单击编辑按钮，更改文件夹的所有者(具有正确的权限)，并选中"Repalce+on+subcontainers++objects“复选框。点击"Apply“，然后我就可以开始工作了(可以调试)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2999495|希望这对其他人也有效。|2999496|entityMap^0|16|2|1F|7|1S|2|2K|1U|0|0|B|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|I|$]]

Here is what I did to clear the error you noted. Locate the web folder for the app within the file system, go to Properties=>Security click the Advanced button then click the Owner tab, click the Edit button and change the owner (with the correct permissions) of the folder and checked the "Repalce owner on subcontainers and objects" checkbox. Click "Apply" and then I was in business (able to debug).

Hope this works for someone else.

blocks|key|3212916|text|为了其他人的利益，在我的例子中，我已经将应用程序池配置为使用我的windows凭据来访问网络资源共享。自从上次调试解决方案以来，我已经重置了我的windows密码。更改了应用程序池和bada+bing中存储的密码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3212917|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For the benefit of others, in my case I had configured the application pool to use my windows credentials in order to access a network resource share. Since debugging the solution last I had reset my windows password. Changed password stored in app pool and bada bing.

blocks|key|286260|text|像这样移除sting+:+web.config中的targetFramework="4.0“或将AppPool更改为适当的框架版本。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|286261|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

remove sting like this: targetFramework="4.0" in web.config or change AppPool to appropriate framework version.

blocks|key|2999569|text|最终修复了我的单一解决方案的这个问题。解决方案中的两个项目被设置为IIS中的站点。我进入并在身份验证下为两个projects...and+VIOLA启用了ASP.Net模拟！最后，不要再犯这种恼人的错误了！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2999570|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Just finally fixed this for my single solution that was having this. Two of the projects in the solution were set as sites in IIS. I went in and enabled ASP.Net Impersonation under Authentication for both projects...and VIOLA! FINALLY, no more of this annoying error!

blocks|key|283061|text|对于我的场景，它是对web.config中的httpErrors部分的更改，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|283062|<httpErrors+mode="Custom">+|code-block|syntax|javascript|283063|导致“无法在web服务器上启动调试”问题。将其设置回以前的"DetailedLocalOnly“值修复了此问题。再深入一点，我发现实际上正是401错误设置导致了这一点：|283064|<httpErrors+mode="Custom">+
++++<error+statusCode="401"+prefixLanguageFilePath=""+path="/masterpages/500.html"+responseMode="ExecuteURL"+/>
<httpErrors+mode="Custom">+|283065|注释掉401错误行也修复了这个问题，因为这样我就可以维护自定义错误处理并开始调试了。|283066|我仍然不知道为什么会发生这种事。|283067|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

For my scenario it was changes to the httpErrors section in web.config, setting it like this:

<pre><code>&lt;httpErrors mode="Custom"&gt; 
</code></pre>

caused the "Unable to start debugging on the web server" issue. Setting it back to the previous value of "DetailedLocalOnly" fixed the issue. Digging a little deeper I discovered that it was actually just the 401 error setting that was causing this:

<pre><code>&lt;httpErrors mode="Custom"&gt; 
 &lt;error statusCode="401" prefixLanguageFilePath="" path="/masterpages/500.html" responseMode="ExecuteURL" /&gt;
&lt;httpErrors mode="Custom"&gt; 
</code></pre>

Commenting out the 401 error line fixed the issue as well, I went with that since I can then maintain the custom error handling and start with debugging.

I still have no idea why this is happening.

blocks|key|283069|text|由于应用程序池在IIS中已停止，因此我收到了相同的错误。启动应用程序池后，问题已解决。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|283070|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I got the same error since Application pool was stopped in IIS. After starting the App Pool, the issue was resolved.

blocks|key|286336|text|我今天遇到了这个错误，原因是代码中的一个缺陷导致IIS被大量请求淹没。这实际上锁定了IIS，因此当我尝试调试时，它在尝试启动调试器时“超时”。我简单地重新启动了IIS，这花了几分钟的时间，它解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|286337|我确实希望这个错误不是那么普遍，似乎有几种不同的方法来产生它。|286338|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had this error come up today due to a defect in code that was posting back a tremendous amount of times causing IIS to be flooded with requests. This essentially locked up IIS and so when I tried to debug, it 'timed out' trying to start the debugger. I simply restarted IIS, which took a few minutes, and it solved the issue.

I sure do wish this error was less generic, seems like there are several different ways to produce it.

blocks|key|285376|text|如果ApplicationPool身份设置为自定义帐户且更改了计算机密码，则必须更新密码|type|unstyled|depth|inlineStyleRanges|entityRanges|data|285377|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If ApplicationPool Identity is set custom account and computer's password is changed, you have to update your password

blocks|key|2999798|text|尝试调试DNN+(Dot+Net+Nuke)模块时遇到同样的问题。事实证明，您需要将编译debug=设置为“真”：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2999799|<compilation+debug="true"+strict="false"+targetFramework="4.0">+|code-block|syntax|javascript|2999800|在你的web.config里。默认情况下，它在DNN中为false。原文来源：http://www.dnnsoftware.com/forums/forumid/111/postid/189880/scope/posts|offset|length|2999801|entityMap|0|LINK|mutability|MUTABLE|url|http://www.dnnsoftware.com/forums/forumid/111/postid/189880/scope/posts^0|0|0|13|1Z|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

Had the same issue trying to debug a DNN (Dot Net Nuke) module.
Turned out you need to have compilation debug="true":

<pre><code>&lt;compilation debug="true" strict="false" targetFramework="4.0"&gt; 
</code></pre>

in your web.config. By default it is false in DNN. Original source here:
<a href="http://www.dnnsoftware.com/forums/forumid/111/postid/189880/scope/posts" rel="noreferrer">http://www.dnnsoftware.com/forums/forumid/111/postid/189880/scope/posts</a>

blocks|key|286378|text|我在Windows+8.1上的Visual+Studio+2012和2013中也遇到了同样的问题。对我来说，修复方法是使用“打开或关闭Windows功能”将Windows身份验证添加到IIS|type|unstyled|depth|inlineStyleRanges|entityRanges|data|286379|​|286380|📷|atomic|offset|length|286381|286382|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/93e44e3eff2f8e85e95edabcf76c371d.jpeg|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

I had the same problem in Visual Studio 2012 and 2013 on Windows 8.1. For me the fix was to add Windows Authentication to IIS using 'Turn Windows features on or off'

<img src="https://i.stack.imgur.com/GtTRg.jpg" alt="Turn Windows features on or off screenshot">

blocks|key|3213250|text|卸载IIS+UrlScan扩展为我解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3213251|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Uninstalling the IIS UrlScan Extension solved the problem for me.

blocks|key|3213264|text|确保站点的应用程序池使用正确的框架版本。我在ASP.Net+2005站点上收到"Unable+to+start+debugging“错误。它在Windows7(我认为它使用的是.Net+Framework4)上错误地使用了DefaultAppPool。我基于.Net+Framework2创建了一个新的应用程序池，并将其分配到有问题的网站。在那之后，调试就很好了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3213265|entityMap^0|0|J|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Be sure your site's Application Pool uses the correct framework version. I got the "Unable to start debugging" error on an ASP.Net 2005 site. It was incorrectly using the DefaultAppPool on Windows 7 (which I believe was using .Net Framework 4). I created a new a App Pool based on .Net Framework 2 and assigned it to the problem web site. After that debugging worked fine.

blocks|key|286423|text|我曾经遇到过同样的问题，但它是在Visual+studios自己的web开发服务器上，而不是在IIS.The上解决的是取消选中项目属性下Web选项卡中的选项，将服务器设置应用到所有用户(存储在项目文件中).Hope它将节省一些人的宝贵时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|286424|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had faced the same problem but it was on Visual studios's own web development server instead of IIS.The get around is to uncheck the option in Web tab under project properties, Apply server settings to all users(store in project file.).Hope it will save some one's valuable time.

blocks|key|3213333|text|检查IIS上的网站是否未停止。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3213334|我修复了它，让我的网站运行起来。:D|3213335|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Check if your website on IIS is not stop. 

I fixed it put my web site to run. :D

blocks|key|3213363|text|我也有同样的问题。上面的所有答案对我来说都不起作用。解决方案是手动删除bin和obj文件夹。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3213364|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same problem.
All the answers above did not work for me.
The solution was to delete the bin and obj folder manually.

blocks|key|3213368|text|我也发现了这个问题，但它与@Kirk解释的内容和URL重写非常相似。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3213369|在我的例子中，有人已经将此更改签入到MVC项目的web.config文件中：|3213370|<system.webServer>
++++<security>
++++++++<requestFiltering>
++++++++++++<fileExtensions>
++++++++++++++++<add+fileExtension=".aspx"+allowed="false"+/>
++++++++++++</fileExtensions>
++++++++</requestFiltering>
++++</security>
</system.webServer>|code-block|syntax|javascript|3213371|由于web服务器上不允许使用.aspx文件扩展名，因此/debugattach.aspx+URL被拒绝，从而阻止调试器运行。一旦我删除了这个配置，它又可以工作了。|offset|length|style|CODE|3213372|entityMap^0|0|0|0|R|H|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@$K|U|L|V|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I found this issue too but it was most similar to what @Kirk explained and URL rewriting.

In my case someone had checked in this change to the web.config file for a MVC project:

<pre><code>&lt;system.webServer&gt;
 &lt;security&gt;
 &lt;requestFiltering&gt;
 &lt;fileExtensions&gt;
 &lt;add fileExtension=".aspx" allowed="false" /&gt;
 &lt;/fileExtensions&gt;
 &lt;/requestFiltering&gt;
 &lt;/security&gt;
&lt;/system.webServer&gt;
</code></pre>

Because .aspx file extensions were not allowed on the web server, the <code>/debugattach.aspx</code> URL was denied, preventing the debugger from running. Once I removed this configuration it worked again.

blocks|key|285505|text|请检查应用程序池。如果它停止了。重新启动它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|285506|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Plase check application pool. if it is stoped. restart it.

blocks|key|288861|text|不使用IIS，只需使用IIS+Express即可。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|288862|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Instead of using the IIS, just use IIS Express.

blocks|key|3213395|text|当我在Visual+Studio中创建应用程序，然后在属性中创建用于本地IIS的虚拟目录时，我也遇到了同样的问题。如果有人有这个错误，那是因为VS在错误的AppPool下创建应用程序，即在不符合您需求的AppPool下创建应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3213396|如果是这种情况，转到IIS管理器，选择应用程序，转到基本设置并更改应用程序的AppPool，您就可以开始工作了。|3213397|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had the same problem when I created application in Visual Studio, and then in properties created virtual directory for use with local IIS. If someone has this error it is because VS creates application under wrong AppPool, i.e. under AppPool which doesn't suit your needs. 
If this is the case, go to IIS Manager, select App, Go to Basic settings and change AppPool for App and you are good to go.

blocks|key|288941|text|如果应用程序池在重新启动时遇到问题或根本不想重新启动，请验证windows是否在ASP.NET+v4.0或其他应用程序池上进行了最新更新。这就是发生在我身上的事情。我只需重新启动我的计算机，然后重新启动ASP.NET+v4.0应用程序池，一切都再次正常工作！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|288942|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If App Pool has trouble restarting or simply doesn't want to restart, verify if windows made recent update on ASP.NET v4.0 or other App Pool. That is what happend in my case. I simply restarted my computer, then restarted ASP.NET v4.0 App Pool and everything was working again!

blocks|key|283333|text|我也遇到了同样的问题，我发现这是因为我在结束标记后的Web.config中错误地输入了一个字符。我的Web.config在最后看起来是这样的：</section>h。"h“是结束标记后的额外字符。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|283334|entityMap^0|Q|A|1E|A|1Z|B|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

I had the same issue and found that it was caused because i had a character mistakenly typed in my <code>Web.config</code> after the end tag. My <code>Web.config</code> looked like this right at the end: <code>&lt;/section&gt;h</code>. The "h" was an extra character after the closing tag.

blocks|key|3213572|text|我最近收到了同样的错误，在我的例子中，结果是有重复的MIME类型。我最近添加了两个最初没有出现在列表中的。IIS允许我添加它们，只有当我决定作为诊断过程的一部分再次检查站点的MIME类型时，IIS中也出现了错误。它引用了web.config中的重复项。当我返回到web.config文件时，我注意到添加了一个名为的新部分，其中包括两个最近添加的MIME类型。删除了那部分，生活又变好了！希望这能帮助那些没有解决这个问题的人，并提供任何其他建议。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3213573|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I got this same error recently and in my case it turned out that there were duplicate MIME types. I had recently added two that didn't show up in the list initially. IIS let me add them and it was only when I decided to check the MIME types for the site again as part of my diagnostic process that I got an error in IIS as well. It referenced duplicates in web.config. Once I went back into the web.config file I noticed that a new section called had been added, which included the two recently-added MIME types. Deleted that section and life is good again! Hoping this may help others who haven't managed to fix the issue with any of the other suggestions.

blocks|key|289001|text|我遇到了这个问题，并最终意识到我的ASP.net没有正确注册到IIS。当在Visual+Studio之前安装IIS服务器时，可能会发生这种情况。要解决此问题，请使用命令aspnet_regiis+-i可在link中找到详细信息|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|289002|entityMap|0|LINK|mutability|MUTABLE|url|https://msdn.microsoft.com/en-us/library/k6h9cz8h%2528v=vs.140%2529.aspx^0|2C|G|2U|4|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@$9|Q|A|R|1|S]]|E|$]]|$1|F|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

I had this problem and eventually realized that I ASP.net is not registered properly with IIS. This can happen when IIS server is installed before Visual Studio. To fix this issue, use the command aspnet_regiis -i
Further information can be found in the <a href="https://msdn.microsoft.com/en-us/library/k6h9cz8h%28v=vs.140%29.aspx" rel="nofollow">link</a>

blocks|key|3213685|text|我在VS2012中得到了同样的错误信息，但没有以管理员身份运行。当我以管理员身份运行应用程序时，我得到了一条不同的、稍微更有帮助的消息(我能够弄清楚)。HTH|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3213686|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I was getting the same error message in VS 2012, but was not running as Administrator. When I ran the app as administrator, I got a different and slightly more helpful message (which I was able to figure out). HTH

blocks|key|283478|text|也有同样的问题。如果您在IIS上安装了SSL证书，并且尝试从Visual+Studio对其进行调试，则需要将IIS上的应用程序设置为忽略证书。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|283479|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

had same issue. If you have SSL certificate installed on IIS and if you are trying to debug it from Visual Studio then you need to set your application on IIS to ignore certificate.

blocks|key|283481|text|在打开所有IIS窗口功能时，Windows+10也存在同样的问题。已切换到Windows+8.1，但再次出现问题。根目录位于网站名称"http://MySite.local“中(与操作系统版本无关)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|283482|解决方案很简单|283483|使用ip绑定编辑%25SystemRoot%25\System32\drivers\etc\|style|CODE|283484|Add行中的|unordered-list-item|283485|文件：127.0.0.1+MySite.local|283486|283487|283488|entityMap|0|LINK|mutability|MUTABLE|url|http://mysite.local/^0|1V|J|0|0|0|8|Y|0|0|3|M|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|13|8|@$A|14|B|15|H|I]]|9|@]|C|$]]|$1|J|3|K|5|L|7|16|8|@]|9|@]|C|$]]|$1|M|3|N|5|L|7|17|8|@$A|18|B|19|H|I]]|9|@]|C|$]]|$1|O|3|-4|5|6|7|1A|8|@]|9|@]|C|$]]|$1|P|3|-4|5|6|7|1B|8|@]|9|@]|C|$]]|$1|Q|3|-4|5|6|7|1C|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]]]

Had the same problem with Windows 10 when turned on all IIS windows features. Switched to Windows 8.1 and got problem again. 
The root was in web site name "<a href="http://MySite.local" rel="nofollow">http://MySite.local</a>" (not related to OS version). 

And solution is simple 

<ul>
<li>Edit hosts file in <code>%SystemRoot%\System32\drivers\etc\</code></li>
<li>Add line with ip binding: <code>127.0.0.1 MySite.local</code></li>
</ul>

I am running Visual Studio 2010 (as Admin), IIS 7 on Windows 7 x64.
I am able to run the ASP.NET web site in IIS 7 without debugging just fine, but when I press F5 to debug it, I get:

<blockquote>
 Unable to start debugging on the web server. Could not start ASP.NET debugging. More information may be available by starting the project without debugging.
</blockquote>

Unfortunately the help link is not helping me much and leads down a heck of a large tree of things.

I checked the following:

<ul>
<li>Security requirements — I don't recall having to do anything special before. The worker process in IIS7 is w3wp.exe. It says that if it's running as ASPNET or NETWORK SERVICE I must have Administrator privileges to debug it. How do I find out if I need to change something here?</li>
<li>Web site Property Pages > Start Options > Debuggers > ASP.NET is checked.
Use custom server is set to the URL of the site (which works fine without debugging).</li>
<li>Debugging is enabled in <code>web.config</code>.</li>
<li>Application is using ASP.NET 3.5 (I want to move to 4.0 eventually but I have some migration to deal with).</li>
<li>Application pool: Classing .NET AppPool (also tried DefaultAppPool).</li>
</ul>

Any ideas where I can check next?

Surely it shouldn't be that hard to install IIS, VS, create a web site, and start testing it?

Thanks in advance.

Unable to start debugging on the web server. Could not start ASP.NET debugging VS 2010, II7, Win 7 x64

Visual Studio

身份验证

文件系统

服务器

调试器

Windows

我在Windows7 x64上运行Visual Studio2010(作为管理员)和IIS7。我可以在不调试的情况下在IIS7中运行ASP.NET网站，但是当我按F5进行调试时，我得到：无法在web服务器上启动调试。无法启动ASP.NET调试。通过启动项目而不进行调试，可以获得更多信息。不幸的是，帮助链接对我帮助不大，...

问无法在web服务器上启动调试。无法启动ASP.NET调试VS 2010、II7、Win 7 x64
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法在web服务器上启动调试。无法启动ASP.NET调试VS 2010、II7、Win 7 x64EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法在web服务器上启动调试。无法启动ASP.NET调试VS 2010、II7、Win 7 x64
EN