Executable can't access VIs in lvlibp because it's not a readable library... Please help

[DailyDose]

Code works in Dev environment without issue.  All lvlibp are part of the project and the necessary VIs are taken straight from them.  In the build, I don't have "exclude packed libraries" checked.  So they're included in the data folder.  However, when I run the .exe it prompts me to find a couple VIs.  So I go to the data folder and select the appropriate lvlibp and it responds with "[my class].lvlibp is not a readable library."  But I can double click and open up that lvlibp up like and see the list of VIs that are in it, and the specific one it's looking for is there.  Any idea what's going on?  How do I fix this nuisance?  Everything runs fine in dev mode.  Super annoying.

[DailyDose]

Also, it's LabVIEW 2020 - and so far I'm noticing a lot of crashing involved with classes in LabVIEW 2020

[DailyDose]

Just learned all lvlibp will be included in the data folder no matter what you do.  So... again, begs the question, why is the executable being refused access?  It's also only looking for ONE vi.  I guess has access to all the others?

[Kyle97330]

For the one VI that's being refused access, is there anything special about it that you know of?  Like it's the only VI with a certain data type, or reference to a DLL, or has special characters in its name, or it's the VI with the longest name in the library?

Something else you could do is use the VI Analyzer on it, specifically the test "General -> VI Properties -> Built Application Compatibility" and see if anything flags (assuming it was you who built it and have full source access to do so).

[Jeff_Long]

I've been having this same issue for years now.  With some applications, it will sometimes search for the lvlib VI and reject as unreadable, and other times will load perfectly fine.  Same EXE build, two different outcomes...

I'd really like to eliminate this issue once and for all.