LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW 2025 Q3 Breaks Actor Framework....Send Ping.vi Owning Library Missing

Solved!
Go to solution

Hello all,

 

I just made the horrible mistake of updating LabVIEW immediately when the new version was available (2025 Q3).

 

My project, which had no errors and was working perfectly fine last night on this PC, now displays this error:

Gryffin_0-1754068591134.png

Gryffin_1-1754068605719.png

 

Please tell me there is a way to fix this without uninstalling 2025 Q3 and going back to 2025 Q1.......

 

 

0 Kudos
Message 1 of 8
(689 Views)

Another restart and it claims these two VIs are missing:

Gryffin_0-1754069435983.png

Gryffin_1-1754069458786.png

 

 

0 Kudos
Message 2 of 8
(677 Views)

Are you able to load the classes outside the application without any errors?

0 Kudos
Message 3 of 8
(638 Views)

After reopening my project in LabVIEW 2025 Q3 at least ten times and trying to recreate the bug in a new blank project....everything works fine now....

 

I am at a loss...but everything works fine now, thank you for your time!

 

0 Kudos
Message 4 of 8
(608 Views)

I'm not sure if this fixed it, but I opened one of my classes by itself, then totally closed out, then opened my project again to find it working.

 

Thank you for your suggestion!

0 Kudos
Message 5 of 8
(607 Views)
Solution
Accepted by topic author Gryffin

Glad to hear everything is working. I can't give a good answer to why your application lost the links to the class VIs, but a refresh seems to have cured the problem. 

 

I will ask the support engineer to close out the support case you opened. Please open a new case if you have further issues. 

0 Kudos
Message 6 of 8
(597 Views)

Gryffin_0-1754417130430.png

 

Upon trying to compile my .EXE, this error shows up again.............................

 

0 Kudos
Message 7 of 8
(481 Views)

The issue was ultimately that a .DLL had been placed in the "Always Included" list and was accidentally removed.

This had no effect in the development environment, but broke the build. Error messages were not helpful (it merely states that Actor.vi is the culprit).

 

I discovered what the issue was by noticing that turning on "Debugging" in the build menu allowed the build to complete, but I did not want to deploy it this way.

I was lucky to recall and try this, it's not clear how I would've determined the problem otherwise. 

Message 8 of 8
(445 Views)