如何解决 "Unable to start debugging" ?

来源:互联网 发布:社保网络认证的意义 编辑:程序博客网 时间:2024/06/06 17:54

 

在VS 2003 中几次出现如下画面,但一直没有很好的解决。

 

 

如何解决呢?收集了一些文档,终于在最后成功解决!

If all this doesn’t succeed, try using DebuggerDiagnostics.exe. You can install it fromhttp://download.microsoft.com/download/a/6/f/a6f1de85-7284-4c97-9ddd-6f18000f5848/DebuggerDiagnostics.msi.                                   

 

Yes  成功: 在下载并运行了 DebuggerDiagnositics.exe 之后,终于能够正运行,不再出错!

 

 

解决方法汇总如下:

 

Error: Unable to Start Debugging on the Web Server(from MSDN)

Posted on 2008-07-09 10:18 落花人独立 阅读(1160)评论(0)编辑收藏

当试图对运行在 Web 服务器上的应用程序进行调试时,有时可能会得到此错误信息:
Unable to start debugging on the Web server
如果你得到的错误信息是比这个更长的消息,这个主题下面的子主题对其做了说明.

如果你遇到了这个错误,有几点是需要被考虑的.第一就是things to check,然后基于你的机器的硬件和软件配置来考虑其它的项目.
    

·Things to Check

·Web Applications on Remote Servers

·Web Applications Stored in Visual SourceSafe and Using FrontPage Server Extensions

·Manually Attaching

·Debug Request Could Not Be Processed By the Server Due to Invalid Syntax

Things to Check

Try checking the following things:

试着做如下检查:

·Review the procedures for setting up ASP.NET or ATL Server. For more information seeGetting Ready to Debug ASP.NET Applications.
回顾安装ASP.NET或者ATL Server的过程.更多信息参考Getting Ready to Debug ASP.NET Applications.

·Do you have the necessary access privileges for debugging? For more information see theSecurity Requirements section inASP.NET Debugging: System Requirements.

你是否拥调试的权限?更多信息参考ASP.NET Debugging: System Requirements的安全需求部分.

·Are you running a version of Windows that allows the Visual Studio debugger to automatically attach to a Web application? If not, you need to launch the application without debugging and manually attach to it. (For more information, seeManually Attaching and ASP.NET Debugging: System Requirements.)

你在使用允许Visual Studio 调试器自动的attach to a Web application(绑定Web应用程序)的Windows版本么?如果不是,你需要以不调试的方式启动应用程序并且手工的绑定它.(更多信息参考手工绑定和ASP.NET Debugging: System Requirements部分)

·Does your Web application have a Web.config file?

Web应用程序是否有Web.config文件?

·          

·      Does the Web.config file enable debug mode by setting the debug attribute to true? For more information, seeHow to: Enable Debugging for ASP.NET Applications.

在Web.config文件中是否设置了debug="true"?更多信息参考....

·      Does the Web.config file contain any syntax errors? You can check for syntax errors by running the Web application without debugging. (From the Debug menu, chooseStart Without Debugging.) If there are syntax errors in Web.config, detailed information will be displayed.

Web.config文件中有无语法错误?通过F5运行可以检查到语法错误.如果有语法错误,它的详细信息会会显示出来.

·Did you create the project by specifying a specific IP address (100.20.300.400, for example)? Debugging a Web server requires NTLM authentication. By default, IP addresses are assumed to be part of the Internet, and NTLM authentication is not done over the Internet. To correct this problem:
是不是创建工程的时候指定了IP地址?在Web服务器上调试需要NTLM授权.默认情况下,IP地址作为Internet的一部分,但是NTLM授权不能通过Internet来进行.更正这个问题的办法如下:(有这个问题的时候会提示:Unable to start debugging on the web server.The project is using a web site that is configured with IP adress....)

·      When creating the project, specify the name of the machine on your intranet.

创建工程的时候指定intranet中的你的主机名字.

-or-

·      Add the IP address (http://100.20.300.400) to the list of trusted sites on your computer. (From the Internet Explorer Tools menu, choose Internet Options, and then select the Security tab).

将IP地址加入你的计算机上的信任站点.(从IE 浏览器中的工具菜单中选择选项->安全).

Are the necessary extensions registered on the server machine? If not, re-register ASP.NET as described in the procedure below.

必要的扩展是否在服务器上注册了?如果没有,重新注册ASP.NET.

 

 

 

 转自:http://blogs.msdn.com/b/greggm/archive/2004/04/16/114828.aspx

Diagnosing 'The debugger is not properly installed'

greggm

16 Apr 2004 12:30 PM

·         Comments 58

One of the error codes that we included in the VS.NET 2002 and 2003 debuggers is:

The debugger is not properly installed.  Run setup to install or repair the debugger.

Diagnosing this is much harder then it should be (more on this later). For now lets talk about trying to figure out what’s going wrong.

First step, you should follow the instructions. Most of the time this is going to work:

  • Go to Start->Control Panel->Add or Remove Programs->Microsoft Visual Studio.NET <whatever>
  • Click Change/Remove
  • Repair your installation

If that doesn’t work, try reinstalling the .NET Framework debugging services:

  • Start command prompt
  • cd /d %windir%\ Microsoft.NET\Framework\<version>
  • regsvr32.exe mscordbi.dll                                                                                                   X 不成功

Another known reason for this error is that oleaut32.dll isn’t registered:

  • Start command prompt
  • cd /d %windir%\system32
  • regsvr32.exe oleaut32.dll                                                                                                    X 不成功

Also try manually reregistering mdm.exe [updated 4/28/2004]:

  • Start command prompt
  • %CommonProgramFiles%\Microsoft Shared\VS7Debug\mdm.exe" /regserver                    X 不成功

If all this doesn’t succeed, try using DebuggerDiagnostics.exe. You can install it fromhttp://download.microsoft.com/download/a/6/f/a6f1de85-7284-4c97-9ddd-6f18000f5848/DebuggerDiagnostics.msi. Here is how to interpret the output:                                            

 

Yes  成功: 在下载并运行了 DebuggerDiagnositics.exe 之后,终于能够正运行,不再出错!

 

[Updated on 8/17/2004] If you are getting failures from the 'UseOleAut32' part of DebuggerDiagnostics.exe (see bellow), then you have a broken installation of oleaut32.dll. If you haven't already done so, try 'regsvr32 oleaut32.dll'. If the problem persists, then download and run OleAutClean.exe. After that has finished, you will need to run 'regsrv32 oleaut32.dll'. Example Failure:

Begin 'UseOleAut32(spMachine)'
    QueryInterface failed.
    MarshalConnectionPointContainer() = '8007007e'
Result of 'UseOleAut32(spMachine)' is '8007007e'

For anything else, check the comments of this post. They might already have the solution, if they don't add your commentshere. I guess you can't leave comments on really old posts.