NI Error Reporting (NIER) FAQ

NI Error Reporting allows you to send NI a crash or internal warning report. You can attach relevant files, comments, and your email address to the crash or internal warning report. When a crash occurs that causes LabVIEW to close, the following dialog box appears:

When an internal warning occurs, the following dialog box appears when you close LabVIEW 2014 and earlier:

When you close LabVIEW 2015 and later, the following dialog box appears:

Sending a report to NI through NI Error Reporting does not provide immediate technical support. NI employees use the reports to improve the software. If you want help resolving a crash or internal warning, contact NI technical support. Opening a Service Request Case Using the Service Request Manager (SRM) will offer you the possibility to add attachments. Refer to Error Log File Location after LabVIEW Crashes article if you want to retrieve and share your error log file.

The crash or internal warning report contains:

• Dump files for the DWarns, DAborts, and exceptions that include error codes and other information pertaining to the crash or internal warning
• A text file (lvlog.txt) that includes additional details on the crashes and internal warnings
• A second text file that includes the comments and email address you enter in the NI Error Reporting dialog box
• The zip file you attach to the NI Error Reporting dialog box

When the NIER server (nierserver.exe) is running, the mini-dumps that are generated when there is an internal warning or crash are called out-of-process mini-dumps. However, when the nierserver.exe is not running (disabled or not installed for some reason), the LabVIEW Development System will create in-process dumps if possible and save them at the same location on disk as the regular NIER internal reports. You will not see the LabVIEW Crash Reporter or LabVIEW Internal Warning Reporter dialog boxes when the NIER Server is not running even though LabVIEW created an in-process mini-dump. LabVIEW built applications/DLLs do not have the ability to create in-process dumps when the NIER server is not available.

When using the LabVIEW Run-Time Engine, you get a crash dialog if an internal error (DAbort) or exception is detected. However, the crash dialog does not have the option to send the report to NI. The product name shown will be the name of the process that crashed and not LabVIEW. Internal warnings cause LabVIEW to create mini-dumps, but the Internal Warning Reporter dialog box will not appear when you close the application. These characteristics apply to LabVIEW built applications, DLLs, and interop assemblies. When a LabVIEW built application, DLL, or interop assembly crashes, the following dialog box appears.

If the connection is too slow or if the report that you send is extremely large, the send process will time out after 5 minutes if it is not completed by then.

3 MB. Currently, you can only attach a VI or a zip file.

LabVIEW saves the last 20 reports for each process or product.

No. If the same internal warning (DWarn) happens back to back during an extremely short time frame, the software throttles the mini-dump generation for that particular internal warning for a certain amount of time.

Your right to privacy is a priority to us at NI. We recognize your need for reasonable control of information that you share with NI. The information contained in the reports sent to NI will consist of a log file, a minimal process memory dump file as well as comments and files you have attached to the crash dialog box. More details about our privacy policy can be found at ni.com/privacy.

You get an Investigate Previous Internal Errors dialog box when you launch LabVIEW 2011 if the NIER Server (nierserver.exe) is not running. The NIER Server always runs in the background, but if it is shutdown or crashes for some reason, LabVIEW reverts back to the pre-2011 crash reporting behavior so LabVIEW can share relevant information about the crash with the user.

No. You should report reproducible issues that you would like to see addressed in LabVIEW so a Corrective Action Request (CAR) can be filed against it.

• LabVIEW Help: Investigate Previous Internal Error or Warning Window
• Error Log File Location after LabVIEW Crashes