0xF Resource not found. Could not load Front Panel if there's a broken member of a class

[nanocyte]

If there is a broken member of a class and you build an executable, you get an error when you run the executable:

LabVIEW: (Hex 0xF) Resource not found.

An error occured loading VI 'Class xxx'

LabVIEW load error code 3: Could not load front panel

A few odd things:

• I don't use the front panel or call the broken member in any way. Why is it trying to load anything? I have "remove unused members of project libraries" checked but it seems like the unused member is not actually removed from the EXE which makes it larger than it has to be.
• Why didn't the builder notice this problem when it was building?
• The top level runs just fine so why is there an issue when it becomes an EXE?
• At the very least, couldn't the RTE wait until it's asked to run the broken member before throwing this error.

[mjochinsen]

I have the same issue. Any ideas?!

[nanocyte]

I think it's a bug in that the build isn't properly disconnecting the unused members but the workaround is pretty simple. Just delete the unused broken member.

[mjochinsen]

I'm not sure if it is related to my project or Vis. Because I opened a few back up copies of my project which I am sure they were working when I made the backup. They don't work now.

The only change I've done was to install a package

The errors points to a different VI every time:

-Simple Error Handler.vi

-MGI write Anything.vi

-My own VIs

When trying toale it work, I ended up getting this message too "This vi is not executable. The full development version of LabVIEW is required to fix the errors"

But in the NI License Manager, is see LabVIEW full Development System as registered.

[mjochinsen]

I'm not sure if it is related to my project or Vis. Because I opened a few back up copies of my project which I am sure they were working when I made the backup. They don't work now.

The only change I've done was to install a package

The errors points to a different VI every time:

-Simple Error Handler.vi

-MGI write Anything.vi

-My own VIs

When trying to make it work, I ended up getting this message too "This vi is not executable. The full development version of LabVIEW is required to fix the errors"

But in the NI License Manager, is see LabVIEW full Development System as registered.

[nanocyte]

The error is just trying to hint that you have to open the VI in the dev env. Not that you are missing the dev env.

It's odd that you are seeing a different VI implicated. I suspect your error is actually different than mine because I think mine is specific to libraries. But, the root cause might be similar (bad linking). But, the work around might be different so you might want to start a different thread. With that said, when I see issues like that (what version of LV are you on, have you tried 2020 or 2021?) I usually clear object cache and ctrl click the run arrow at the top level to rebuild the hierarchy.