Missing subvi from ni_aalbase.lvlib

[abdel2]

I have a source distribution which I'm using in my executable application through dynamic VI calling. However, I cannot run the specified VI. It gives me a bunch of errors saying subvi is missing in ni_aalbase.lvlib and ni_aapro.lvlib. I can see both libraries under the "dependencies" section of my project explorer but they are inside vi.lib which is excluded from being copied into the source distribution. Why cannot it find those missing subvis?   

[SnowForest]

Have you marked these dynamic called VI's under "always included"? This can be done in build setup.

[abdel2]

Do you mean I should mark them under dynamic VIs tab of the main executable (not the source distribution)? The signal analysis Vis I'm using are all subvis (not called dynamically) so I hoping they would be automatically included in the source distribution. However, I'll try to find the individual subvis it's giving me errors on and include them manually in the build.

[abdel2]

Ok, so I tried to include all the subvis that the above error included in the "always include" section. Now I got different errors (attached).

Finally, I included the whole NI_aalBase.lvlib and NI_aalPro.livlib and things started to work; but the source distribution size is huge (13 MB). There has to be a better and simpler way than this.

Message Edited by abdel2 on 11-30-2009 11:25 AM

[The_Chancenator]

Hi,

It looks like you are using some of the Advanced Signal Processing VI's that are included as a part of the Full Development version of LabVIEW, but not the Base package: https://www.ni.com/en/shop/labview/select-edition.html

Does your VI run at all, even before building the executable?  You will need to get the VI itself in a state where it could run before you can build an executable out of it.  

Cheers, 

[abdel2]

I am using Professional Development System. At least that's what it shows in License Manager. Everything runs fine as long as it is running under the development environment. Is it possible that Labview run-time doesn't include the necessary files? I am testing the executable on the same development computer with professional Labview installed.

[SnowForest]

Hi,

What is your LV version? If you are using LV 2009 have you installed latest patch? I noticed that they were fixed many things and build setup must be done again.

Have you tested to delete current build specification and then create new one?

[abdel2]

I am using Labview 2009 with the latest patch (f2). I have also tried deleting the old build configuration and creating a new one, but that didn't make any difference.

I guess I'll try and create a new project that calls one of the signal analysis vis, create its source distribution, and then call it from another executable dynamically to see if it produces similar results.

[abdel2]

I've attached an example set to show the kind of the problem I am facing.

The module I'm calling dynamically is in the folder "Test Module".  The actual executable is in the folder "Call Module".

-Run "Call Module/builds/Call Module.exe"

-A dialog box asking for the dynamic vi to call will pop up. Select "Test Module/builds/Execute.vi"

-You'll see Labview ask for path to the missing subvis. If I include the whole NI_aalBase.lvlib and NI_aalPro.livlib, this won't happen and the vi will execute properly and count up to 500.

[The_Chancenator]

Hi,

I downloaded your code and did see the same behavior.  However, I'd like to know your overall goal here--are you just trying to get an executable up and running on another machine?  If so, have you tried building an installer?  What is the purpose of loading the VI's through the File Dialog box, as opposed to just having the top level VI?  I believe that building an installer with your executable would accomplish the same result that you are looking for.  

Please give us a little more about why you'd like to load these VI's from a source distribution. 

Thanks,