Executable can't find some vis

[Collin M]

When I run a LV created executableI get a dialog that it cannot find the vis listed below. If I navigate to them through the file dialog box my exectuable runs fine. This is a new problem - previously the executable worked as expected. I did recently upgrade to 8.6. I did verify all these vis are present in my 8.6 <vilib> directory. I didn't see anything in the build spec to cause LabVIEW to search for a specific location. I didn't think that would be necessary as these are all native LV vis. I did verify this behavior on two separate systems. Anyone have any ideas?

<vi.lib>\Utility\error.llb\Not Found Dialog.vi
<vi.lib>\Utility\miscctls.llb\LVBoundsTypeDef.ctl
<vi.lib>\picture\picture.llb\Get Text Rect.vi
<vi.lib>\event_ctls.llb\eventvkey.ctl

[Hillman]

Hi Colin,

Thanks for the post and I hope your well today!

I have not seen this issue before - but you seem to have covered a few of the normal steps.

Do you think you could supply the source code?

If you manual include these files (vi and ctl) in the build spec one assumes this box doesnt appear?

Can you verify the paths for the browsed file and the searched file are the same?

Kind Regards,

James.  

[mikeporter]

It sounds like perhaps these are in something that is being called dynamically. If they were statically liked into the hierarchy the application builder would include them into the build automatically. Is there anything else that is coming up as missing?

Mike...

[Hillman]

Hi,

I think mike is correct - something must be dynamically called.

Where these vi's added to vilib, remember that the LabVIEW runtime engine vilib may not include those vi's. So therefore you will need to include them in the build.

Just a thought, please let us know if you've resolved this issue.

Kind Regards,

James. 

[Collin M]

I'm not calling any vis dynamically. How do I include these in the build? In my project explorer I can see the vis under dependencies->vi.lib but I don't see a way to manually add them to the build spec.

[Hillman]

Hi Colin,

Thanks for the reply.

In order to include support files into an executable, these files must be first added to the project and then they can be included as support files in the executable. First, to add a file to the project explorer, right click My Computer >> Add >> File.. and browse to the file you would like to add.

Once the support files have been added to the project, they can now be included in the executable. To do this, right click Build Specifications >> New >> Application (EXE) . In the  Application  Properties , select Source Files Settings and add your main VI to the Startup VI's box, and the rest of the support files to the Always Included box.

Hope this helps,

James. 

[Collin M]

I tried adding the vis that were not initially found. I built the executable and now there are more vis that are not found but they are in the same llbs as the previous vis that were not found. I tried adding the entire llb (as an llb, not a file) and then it doesn't find the files it originally couldn't find. Any more ideas? I'm about ready to try uninstalling everything and then reinstalling.

[Hillman]

Hi Collin,

I hope your well.

I have been away teaching for a few days and want to catch up with your interesting issue.

Did you resolve it in the end?

My thoughts are currently, on the deployment machine can a simple vi reference the problem files (vis/ctls)? Confirm the files are present is obvious.

Please update the post, and we can continue to look into it together.

Kind Regards,
James. 

[Collin M]

I haven't had a chance to work on this lately. I have confirmed that on the build machine and a seperate machine the behavior is identical. The executable can't find the vis reference above on either machine. But if I navigate to them manually everything works fine. I do have to navigate to them manually every time I run the executable though.

[tmaxprt · Accepted solution]

One way I have been able to get around this problem (experienced many times with LabVIEW 8.6) is to remove all build configurations from the [project (installers, exe dll etc) and to recreate them