LV2017 Application builder issue

[StevenHowell]

Good evening fellow wire slingers!

Today I was finishing up an application for a client and started to build the executable. I am working in LabVIEW 2017.

When I start the build, everything is fine until it gets to the "compiling" point in the progress bar and then I get this error screen.

The app builder stops until I either click show details or ignore. 

Once the build finishes if I click show details, I get this screen.

I have never seen this behavior before when building an executable. I am using the Actor Framework for the application, and when I launch the application, it never launches. I see the main gui come up but no data. 

I have debugged and the top level actor is never launching. In the Launch Actor Core.vi the Actor Core never launches, and then the launcher hands at the dequeue after. Not sure if the above cross link has anything to do with it? 

[MangeshD]

The warning list window is showing that the dependencies for error.llb loading from custom folder(C:/tNIAB/) instead of default NI folder.
This may be a conflict.
From project window change the dependancy of custom folder error.llb, to default (which is expected dependency path in warning list)

[Fedor]

I get the same warning with my LV 2108 application builder:

C:\Program Files\National Instruments\LabVIEW 2018\resource\dialog\lvconfig.llb\LV Config Read String.vi (LV Config Read String.vi)
    - The VI expected to be at "<vilib>:\Utility\error.llb\Error Cluster From Error Code.vi" was loaded from "C:\github\builds\ResonanceSpectrometer\ResonanceSpectrometer.exe\1abvi3w\vi.lib\Utility\error.llb\Error Cluster From Error Code.vi".
C:\Program Files\National Instruments\LabVIEW 2018\vi.lib\Utility\SystemLogging\Write to System Log.vi (NI_SystemLogging.lvlib:Write to System Log.vi)
    - The VI expected to be at "<vilib>:\Utility\error.llb\Error Cluster From Error Code.vi" was loaded from "C:\github\builds\ResonanceSpectrometer\ResonanceSpectrometer.exe\1abvi3w\vi.lib\Utility\error.llb\Error Cluster From Error Code.vi".

I don't see how I can change dependency for error.llb content since it is already located in default Labview folder.  

[mjhakkar]

Hi,

I'm having the same issue on LV2018. LV Config Read String.vi and Write to System Log.vi are loading Error Cluster From Error Code.vi from the build folder ("build path"\1abvi3w\vi.lib\Utility\error.llb\.) instead of the <vilib>:\Utility\error.llb\.

It's kind of annoying, I can't leave the build to run on it's own 

[cbutcher]

Having not tested, I'm not certain, but I suspect if you tick the "Exclude Dependent Shared Libraries" you might have some luck avoiding this.

You become dependent on those VIs being available wherever you run the application though - I'm not sure what the interaction with the RunTime engine would be like.

[mjhakkar]

---

<Forum rubber duck debugging>

---

I'm having the same issue on LV2018. LV Config Read String.vi and Write to System Log.vi are loading Error Cluster From Error Code.vi from the build folder ("build path"\1abvi3w\vi.lib\Utility\error.llb\.) instead of the <vilib>:\Utility\error.llb\.

---

I took a closer look at the warning message, which lead me to AF Debug.lvlb/Generate Trace.vi. From there I found Write to System Log.vi inside a conditional disable structure. Of course all trace vis are inside a conditional disable structures in Actor Framework. This then lead me to Build Specifications and to uncheck "Modify project library file after removing unused members"

[croohcifer]

Hi Marko,

Did unchecking "Modify project library file after removing unused members" resolve the problem for you?  I've just run into this same warning, and unchecking that box didn't change the behavior for me.

David

[mjhakkar]

Hi David,

Yes it worked in my project. Other settings I have are:

[andreas_he]

Since I found a solution which I think works for others as well, I want to share it here as well.

I did post in a different thread, so take a look there:

https://forums.ni.com/t5/Actor-Framework-Discussions/AFDebug-lvlib-Generate-Trace-vi-causing-error-i...