Executable can't find some vis

[Hillman]

HI Colin,

I hope your well.

I have recently come across another instance of the issue (another AE), and was wondering if you still have the issue?

I was wondering if you could tell me / send me an example project?

My guess is that these VIs (ctrls) have changed between 8.5 and 8.6 - now clearly require some form of adding into the project. 

I would suggest,

a. Dragging the VIs from vi.lib into the project.

b. Under the Build options I would select to Always Included.

If you could forward the information that would be great.

[Hillman]

Hi All,

Just to sum up then,

Resolution:

Delete the build spec from the project and then recreated it. Also deleted all the files created during the build.

[JJohnston]

I have deleted my build specifications and the build directory and recreated build specifications; and I am still getting the prompts for vi's and controls when I try to run the executable.  Your solution does not work.  I guess I need to manually add all of these files to my build specification... labview comes through again...

[Hillman]

Hi John,

Thanks for your post and I hope your well.

I am sorry your having issues that werent resolved in the same mannor. 

What do you mean you've deleted and then I guess you need to add the files... how would this work anyother way?

If you could explain in more details what you've done then maybe I can help you to resolve the issue.

Thanks, 

[JJohnston]

Hi, thanks for responding.  I have not explicitly made any dynamic calls in my application, however there must be some dynamic references in the background that I have no control over; when i run the executables, I am prompted for vi's (from error.llb) 'not found dialog.vi', 'details display dialog.vi', and 'set string value.vi'.   If I add these 3 vi's to my project and add them to the 'always included' section of the build specification, the executables work without issue. (perhaps this is a known issue with 8.6 - I dont have the time to look), but the trick mentioned above about deleting the previous build specifications and build files did not work for me.

Thanks.

[Hillman]

Hi John,

Thanks for your reply. 

I am glad things are working - your issue was slightly different it seems. 

If you have dynamic calls then you must add them manually this is well-known (espically for users of the Report Generation Toolkit). Your right, this is unusal for vi's from vi.llb. 

Im glad its working anyways.

[tst]

This seems to me to be a bug which needs to be handled.

A coworker ran into the same issue with VIs from error.llb (called from the error handler VI) and after examination, it seems that this is caused by the conditional disable structure. The general error handler core VI has 3 VIs which are placed inside those structures and are only called when not on RT targets. It looks like there is a bug in the CDS, since after opening one of the VIs I couldn't see any entries in its Callers menu item. Only after double clicking the VI in the GEH core VI the GEH core VI appeared as a caller.

In this case my coworker did work with an RT target at some point, but LabVIEW should still have been able to load the dependencies correctly when he tried to build something for the PC. I think that the other examples brought up in this thread are probably related, as they are related to UI stuff which would not be in an RT target and would probably be in a CDS.

As I said, I think this needs to be reported to R&D.

[Hillman]

Hi All,

Thanks for the added information.

I have submitted a CAR - Corrective Action Request - #136989 regarding this issue.

[J0LT]

Same problem, same missing files. Solution to "always include" seems to work.

This project does target a RT system but not as part of the executable I was trying to build...

[Collin M]

Have you tried deleting the build spec from the LabVIEW project manager and then recreating it?