How to clear Error " exe has encountered a problem and needs to close. We are sorry for the inconvenience. "

Question

1.00/5 (2 votes)

See more:

Dear All,
.net application run in another system not run error occur
" ElsFigMov.exe has encountered a problem and needs to close. We are sorry for the inconvenience. "

install .net framework 4.0 but not run

How to clear error pl help me ........

Regards
E.Veeraperumal

Posted 18-Apr-14 18:52pm

Member 10420597

Updated 18-Apr-14 18:53pm

v2

Add a Solution

Comments

Sergey Alexandrovich Kryukov 19-Apr-14 1:03am

No information; how can you hope for some help?
—SA

Richard MacCutchan 19-Apr-14 4:19am

As Sergey says, there is not enough information. You need to check that all prerequisite libraries for your application are installed on the target system. You should also include some logging in your program to help you discover where it fails.

1 solution

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)

Dave Kreskowiak · Answer 1 · 2014-04-19T04:18:00

Solution 1

Fix the bug in your code that's causing the problem. Simple, isn't it?

With the complete lack of any information about what your application is doing, what it was doing at the time of the error, or anything else of use, this is about the best answer you could possibly hope for.

Posted 19-Apr-14 4:18am

Dave Kreskowiak