LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

What causes "An error occurred while sending this report" after LabVIEW crash

Sometimes* when the LabVIEW IDE crashes we are shown a dialogue message like below:

1.png

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

After selecting "Send", we are shown a "Sending Report" window like below.

Petru_Tarabuta_1-1718308919487.png

 

After a few seconds (less than a minute) I am sometimes shown the following error. Other times the report is sent successfully, from the same computer, on the same network.

Petru_Tarabuta_0-1718308736175.png

 

Questions

  • Does anyone know what causes the crash report not to be sent?
  • Does anyone know why this behaviour happens sometimes, but other times crash reports are sent successfully? Has anyone else faced the same intermittent behaviour?
  • Are there any logs that can shed information on why the crash report could not be sent?
  • *Other times LabVIEW crashes but the LabVIEW crash report window does not show at all.
    • Is there a fundamental difference between crashes that are caught by the LabVIEW crash reporter, and crashes that aren't? Are the first type of crashes triggered by LabVIEW itself (due to insanity detected), and are the second type caused by the OS (Windows in my case) terminating the process (due to the process trying to perform some illegal action)?

Thanks!

0 Kudos
Message 1 of 4
(143 Views)

@Petru_Tarabuta wrote:
  • Are there any logs that can shed information on why the crash report could not be sent?
  • *Other times LabVIEW crashes but the LabVIEW crash report window does not show at all.
    • Is there a fundamental difference between crashes that are caught by the LabVIEW crash reporter, and crashes that aren't? Are the first type of crashes triggered by LabVIEW itself (due to insanity detected), and are the second type caused by the OS (Windows in my case) terminating the process (due to the process trying to perform some illegal action)?

Thanks!


LabVIEW and other NI services generate logs in

<Your user documents folder>\LabVIEW Data\LVInternalReports\<Application name>

 

You can check there and see if you see anything helpful.  Probably not.

 

When LabVIEW crashes, it doesn't recover alone, there's a program that runs on startup and sits in the background of your computer named "NI Error Reporting Server".  You should see it if you open up Task Manager and look in the "Background processes" section, and it's also in the "Startup" section.  If LabVIEW crashes, then that is what makes the window show up that lets you report (or not) the crash.  If it doesn't show up at all, then it could be that this either isn't running or LabVIEW closed in such a way that it didn't register as a proper crash.

 

Is there a reason you're trying to send these reports?  Have you contacted NI support and they asked you to send them to help with something?  If not, it's not very likely that anything will matter if a report doesn't get sent.

0 Kudos
Message 2 of 4
(110 Views)

@Petru_Tarabuta wrote:

Questions

  • Does anyone know what causes the crash report not to be sent?

Whenever my crash report fails to send, I find it is usually because corporate IT blocked the communication for some reason.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 3 of 4
(92 Views)

Thanks both.

"LabVIEW and other NI services generate logs in <Your user documents folder>\LabVIEW Data\LVInternalReports\<Application name>" - Yes, I can see crash reports there. But nothing that provides information on why some crash reports couldn't be sent.

 

"When LabVIEW crashes, it doesn't recover alone, there's a program that runs on startup and sits in the background of your computer named "NI Error Reporting Server".  You should see it if you open up Task Manager and look in the "Background processes" section, and it's also in the "Startup" section.  If LabVIEW crashes, then that is what makes the window show up that lets you report (or not) the crash.  If it doesn't show up at all, then it could be that this either isn't running or LabVIEW closed in such a way that it didn't register as a proper crash." - Thanks, I was vaguely aware of the NI Error Reporting Server but wasn't aware of its role. Using Process Explorer I can see a process named nierserver.exe whose description is "NI Error Reporting Server".

 

"Is there a reason you're trying to send these reports?  Have you contacted NI support and they asked you to send them to help with something?  If not, it's not very likely that anything will matter if a report doesn't get sent." - I would like to send the crash reports simply to provide data points for NI, such that, hopefully, the cause(s) of crashes are addressed and the LabVIEW IDE becomes even more stable in the future. I have not contacted NI support, and don't plan to. There are days when the LabVIEW IDE doesn't crash at all, and others when it crashes even 5 times per day. It's frustrating when it happens, but thankfully it's not a showstopper.

"Whenever my crash report fails to send, I find it is usually because corporate IT blocked the communication for some reason." - Thanks. I think this is what stops the crash reports being sent in my case too. The laptop I'm using is behind a corporate VPN. The strange thing is that it sometimes (roughly 50% of the time) works. It seems that some days all reports get sent successfully, and other days all reports fail to send. It would be nice if the NI Error Reporting Server would log or display the reason why it could not send the report.

0 Kudos
Message 4 of 4
(66 Views)