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

[wikessen]

Could you try a "Clean" action from the App-Builder pulldown and then rebuild? This would always reproduce the issue in my case.

[Darren]

I looked through the app builder logs attached above, nothing out of the ordinary jumped out at me.

If anybody on this thread is able to share code that reliably reproduces the 1051 build error, please send me a direct message so I can get the code and try to reproduce the issue in-house at NI. Thanks.

[wikessen]

I made a stripped down version of a larger project that reproduces the error (LV24Q3 64bit, attached)

It turns out that this issue is related to MediaMongrels Ltd's Websockets (Version 2.0.2.41) package, which can be installed via VIPM.

I suspect that the issue has to do with the fact that the Wesockets package incorrectly claims a couple of VIs from vi.lib (as per menu Item "Find Item Incorrectly Claimed by a Library" form the project root).

The issue only appears if building the vi using websocktes as module into a path rather then compiling it into the main app.

To reproduce the issue you have to install the websockets packet, then build then "Clean" from build specs menu, then rebuild.

[Darren]

Thanks, wikessen, I was able to reproduce the issue in LabVIEW 2024 Q3 Patch 2 64-bit.

I have filed Bug 2914772 to LabVIEW R&D to investigate the issue further.

[wikessen]

I found another work-arround for the issue:

"Clear Compiled Object Cache..." from the Tools/Advanced menu-bar.

If this is done before each rebuild then everything seems to work.

[remywizard]

I too am having this exact same issue. I also am using the MediaMongrels WebSockets. Clearing the object cache as a work around is working for me as well. I was using LabVIEW 2021 and updated to 2024 Q3 release and this issue popped up.

[danijobe]

Just wanted to add to this thread for anyone searching for it - I was getting this error building a lvlibp from a project that was copied from another project. When I made a new project and created a fresh build specification I was able to build without errors. Clearing compiled objects cache didn't fix it for me.  

[aartjan]

I am running into the same issue, too, after migrating a project from LV2020-32 to LV2024Q3-64. Mine does include openG VIs and a webservice, too.

[aartjan]

I have somehow introduced this error again in one of my web app projects, and I can't seem to get rid of it. Now I can't deploy the application update.

The bug ticket doesn't come up in the 2025Q1 bug fix list. I tried building my app in 2025Q1 anyway, but it yields the same error 1051.

[Darren]

---

@aartjan wrote:

I have somehow introduced this error again in one of my web app projects, and I can't seem to get rid of it. Now I can't deploy the application update.

The bug ticket doesn't come up in the 2025Q1 bug fix list. I tried building my app in 2025Q1 anyway, but it yields the same error 1051.

---

I was unable to reproduce the error in LabVIEW 2025 Q1 with the original codebase that reproduced the error in previous versions. Are you able to share code with me that reproduces the build error in 2025 Q1? If so, please send me a private message so I can try to reproduce the error in-house. Thanks.