如何解决 "Unable to start debugging" ?

 

在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 in ASP.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.

 

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 1
    评论
### 回答1: 您好,针对您的问题:vscodeunabletostartdebugging如何解决,我可以为您提供以下解决方法: 1. 检查代码:请确保您的代码没有语法错误或其他问题,这可能会导致调试失败。 2. 检查配置:请确保您的调试配置正确,例如启动文件路径和调试器类型等。 3. 检查插件:如果您正在使用调试插件,请检查插件是否最新版本,并尝试禁用其他插件以查看是否与其冲突。 4. 检查运行环境:请确保您的运行环境正确安装并配置,例如您的编程语言版本和相关依赖项。 如果以上方法都不能解决问题,您可以尝试重装VS Code,并重新配置调试器。 希望这些方法能够帮助您解决问题! ### 回答2: 要解决VSCode无法启动调试的问题,可以尝试以下几种方法。 首先,确保已正确配置调试器。在VSCode的调试面板中,选择合适的调试器,并确保已正确配置调试器的名称、程序入口文件以及调试选项等。 其次,检查调试配置文件是否正确。在项目的根目录下,找到名为launch.json的调试配置文件,并确保其中的配置项正确。可以检查调试器的路径、程序参数、环境变量等配置是否正确。 另外,确认是否安装了必需的调试插件。在VSCode的扩展面板中,搜索并安装对应的调试插件,例如针对特定语言的调试插件或针对特定调试器的插件。 此外,检查代码是否有错误或问题。如果代码中存在语法错误、断点设置错误或程序逻辑问题等,可能会导致无法启动调试。确保代码正确无误,或者尝试在没有错误的代码段上进行调试。 最后,还可以尝试重启VSCode或重启电脑。有时候VSCode可能会出现一些临时问题,导致无法启动调试。通过重新启动软件或电脑,可以尝试解决一些临时的问题。 如果以上方法仍然无法解决问题,可以尝试查看VSCode的错误日志或在线搜索相关错误信息,以获得更多的帮助和解决方案。 ### 回答3: 解决VSCode无法启动调试的问题可以按照以下步骤进行操作: 1. 确保已正确安装并配置了调试器插件,例如对于JavaScript的调试,需要安装`Debugger for Chrome`插件。 2. 检查VSCode的配置文件`.vscode`中的`launch.json`文件,该文件用于配置调试器。 3. 确保`launch.json`文件中的`configurations`字段设置正确。例如,对于JavaScript调试,检查`launch.json`中是否有类似以下配置: ``` { "version": "0.2.0", "configurations": [ { "type": "chrome", "request": "launch", "name": "Launch Chrome", "url": "http://localhost:3000", "webRoot": "${workspaceFolder}" } ] } ``` 4. 检查调试器是否使用了正确的URL和端口号。根据实际情况,可能需要修改`launch.json`中的`url`字段,确保URL与你的项目的URL匹配。 5. 确保项目已正确启动。如果调试器无法连接到正在运行的项目,那么调试也无法启动。因此,请确保你的项目已正确启动并正在运行。 6. 尝试重启VSCode。有时候简单的重启可以解决一些问题。 如果以上步骤都无法解决问题,可以尝试从VSCode插件市场卸载并重新安装调试器插件。另外,检查VSCode的版本是否为最新版本也是一种解决问题的方法。如果问题依然存在,可以在相关开发社区或论坛上寻求帮助,其他开发者可能会提供更具体的解决方案。
评论 1
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值