LV 2013 exe not working with runtime, only with full LV installed

[_Faust]

Hello,

We have this weird problem lately with distributing compiled exe's in labview 2013:

They compile OK and run on the source PC. When installing on another PC the exe runs, but several (sub) VI's are broken and don't run (only showing front panel).
Problem is solved by downloading the LV 2013 trial and installing it, after that it works.

Happens on WIN7 PCs, but I think I've also seen it on XP machines. Any clue what the cause of this may be? I don't want to install full LV for no reason.

[P@Anand]

In your target PC you might have installed only the Runtime engine which executes the exe but you might be missing the supporting tool kits if any used. To make a proper deployement you must create an installer along with whatever tool kits and support files you have used. Then install this in the Target machine and then run your exe. 

[_Faust]

Ok I can try this, but it has always worked before, and the problems started to arise since like a month or 2-3.

Doesn't the full runtime engine have all the necessary components? Besides PID & fuzzy logic toolkit, I am not using anything!! Just standard LV.

[_Faust]

Hi,

I tried building an installer in Labview incl. runtime. same issue. So this clearly doesn't resolve it (I was already afraid so)/

[P@Anand]

Now what exactly you get? When you said it only shows front panel I suspect there is some error occurs and the whole exe stops working. The execution of the exe and the Developement environment will be little different. For example you might be creating a path for a file and loading the file in this case when you execute the same in the executable the path might be different and you might get error opening it and thus stopping the execution.

You might get a pop-up error message if you leave the output wire open but in the case where you pass the error wire properly then it might silently pass and the execution might stop. Does it make sense?

[_Faust]

The exe loads as if there was no problem. No visible errors or popups. Just some VIs don't run (I can tell; the front panel is unresponsive and shows the default control values).

It is an exe consisting of several tabs with subpanels with VI's loaded into them. Some work, some don't.

So, I close the exe down, install the full labview installer, restart my software (no reboot!!) and it works!

[Hooovahh]

Are you calling these VIs dynamically?  If they are broken the run should return an error.  Are you doing proper error handling to know if the VI is broken in the EXE?

[Dennis_Knutson]

And you should know that there are numerous externals that are not included in the runtime engine. Look in the data folder of your build. Anything there such as the analysis dll?

[natasftw]

In the exe build properties, did you disable options to include vi.lib and the such?  If installing LabVIEW without any additional changes fixes things, I can't imagine it's a dynamic call issue.  The VIs would still be missing with the full development system in place.  It sounds like you're missing libraries that come with LabVIEW and those can be left out of your exe if you choose to leave them out.  If so, you'd need them on the target PC to run the exe.  You'd see them after you installed the full development system.

[_Faust]

I'm calling the Vi's by static VI reference, and I've explicitly added them to the exe's build, so this should be good.

The data folder is also copied always and contains som dll's.

I probably get an error when the exe tries to load some of the sub vi's that are broken, but I'm  suppressing them (yep; error handling could be better in this case!).  So I get no visible error.

My explanation would also be that the exe needs some VI's that are with the standard LV installation; but how do I find which ones?

Thanks for input everyone.