CLR错误:8007000b [英] CLR Error: 8007000b

问题描述

我有一台客户端计算机抛出"CLR错误": 8007000b "尝试启动任何VB.NET 2003应用程序时出现错误消息.我尝试了不同的方法，但似乎无法解决问题.

尝试过的事情列表

1.卸载并重新安装.NetFramework 1.1，包括Service Pack和修补程序.尝试过此次数.

请注意，.NetFramework安装正常，没有任何错误.

此外，如果运行Microsoft .Net Framework 1.1向导，则会显示相同的错误消息.

2.禁用Symantec Endpoint Protection，然后重新安装.NetFramework 1.1和应用程序.

3.遵循Aaron Stebner的WebLog上的文章中给出的指示.虽然.NetFramwork的设置没有失败，但是我尝试过(例如，删除URTTemp文件夹并检查注册表项等).

4.进行了完整的系统扫描以查看计算机上是否存在任何病毒.

客户端的计算机是带有Windows XP Pro SP2的新型Dell笔记本电脑.这是我们的第一个遇到此问题的客户.

希望有人可以帮助我.

解决方案

AnjaliP，

根据问题和CLR错误信息，我想为您提供以下两条建议:

1. 8007000b" error message when attempting to launch any VB.NET 2003 application.  I have tried different things but does not seem to solve the problem. 

 

List of things tried

1. Uninstall and reinstall .NetFramework 1.1,  including service pack and hotfixes.  Tried this number of times.

Please note that .NetFramework installation goes fine without any errors.

Also, if run the Microsoft .Net Framework 1.1 wizards the same error message is displayed.

2. Disabling the Symantec Endpoint Protection and then reinstalling the  .NetFramework 1.1 and application.

3. Followed the direction given in the article on Aaron Stebner's WebLog.  Though the setup of .NetFramwork was not failing I tried(e.g. deleting the URTTemp folder and checking the registry entries etc.)

4.  Did a full system scan to see if any virus was present on the machine.

 

The client's machine is new dell laptop with Windows XP Pro SP2.  This is our first client who is having this problem.

 

Hope someone can help me with this. 

解决方案

AnjaliP,

 

According to the question and CLR error information, I would like to provide you the following two pieces of advice:

 

1. Troubleshooting 1935 and 2908 errors during installation

In general, this error means that Windows Installer encountered an error while trying to install assemblies to the Global Assembly Cache (GAC) or the Win32 GAC (WinSxS).  This error is considered fatal and causes setup to fail and initiate rollback.

 

If the setup is run in UI mode, the user will see a message box indicating that a 1935 error occurred, and it will list the HRESULT and the Windows Installer component GUID of the assembly that caused the error.  If the setup is run in silent mode, the user will see no visible error.  In both cases, more detailed information about the error can be found in the Windows Installer verbose log file.

 

2. You can also install .NET Framework SDK and use CLR Debugger (DbgCLR.exe) that provides debugging services with a graphical interface to help application developers find and fix bugs in programs that target the common language runtime.

The following article can help you to use this tool better:

 

Improve Your Understanding of .NET Internals by Building a Debugger for Managed Code

 

With the release of .NET, the Microsoft scripting strategy has evolved. Script engines can now compile or interpret code for the Microsoft common language runtime (CLR) instead of integrating debugging capabilities directly into apps through Active Scripting. With that change comes a new set of published services for including debugging functionality in a custom host application. You'll see how to use the debugging services published in the .NET Framework to create a full-featured CLR debugger that allows you to set breakpoints, view call stacks, browse variables, view processes, enumerate threads, and perform other important debugging tasks.

 

Hope that can provide you some idea and good luck.

这篇关于CLR错误:8007000b的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！