NI Error Reporting Not Sending Reports Due to Firewall Restrictions

Issue Details

I am using LabVIEW, and I want to ensure that NI Error Reporting (nierserver.exe) can send crash or error reports. However, I notice that no reports are being sent, or the reporting functionality does not seem to work as expected.
My system is behind a corporate firewall, and I suspect that outbound connections may be restricted. I am specifically interested in understanding how NI Error Reporting communicates externally and what needs to be configured for it to function correctly.

Solution

NI Error Reporting (nierserver.exe) sends crash and diagnostic data to external endpoints hosted on *.sentry.io. To enable this functionality, configure your firewall to allow outbound HTTPS traffic (TCP port 443) to *.sentry.io domains.

After updating the firewall rules, restart the NI Error Reporting service or reboot the system and verify that reports can be sent successfully.

Additional Information

NI Error Reporting is designed to collect and submit diagnostic information related to crashes or unexpected behavior in LabVIEW applications. This helps with debugging and improving software reliability. The communication relies on secure HTTPS connections to external endpoints. In environments with strict network security policies, these outbound connections may be blocked by default, preventing reports from being transmitted.

This issue is not related to the LabVIEW crash itself, but rather to the network configuration restricting the reporting mechanism. Ensuring proper network access allows the reporting service to function as intended while maintaining secure data transmission.