LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Resource Not Found: NI_AAL_SigProc.lvlib

Solved!
Go to solution

On a computer I upgraded from LV2013 to LV2016.  

My program loads and runs correctly when built with LV2013.  

When trying to run the exe that was built using LV2016 I get a Resource not found error.  It could not load Peak Detector.vi from the NI_AAL_SigProc.lvlib library.  

I checked my Device Driver install.  Would someone please tell me how to fix this error?

Mark | CLA
0 Kudos
Message 1 of 7
(3,382 Views)

Do you have Full LabVIEW 2016 or Base? It is not included into Base version

0 Kudos
Message 2 of 7
(3,371 Views)

Nah, if you can build exe, you can open vi.

Do you run it directly after build, on the same PC?

Try to copy your main build specification, and set as source vi one that includes only peak detector.

Do you build into same destination as 2013? Try to change.

Try to force recompile starting from main vi (Ctrl+Shift+Click on arrow)

0 Kudos
Message 3 of 7
(3,369 Views)

I have Professional Development System.

 

I'll try your suggestions.

 

 

Mark | CLA
0 Kudos
Message 4 of 7
(3,360 Views)

Still no solution yet.

Things I have tried:

  1. Run the exe right after the build on the same PC.  Same error.
  2. Put the Peak Detector subVI in a VI and compiled that VI.  Works.
  3. Compiled one of my medium level subVIs that has a call chain that called the Peak Detector subVI.  Works.
  4. Used different PC.  Same error.
  5. Compiled under LV2015.  Same error. 
  6. Mass Compile.  Same error.  This one really confuses me.
  7. Peak Detector.vi is called from two places in my code. One is from a VI in an lvlib.  So I Mass Compiled the lvlib.  And also made all the VIs public.  Same error.

 

Mark | CLA
0 Kudos
Message 5 of 7
(3,324 Views)

Thinking about this further I am wondering if there is some conflicting code in a Disable Structure.  

 

Is there a way to use scripting to look for Disable Structures that have peak Detector.vi in them?

Mark | CLA
0 Kudos
Message 6 of 7
(3,317 Views)
Solution
Accepted by topic author Mark_L

Solution Found.

lvanlys.dll was down level.  This was because the directory location I needed to place the exe used a different lvanlys.dll than the latest from the build directory.  

 

Copied lvanlys.dll to location where the exe would use it.  Now the exe runs.  

 

Mark | CLA
0 Kudos
Message 7 of 7
(3,311 Views)