How to Disable Crash Report

[MartinP]

I have a program (executable) created under LabVIEW 2011 SP1.

Every time the program is stopped and closed, a LabVIEW Crash-report is created.

Nothing is wrong in the program, and when restarted everything works fine.

The Crash-report doesn't tell much, NI say it could indicate that something is wrong on the computer with some other software, for example the anti-virus program.

All this crash-report does is frustrating the customer using the software.

I have asked NI how to turn off the Crash-report functionality, but has not received any answer after a week.

Does anybody know how to do this ?        :mansurprised:

(Running the source code does not generate any errors or crash reports.)

Martin

[Norbert_B]

Martin,

errors like this can have different sources. One source might be an invalid entry for the <exe>.ini file.

So please remove this file (backup) and start the exe. It will recreate a default ini file.

If the error dialog still occurs, you might want to try the following keys in the ini-file:

NIERShowNonFatalDialogOnExit=False
NIERNonFatalAutoSend=false

Please note that it is recommended to dig in for the real source of the error dialog and address it. The above is only a workaround which should remove the dialog.

hope this helps,

Norbert

[billko]

---

@Norbert_B wrote:

Martin,

errors like this can have different sources. One source might be an invalid entry for the <exe>.ini file.

So please remove this file (backup) and start the exe. It will recreate a default ini file.

If the error dialog still occurs, you might want to try the following keys in the ini-file:

NIERShowNonFatalDialogOnExit=False
NIERNonFatalAutoSend=false

Please note that it is recommended to dig in for the real source of the error dialog and address it. The above is only a workaround which should remove the dialog.

hope this helps,

Norbert

---

I agree.  It's like treating a broken leg with painkillers - with the exception that a borken leg will porbably heal eventually.  Obviously there IS something wrong, or an error report wouldn't be generated.  It just doesn't appear to be critical - yet.

[DavidBoyd]

I saw Martin's query on Info-LabVIEW, then came here.  Thanks, Norbert, for the preference tokens - first time I recall seeing these.

I'm interested, because my current development environment is generally 2011SP1 - and it generates a crash report on every exit.  Fortunately, I don't think I have that problem with my built apps.

Without any intention of ruffling feathers, I need to say this:

Letting the NIER do its thing is probably giving the LabVIEW development team lots of good field data.  (But...)

For any given user, it is probably of very limited use to say "dig in for the real source of the error dialog and address it".

In my own case, I remain clueless about what's wrong with my development environment.  I suppose I could revert to a plain-vanilla labview.ini file (I now make it a practice of saving one right after each version install), then slowly replace tokens until the crash dialog reoccurs.  But what if reverting to vanilla doesn't fix the problem in the first place?

Best regards,

Dave

[billko]

---

@DavidBoyd wrote:

<snip>

For any given user, it is probably of very limited use to say "dig in for the real source of the error dialog and address it".

<snip>

---

I'm sure that Norbert didn't mean that the user should take on the error by himself.  But the OP still needs to find out what's causing the error - any way possible, including working with an NI Engineer - and not to just shrug it off.  You don't fix a problem by ignoring it just because there doesn't APPEAR to be any detrimental effects.  That's rather like ignoring a constant blue screen and rebooting with no "apparent" side effects.  In the mean time, your disk is slowly becoming corrupt, and one day a sector belonging to an important system file is corrupt and you can't boot into your operating system,.

[Nitin_T]

With the introduction of NIER in LV 2011, it is now possible to catch crashes that happen when LabVIEW exits. Many of these crashes have to do with LV, one of its modules, toolkits, drivers etc. not shutting down correctly, which may or may not be related to the application that was running (as in, it could be an issue with the LV Editor or RTE Environment). A certain chunk of these exit-crashes have been addressed in later versions of LV. 

If you are concerned about a particular crash, please do contact NI support. The Applications Engineers should escalate the issue and someone from LV R&D will be able to analyze the crash dumps and say what's the specific cause. 

Martin: To disable NIER for the built application that your customer is using, please add the following token to the app's ini file NIER=False. This and other details about disabling NIER can be found in the following KnowledgeBase: How do I disable NI Error Reporting (NIER)?

- Nitin