Sporadic Error 1051, Method Name: Library:Open when building an App

[wikessen]

Building an App with LV24Q3 I get the error message:

Error 1051 occurred at Invoke Node in AB_Source_Library.lvclass:Open_Reference.vi->AB_Build.lvclass:Open_All_References.vi->AB_Build.lvclass:Copy_Files_Core.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller

Possible reason(s):

LabVIEW: (Hex 0x41B) A LabVIEW file of that name already exists in memory, or exists within a project library already in memory.

Method Name: Library:Open

The App building process was fine in LV23Q3 and LV2020 (with same project file). Strange is also that a first build with a fresh Labview install works OK, but only after the second build I get the error message.

I already tryed the "Clean" action of the app-builder, a manual deletion of the Build directory and windows restart.

After some more testing I figured out that the build fails sporadically most of the time without making any changes on the project.

Any hints what might be going on?

[Darren]

Does your EXE call any OpenG VIs (i.e. VIs installed in [LabVIEW 20xx]\user.lib\_OpenG.lib)?

[Darren]

---

@zeucqu2 wrote:

Never used this library 

---

I was aware of an issue with the new Project Save Version feature in LabVIEW 2024 Q3 that could cause this error with builds that included some OpenG libraries, that why I asked. I'm not aware of any other bugs specific to that error code in recent LabVIEW versions.

---

@zeucqu2 wrote:

Good luck, you're doing great!

---

Thanks, you too!

[wikessen]

Thanks for your suggesion Darren, but no, there is no OpenG involved. Its not even installed 

[Darren]

Does your EXE build include a web service?

[wikessen]

No Web service is included.

[wikessen]

I have been playing a little more with the App-Builder.

Very Oddly, after I duplicate or rename my build specs, then the build works.

But after doing "Save All" and then "Save Project" or after removing the build directory the build process will be broken again.

I have also tryed to run the build via Labview-CLI with the "-Verbosity Diagnostic" option, but was not able to get any more detailed info in the logfile/console. Does anybody know if there are more options to debug the App-Builder?

[Darren]

---

@wikessen wrote:

Does anybody know if there are more options to debug the App-Builder?

---

If you add NI_AppBuilder_Logging=True to your LabVIEW INI file, then a detailed log will be created next to the .lvproj file on disk whenever you do a build.

[wikessen]

Thanks Darren,

the NI_AppBuilder_Logging=True realy gives a lot of debug info.

I have attached the build logs of the failing build spec and the successful copied build spec.Maybe someone can make sense of it.

[aeastet]

I am seeing this same error when using VIPM to build a package for release. I have built many version of this software and now it will not build and I get this error. I have mass complied the code and it has no problems. The code has no broken vi's. I'm just not able to build code that I could previously build.

I am using LabVIEW 2024 Q3 patch 2

UPDATE: I went a built a different package and came back to this one. This time I was able to build my package with no changes.