Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / CLR / April 2008

Tip: Looking for answers? Try searching our database.

.NET Runtime 2.0 Error Reporting , Event ID:5000 Application Crash

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Shahbaz - 18 Apr 2008 07:00 GMT
I have running Desktop Network Application based on .NET Framework 2.0 ,
Visual Studio 2005 and Sql Server 2000 /2005. It suddenly exits while running
without any prior notice. After I look at the Event Log in Windows 2003
Server, found the following Error log. It only happens on the client side, I
am not  unable to debug the situation which causes the application to crash.
How do i know the exact cause of the crash? kindly help me out.

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date:  3/20/2008
Time:  1:50:14 PM
User:  N/A
Computer: ALL
Description:
EventType clr20r3, P1 servicemain.exe, P2 1.0.0.0, P3 47bae0cd, P4
cat.cass.sockets, P5 1.0.0.0, P6 478202aa, P7 a, P8 3b, P9
system.argumentexception, P10 NIL.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Misbah Arefin - 21 Apr 2008 00:09 GMT
This problem occurs because the default policy for unhandled exceptions has
changed in the .NET Framework 2.0. By default, the policy for unhandled
exceptions is to end the process.

In the Microsoft .NET Framework 1.1 and in the Microsoft .NET Framework 1.0,
unhandled exceptions on managed threads were ignored. Unless you attached a
debugger to catch the exception, you would not realize that anything was
wrong.

When an unhandled exception is thrown in .NET Framework 2.0, the application
unexpectedly quits.

The eventlog entry you mentioned is usually followed by another entry with
the details of the unhadled exception.

Signature

Misbah Arefin
https://mcp.support.microsoft.com/profile/MISBAH.AREFIN
http://www.linkedin.com/in/misbaharefin

> I have running Desktop Network Application based on .NET Framework 2.0 ,
> Visual Studio 2005 and Sql Server 2000 /2005. It suddenly exits while running
[quoted text clipped - 17 lines]
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.