Problem with .exe and vi.lib

[alvamatik]

Hi all!
I'm trying to build an .exe, but I have problem with vi.lib 😞

In my project there's the main VI and the folder "dependencies" that contains some VI from vi.lib.
When I run my VI from the development system, it works fine. When I run the compiled VI (the .exe file that I build), a dialog box pops up asking me, one by one, the location of some vi included in vi.lib, that I used!

If I copy manually the folder c:\program files\National Instruments\LabVIEW 8.6\vi.lib in the folder where I have the exe file (d:\builds\myproject\app) it works fine!

Why the .exe file doesn't know where is the vi.lib? Anyone can help me?

[Norbert_B]

What are the VIs which are searched for? Are those from special toolkits?

Have you played around with the settings in "Advanced Exclusions"? What if you remove all checkmarks there?

hope this helps,

Norbert

[alvamatik]

the VIs missing are: "Not found Dialog.vi", Details Display Dialog.vi", "Set String Value.vi"

If I try to load them during startup from somewhere, the app asks me more VIs...

I don't have "Advanced exclusions", I have "additional exclusions" and I tried to remove all checkmarks, same result.

[Norbert_B]

Could you post the project? This seems a rather odd issue....

If you do not want to post the project (or must not), please contact your local NI Support for further help.

hope this helps,

Norbert

[SnowForest]

Have you changed LabVIEW version ? I have noticed that almost every time I must do build setup again if LabVIEW version have changed. I recommed to create totally new build setup and then test to do EXE. This have helped me many times with strange EXE problems.

-Jim

[IMpossible1 · Accepted solution]

Not found Dialog.vi is present in General Error Handler CORE.vi. Seems like you have used general error handler or simple error handler in your program. I would like to give you a work around. Open you general error handler VI (also the CORE vi) from project and save it before building your exe ( you have to do it every time while building your exe. Now you don't have to put the vi.lib VIs in your exe folder.

Try it, I have done this in my project.

🙂

[alvamatik]

It works!!!!

But I don't understand why happens such a strange thing......

thank you.

[IMpossible1]

Not found VI is not linked with the caller VI which should be the normal behaviour. so you are manually linking it after opening the caller VI and saving it.

[dr2]

I just experienced the same problem with LV2012, and opening and saving the error handler fixed my problem.