网络运行时错误：.NET运行库2.0错误 - 事件ID：1000坠毁我的程序。是什么原因造成的？ [英] Net Runtime Bug : .NET Runtime 2.0 Error - Event Id: 1000 Crashed my program. What caused this?
问题描述
我有一个已经运行24/7超过2个星期了一个新的方案，但昨晚它崩溃/下去，在我的log4net的文件中没有致命日志例外......这个过程似乎已被杀害成才。 ......当我看着在Windows事件查看器应用程序日志它包含了程序的过程说.NET运行库2.0错误类型的错误：错误事件ID：1000
I have a new program which has been running 24/7 for over 2 weeks now but last night it crash/went down with no Fatal log exception in my log4net file ...the process appears to have been killed by someting .... and when I looked in the Windows Event Viewer Application log it contained an error for the programs process saying '.NET Runtime 2.0 Error' Type: Error EventID: 1000.
这似乎是一个.NET运行时故障/错误，并没有任何与我的code。
This appears to be a .Net runtime failure/bug and has nothing to do with my code.
有谁知道是什么原因造成的？是否有.NET运行时解决？
Does anyone know what caused this? Is there a .Net runtime fix?
/我在Window Server 2003的虚拟切片运行.NET 3.5。
/I'm running .Net 3.5 on a Window Server 2003 vm slice.
在此先感谢。
编辑：
下面的完整的事件的描述。还有的是周围没有任何活动几个小时，有INFO级别的错误不是这样的。
Full event description below. There's were no events around it for hours and there were Info level not Error like this one.
来源：.NET运行库2.0错误 类型：错误 事件ID：1000
Source: .NET Runtime 2.0 Error Type: Error Event Id: 1000
事件日志说明： 错误的应用程序CompanyName.AppName.exe，0.0.0.0版本，印花税4ca5d33d，错误模块的Mscorwks.dll，2.0.50727.3607版本，印花税4add5446，调试？ 0，错误地址0x0010724e。
Event log description: Faulting application CompanyName.AppName.exe, version 0.0.0.0, stamp 4ca5d33d, faulting module mscorwks.dll, version 2.0.50727.3607, stamp 4add5446, debug? 0, fault address 0x0010724e.
有关详细信息，请参阅帮助和支持中心 http://go.microsoft.com/ fwlink / events.asp 。
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
推荐答案
由于你没有得到在崩溃时的任何有用的信息，另一种方法是将一个调试器附加到崩溃 EXE 。有两种方法，我建议：
As you are not getting any useful information at the time of the crash, an alternative approach is to attach a debugger to the crashing EXE. There are two ways I suggest:
使用Visual Studio
如果您已经安装在同一台PC /服务器的崩溃的应用程序在Visual Studio中，连接Visual Studio中的 EXE ，而它的运行。下面是关于如何做到这一点的介绍：
If you have Visual Studio installed on the same PC/server as the crashing app, attach Visual Studio to the EXE whilst it's running. Here's an intro on how to do this:
http://msdn.microsoft.com/en-us/library/ c6wf8e4z.aspx
使用的WinDbg
这是一个非常低的水平，功能强大，调试器的Windows。这肯定会帮助你解决问题。但是，在如何让使用它开始陡峭的学习曲线。在.NET框架提供了 DLL 的 SOS.DLL （在Ç发现： \的Windows \ ...... 系统文件夹），其中包含了您可以使用的WinDbg来分析.NET应用程序中的许多命令。这些措施包括上市线程堆栈和显示异常信息。
This is a very low-level, and powerful, debugger for Windows. This could certainly help you with your problem. However, there is a steep learning curve in how to get started in using it. The .NET framework comes with a DLL named SOS.DLL (found in the C:\Windows\...... system folder) which contains many commands that you can use in WinDbg to analyse a .NET application. These include listing thread stack and displaying exception information.
信息如何.NET问题的WinDbg调试一个很好的来源是
A very good source of information on how to debug .NET issues with WinDbg is
有如何调试问题，如
的http://blogs.msdn.com/b/tess/archive/2008/02/11/net-debugging-demos-lab-2-crash-review.aspx
您可以从下载的WinDbg：
You can download WinDbg from:
- 在32位版本 http://www.microsoft.com/whdc/devtools/debugging/installx86 .mspx＃E3
- 在64位版本 http://www.microsoft.com/whdc/devtools/debugging/install64bit。 MSPX -
- 32bit version http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx#E3
- 64bit version http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx-
我会强烈建议在Visual Studio的方式，由于它的简单性。然而，迄今为止最强大的方式来调试您的应用程序是使用WinDbg，但它可以恐吓的初级用户。
I would highly recommend the Visual Studio approach, due to its simplicity. However, by far the most powerful way to debug your app is to use WinDbg, but it can be intimidating for first time users.
编辑： 下面是可能会使用其他链接：
Here's another link that might be of use:
<一个href="http://social.msdn.microsoft.com/Forums/en-US/netfxbcl/thread/ebd10d1f-902b-4a95-ba42-e87c4f817097" rel="nofollow">http://social.msdn.microsoft.com/Forums/en-US/netfxbcl/thread/ebd10d1f-902b-4a95-ba42-e87c4f817097
这篇关于网络运行时错误：.NET运行库2.0错误 - 事件ID：1000坠毁我的程序。是什么原因造成的？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
