This content is not available in your preferred language.

The content is shown in another available language. Your browser may include features that can help translate the text.

Error -1074384758 or -1074384895 using NI-XNET Create Session

Updated Dec 28, 2023

Reported In

Software

  • LabVIEW

Driver

  • NI-XNET

Issue Details

  • My NI-XNET session in LabVIEW is generating error -1074384895. How can I fix this?
  • When I try to create an NI-XNET session I get either Error -1074384758 or Error -1074384895: NI-XNET: (Hex 0xBFF63001) An internal error occurred in the NI-XNET driver.  Why is this and how can I correct this issue?

Solution

These errors can be resolved in several ways, depending on what components are in your system:
  • If you are using a CompactDAQ (cDAQ) chassis and have multiple NI-DAQmx tasks already running, this is the result of a known issue that has been corrected in NI-DAQmx versions 17.1.1 and later. Upgrade your DAQmx driver to version 17.1.1 or later to add the patch. If upgrading DAQmx is not an option for your system, the following workarounds can be applied:
    • Create your XNET session prior to creating your DAQmx tasks.
    • Downgrade to NI-DAQmx 15.0, if your hardware is supported.
  • The C-Series module or cDAQ/cRIO chassis may have been removed from the system either intentionally or through a USB driver issue, or the chassis had a problem and failed to notify NI-XNET. Upgrade to NI-XNET 17.5 or later as there were improvements that will help you resolve this issue.
  • The Queue Size parameter is not properly configured for your application.If using the USB-8502, verify that the correct port is selected and that it is properly connected to the PC and bus.
  • If you are using a memory database, ensure the memory database I/O mode matches with the database used for another session.
  • This error could be due to memory allocation and not related to the XNET driver. Check Windows Task Manager or Performance Monitor to see if memory growth is an issue.
  • If you are creating multiple XNET sessions, add a delay between the XNET Create Session VIs like in the illustration below.