Error when starting executable on target PC

[mschoenborn1977]

Hello All,

      This is my first time posting here so bear with me.  I have been using LabVIEW for over twenty years but rarely have created executables until five years ago.  Now to help deployment of test program I am in need of help solving a problem of running an installer program created though the build Specifications.  The executable works fine on the development PC however I get the following error when running on the target PC.

      I will need to Have the program installed on twenty PCs so it is very important that all necessary components are installed correctly.  We are using the PC as controller with an NI- 9149 Ethernet Expansion Chassis for I\O control.  Originally the test program was written in LabVIEW 2017 and Windows 11 has forced me to upgrade to 2025 for cRIO driver compatibility.  For compliance reasons I don't want to be loading LabVIEW 2025 to all the PCs I my companies Lab but need the program which seems to work fine on the development PC to work from an installer version on the target PCs.  Any help on this would be great since I have not found reference to this function any were.

      Other things to note the LabVIEW 2017 developed version does work on all target PCs though all had a copy of LabVIEW and most the correct cRIO drivers loaded by my IT department.  I have tried to load the cRIO driver on a target PC then install the program without success.  Also tried to add some folder structures to the installer build that did not work. I believe if I knew the folders and files that are needed, I would be successful.

      If anyone has seen this problem I would appreciate the help.  Thank You in advance.

[mschoenborn1977]

After a few more hours of searching I found the actual missing file.  The file causing the problem was nNIBlueBus_nCrioFixed.dll.  For LabVIEW 2025 this file needs to be present in c:\windows\Syatem32 and c:\windows\SysWOW64 for RIO functions to be used in executable.  Once the file was added to the installer build specifications Destination View under the two folders mentioned the program worked as expected on the target PC.  Only question I have now is why LabVIEW was unable to determine it would need this file when it is part of the NI RIO driver, I think?

[Messenger2]

Hello,

May I ask if you have tried updating cRIO drivers on both your PC and on the cRIO itself? It's an interesting issue, I'd also assume that LabVIEW should detect necessary drivers. You mentioned that the IT department deployed the drivers, but maybe they had old/inaccurate copies of the drivers?

Edit:
I'm not sure if you've found this link, but a similar issue has been noted in "NI CompactRIO Device Drivers May 2019 and R Series Multifunction RIO May 2019 (19.0) Known Issues" (linked here.) Looks like development environment settings and runtime settings/configurations aren't always synced. Please see the following text from the link:

Use of RSI Module Property Node in LabVIEW-built executable using CompactRIO 19.0 LabVIEW 2019 Runtime support will cause executable to fail.

CompactRIO 19.0 LabVIEW 2019 Runtime support is missing components which enable the use of the RSI module property node. When the RSI module property node is present in a built executable that uses CompactRIO 19.0 LabVIEW 2019 Runtime support, the executable will fail with an indication that a .dll file is missing, or with an error that says a refnum entry point cannot be found. The required components missing from the LabVIEW 2019 Runtime support are present in LabVIEW 2019 development support, so the RSI module property node will work in the development environment.

Workaround:

To resolve this issue on a computer with CompactRIO 19.0 LabVIEW 2019 development support installed:

1. Find the two required files at the following file locations:
   C:\Program Files (x86)\National Instruments\LabVIEW\2019\resource\nNIBlueBus_nCrioFixed_nRefnum.dll
   C:\Program Files (x86)\National Instruments\LabVIEW 2019\resource\Framework\Providers\nNIBlueBus_nCrioFixed.dll
2. Copy these files to the following directory:
   C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2019

To resolve this issue on computers targeted for executable installation:

1. On a computer with CompactRIO 19.0 LabVIEW 2019 development support installed, find the two required files at the following file locations:
   C:\Program Files (x86)\National Instruments\LabVIEW 2019\resource\nNIBlueBus_nCrioFixed_nRefnum.dll
   C:\Program Files (x86)\National Instruments\LabVIEW 2019\resource\Framework\Providers\nNIBlueBus_nCrioFixed.dll
2. Add these files to the LabVIEW project where the LabVIEW installer for the executable program is being built
3. In Installer Properties, in the Source Files category, add the two .dll files to the LabVIEW 2019 Run-Time folder

This will cause the files to be installed to the LabVIEW Runtime folder by the installer.

[mschoenborn1977]

Thanks For the reply Messenger2.  yes, similar to 2019 as you posted.  Workaround I found for 2025 was to add the files to locations shown in picture. This is where I found the files loaded on the development PC.  It does work though not certain it is the best solution.

For the question of driver revision, this should have been the same as on the development PC since I had my IT group only run the installer build and no other NI installers.  It is possible the installer did not build as expected I just don't know.  At least the workaround is working.