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.

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.


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


"Shahbaz" wrote:

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.


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


"Shahbaz" wrote:

Probably you need to see the exception details. Check comment at http://malcan.com/EN/Lists/Tips%20and%20tricks/DispForm.aspx?ID=18



MisbahArefi wrote:

This problem occurs because the default policy for unhandled exceptions has
20-kwi-08

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.


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


"Shahbaz" wrote:

Previous Posts In This Thread:

EggHeadCafe - Software Developer Portal of Choice
SharePoint Application Page with Custom Controls
http://www.eggheadcafe.com/tutorials/aspnet/2145201e-00aa-4877-b5f7-cf150d7f0c5f/sharepoint-application-pa.aspx