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?