Try the following troubleshooting steps, and see if the behavior persists:
- Remove and replace the module or card in the chassis
- Reset, or power cycle the chassis
- If the behavior is on a occurring on a cRIO, try compiling and running a blank FPGA VI on the chassis prior to self testing.
If you are starting and stopping sessions asynchronously:
XNET Stop will stop a session first, and then try and stop the interface if it is not being used by another session. If you are starting and stopping sessions asynchronously, different processes could cause the firmware to behave unexpectedly or enter a bad state. Once the firmware is in a bad state, the system API will not be able to communicate with it and will re-assign the interface of a default name of "CAN-1" which will cause further internal errors.