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

[Drouilhet]

Darren,

What is the status of this bug?  I am using Version 2024 Q3 (32-bit) 24.3.2f2 and get the following error using a build spec that worked fine in Version 2021.  I have tried Clear Compiled Object Cache, but that didn't help.

Build error details:

Error 1051 occurred at Open VI Reference in AB_Source_VI.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.

VI Path: C:\builds\UMC\HLM Dorm\UMC.exe\1abvi3w\vi.lib\Utility\error.llb\Error Cluster From Error Code.vi

[Darren]

According to LabVIEW R&D, the bug is fixed in version 2025 Q1. And I was unable to reproduce it in 2025 Q1 with the codebase that previously reproduced it in 2024 Q3.

However, you can see the post above from aartjan on Feb 10th that they are still seeing the error in 2025 Q1. If you or aartjan can share code with me that reproduces the issue in 2025 Q1, I'll re-open the Bug for R&D to look into further.

[Drouilhet]

Darren,

The bug is definitely not fixed, or there is a different one remaining.  I upgraded to LV 2025 Q1 and have the same problem.  When I press BUILD, it takes an unusually long time to start doing anything.  When the build status window finally appears, it gets stuck on this view for a very long time (>10 minutes)

Then eventually, I get a pop-up saying the build failed:

Error Cluster From Error Code.vi is a built-in VI that shouldn't have any issues.  It appears in my dependencies, but I can't find any other instance of it in my project.

My project is quite massive (several hundred MB) and it seems like the issue could be anywhere.  It also requires various add-on packages.  How would I send you the whole thing?

[Darren]

---

@Drouilhet wrote:

My project is quite massive (several hundred MB) and it seems like the issue could be anywhere.  It also requires various add-on packages.  How would I send you the whole thing?

---

I'll send you a direct message on the NI Forums and we can coordinate from there. Thanks for being willing to share your code so we can get to the bottom of the issue.

[Arnorai]

Hello everyone,

nice to see that others also have this migration problem.

There is currently only one solution that solves this problem: Create a new project directly in 2024Q3 or in 2025Q1 and completely recreate the build specification. All those who start directly in LV 2024 or LV 2025 probably do not have this problem.

In the past, removing the “*.alias” file has usually helped, but not here!
Here is an interesting video on the topic: Solved: Build Error AB_Build - NI Community

Best regards Rainer

[Darren]

---

@Arnorai wrote:

There is currently only one solution that solves this problem: Create a new project directly in 2024Q3 or in 2025Q1 and completely recreate the build specification.

---

Rainer, thanks for sharing this tip. I'm curious if you're able to share with me a "before" and "after" .lvproj file where you've solved the issue by re-creating the build spec. Since build specs are stored in the .lvproj, which is an XML file, we should be able to diff the before and after to see what is different about creating the build spec from scratch.

[Drouilhet]

Hi Rainer,

For this fix to work, do I need to recreate a new project from scratch (starting with a blank project and importing all the files), or can I simply delete the build spec from the lvproj file and recreate the build spec?

[Arnorai]

Not from the beginning, for me it helped to create a new project and open the old one. Then copy all objects (VIs, Ctls, Libs, Classes, ... ) into the new project using drag and drop. But then completely recreate all buildspecs. I then copied the upgrade codes and registry entries for my products completely from the old project so that it is identical again afterwards.

Unfortunately, I can't recognize the problem in the XML files, my projects are too big for that! The old project remains in the old version (LabVIEW 2020) and the new one logically in the new version. The only thing I can recognize directly in the two *.lvproj files is that although they are identical, they are different in size and new GUIDs are generated. The new project is much smaller!

[Mark_Yedinak]

---

@Drouilhet wrote:

Darren,

The bug is definitely not fixed, or there is a different one remaining.  I upgraded to LV 2025 Q1 and have the same problem.  When I press BUILD, it takes an unusually long time to start doing anything.  When the build status window finally appears, it gets stuck on this view for a very long time (>10 minutes)

Then eventually, I get a pop-up saying the build failed:

Error Cluster From Error Code.vi is a built-in VI that shouldn't have any issues.  It appears in my dependencies, but I can't find any other instance of it in my project.

My project is quite massive (several hundred MB) and it seems like the issue could be anywhere.  It also requires various add-on packages.  How would I send you the whole thing?

---

I am running into the exact same error. The "Error cluster From Error Code.vi" is the offending VI. As stated, this is a built-in VI and should not be causing this type of issue. My project does include OpenG VIs as well as a Webservice. I need to find a solution to this. Also, I am using LabVIEW 2024q3. For the moment upgrading to LabVIEW 2025q1 is not an option.

[Mark_Yedinak]

I was able to get the application to build by disabling the Web Services. I can live without them for the time being but will need a solution which includes the Web Services.