Resource not found: NI_MAPro.lvlib, NI_AAL_Sigproc.lvlib

[eximo]

Receiving error messages when trying to run the compiled version of a VI on a non developent target machine.

Configuration:

• LV run time 2016 x64
• LV development 2016 x64
• lv visa drivers 2017

development machine also has labview run time, and development for 2015, including the sound and vibration toolkits.

How do I get rid of the error? 

Is there a way to force the compiler to use the lvlib that I need? 

Is there a way to identify which .dll the functions are using?

Executable runs fine on the development machine, however generates errors on non development machine at execution with regards to the lvanlys.dll and the associated NI_MAPro.lvlib and NI_AAL_Sigproc.lvlib libraries.

Other previous user posts 1, 2 have mentioned that this can be caused by the wrong version of lvanlys.dll getting incorporated into the build or installer.  I have tried both lvanlys.dll ver 16.0 and 17.0 without success.

I also tried to force the compiler to "always include" the NI_mapro.lvlib and NI_AAL_sigproc.lvlib libraries, but National Instruments released them in a locked state and prohibits the compiler from compiling them in this locked state.

Attached are the zip files that contain the executable, the vi code and the error message screen shots.

[eximo]

Looks like the fourm doesn't allow uploads of executables.  I'll change the extension to zzz from exe and you can change it back if you want to troubleshoot it.

[eximo]

Similar problem here https://lavag.org/topic/16590-ni_aalprolvlib-missing-from-installation/

[JaredT]

Hello eximo,

Would you mind posting a MAX Technical report for both the development machine and the target machine? I suspect there may be something installed on the development machine that is calling the NI_MAPro.lvlib that may need to be updated/installed on the target machine. The process for creating the report can be found here http://digital.ni.com/public.nsf/allkb/271F252B4EF0A2E0862570E70056A1E4.

Regards,

Jared T.

[eximo · Accepted solution]

Eventually we were able to get it working, but the reasoning is unclear.

The development environment is LabVIEW 2016, with VISA 2016.  By installing Run-time 2017 and visa 2017 and replacing the lvanys.dll with the .17 version it worked on the target (non development) computer.  

It is clear there was some mismatch but replacing any one of those sub components individually did not fix the issue.  Only after making every single component a 2017 version did it work.  (making everything 2016 or 2015 did not)