02-24-2025 03:19 PM
One of the workarounds to the error 1051 that I've seen provide a successful build for someone upthread was to add the following INI token to LabVIEW:
NewAppBuilderCache.Enabled=False
02-25-2025 11:56 AM
@Darren wrote:
One of the workarounds to the error 1051 that I've seen provide a successful build for someone upthread was to add the following INI token to LabVIEW:
NewAppBuilderCache.Enabled=False
Are there any other work arounds? I have a project that I cannot build. It includes both OpenG VIs and Web Services. We are just now migrating to LV 2024q3 and I'm dead in the water because of this issue. I recreated the project file from scratch in LV 2024 and now when I build I get this same error stating:
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"
02-27-2025 12:46 PM
Mark,
Open the following two libraries if they are present on your system:
[LabVIEW 20xx]\user.lib\_OpenG.lib\array\array.llb\openg_array.lvlib
[LabVIEW 20xx]\user.lib\_OpenG.lib\lvdata\lvdata.llb\openg_variant.lvlib
Right-click the .lvlib and choose "Properties", change the Save Version to "Default", then click OK and save the .lvlib.
Additionally, open this VI:
[LabVIEW 20xx]\user.lib\_OpenG.lib\error\error.llb\Case (Error IO)__ogtk.vi
Pass the error wire through on the error cluster so the VI is no longer broken, then save the VI.
Now try your build and see if it succeeds without error.