Error Hex 0xBFF63001 When Attempting Self-Test for NI-XNET Devices in NI MAX

Issue Details

When I attempt to run a Self-Test on my NI-XNET device in NI Measurement & Automation Explorer (NI MAX), the Self-Test fails and I receive the following error:

The self test failed.
NI-XNET: (Hex 0xBFF63001) An internal error occurred in the NI-XNET driver. Please contact National Instruments and provide the information from the file %LOCALAPPDATA%\National Instruments\NI-XNET\log\niXntErr.log. On Windows XP, the file can be found at %USERPROFILE%\Local Settings\Application Data\National Instruments\NI-XNET\log\niXntErr.log. Please note that this location may be hidden on your computer.
 

Solution

This is a general NI-XNET internal error that can be caused by hardware, firmware, driver, or application-level conditions.

Try the following troubleshooting steps and see if the behavior persists:

• Reset the device in NI MAX, then run the Self-Test again.
• Reboot the PC, PXI controller, or chassis.
• Remove and reinstall the device.
• Update NI-XNET to the latest version supported by your operating system and application development environment.
• If applicable, try a different PCI or PXI slot.
• If the behavior occurs on a CompactRIO system, try compiling and running a blank FPGA VI on the chassis before running the Self-Test again.

If you start and stop NI-XNET sessions asynchronously, different processes can cause the firmware to enter an unexpected state.

When NI-XNET Stop executes, it first stops the session and then attempts to stop the interface if no other session is using it. If multiple processes start and stop sessions asynchronously, the firmware can enter a state where the system API can no longer communicate with it. In some cases, the interface may be reassigned the default name CAN-1, which can lead to additional internal errors.

Additional Information

Review the niXntErr.log file referenced in the error message for additional diagnostic information.

In some environments, antivirus or endpoint protection software can interfere with NI software operation. If the behavior persists after completing the troubleshooting steps above, temporarily disable the security software or work with your IT department to review its configuration.