Receiving Error -1074384560 in NI-XNET Executable

Updated Sep 14, 2018

Reported In

Software

  • LabVIEW
  • LabVIEW Full
  • LabVIEW Professional

Driver

  • NI-XNET

Issue Details

After upgrading my XNET application and building it into an executable, I receive below error:

Error -1074384560 occurred at XNET Create Session (Frame Output Queued).vi:5330005

Possible reason(s):

NI-XNET:  (Hex 0xBFF63150) Alias name passed to a function is not defined. Solution: Define the alias before calling the function.

I'm using the example database NIXNET_example or NIXNET_exampleLDF that is included with the NI-XNET driver. Why am I receiving this error and how can I resolve it? 

Solution

This error occurs because the alias name is no longer associated with the database. To resolve the error, firstly check if you have the Runtime or full NI-XNET driver installed on the target machine by checking the Software tab in NI MAX. 

If you have the NI-XNET Runtime driver installed on the target machine, you will have to create the alias programmatically with the XNET Database API (Measurement I/O >> XNET >> Database >> File Mgt). This is because the NI-XNET Runtime driver does not install the example databases or XNET utilities such as XNET Database Editor or XNET Bus Monitor. 

If you have the full NI-XNET driver installed on the target machine, please follow the steps below to add the alias to XNET Database Editor on the target machine. 
  1. Confirm that the example databases are installed in the correct location: <Public>\Documents\National Instruments\NI-XNET\Examples
  2. If they are not present on the target machine, repair the NI-XNET driver
  3. Open NI-XNET Database Editor from the Start Menu. 
  4. Navigate to File>>Manage Aliases. If the example databases are not already listed as an alias, select Add Alias
  5. Navigate to the file location specified in step 1 and select the database.
  6. Confirm that alias and database were added to Database Editor. Confirm that spelling and syntax of the alias in XNET Database Editor match what is referenced in the executable.
  7. Rerun the executable.

WAS THIS ARTICLE HELPFUL?

Not Helpful