Hello Brunotte,
It almost sounds like as if not all handles/references are closed properly.
For example, if you configure and open a CAN port, perform some actions with that port and then stop the VI with the ‘Abort’ button, so that the ncClear VI is not called, the handle handles/reference to the port will still be valid and the port still running/active. Calling another ncConfigNet on that port will then cause errors like 0xBFF62007.
On Windows, this is a bit easier to deal with as you can just close all open VIs (and, if necessary LabVIEW itself) to force the NI-CAN driver to invalidate all references and stop the CAN port, but unfortunately this is not possible on LabVIEW Real-Time.
I guess that this is the main problem. Once there are no more unclosed references, the problem with the ncAction (Reset) should disappear, thus you might not need to clear the buffer with the ncGetAttr (Read Entries Pending) + ncReadNetMult combination any more.
Regards,
-B2k