How to solve unhandled exception using C#

Question

1.00/5 (2 votes)

See more:

.NET2.0

Hi,
I often use try catch block to catch errors but I don't know why my application crashes by displaying errors as follows.

Application has encountered a problem and needs to close

Moreover My application consists of many forms including Program.cs which is the starting class. Then Another Form (FrmMain) gets launched from Program.cs.

FrmMain opens order details and opens many forms.

So how to find the root cause for these type of errors.

Posted 15-May-15 5:08am

KUMAR619

Add a Solution

Comments

Richard MacCutchan 15-May-15 11:33am

This is difficult to answer. The only real way is to do more tests and use your debugger to try and isolate what is happening. You should also check the event logs to see if they have any information that helps.

John C Rayan 15-May-15 11:37am

From the error it looks like you are calling unmanaged code that throws an error and you application crashes. It is really difficult to say unless we run your program.

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

David Knechtges · Answer 1 · 2015-05-15T05:41:00

Solution 2

Do what we did. Write a handler for unhandled exceptions and write the exception and trace log out to either a file or email it to yourself.

That will give you the exception, module name, and line number where it occurred.

Posted 15-May-15 5:41am

David Knechtges

Comments

KUMAR619 20-May-15 4:12am

Can you help to create handler for undhandled exceptions

OriginalGriff · Answer 2 · 2015-05-15T05:32:00

There is no one root cause for these errors - except poor programming - exception happen when there is a problem which means that some operation cannot be completed.

That operation could be as simple as a "divide by zero", or a "null reference" - or it could be buried deep in a bit of SQL that your code asks SQL Server to execute.

We can't tell. You will have to look at each one individually, and work out what kind of exception it is, and then start looking at your code to work out why.

Sorry - but we can't do that for you.