LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Open VI Reference Error in the executable version only

Solved!
Go to solution

Hello folks! I am having a strange issue since I updated to Labview 2014: I have a vi that uses "Open VI Reference" in order to programmatically open the desired vi. It worked flawless also in the compiled version (.exe) of the program until yesterday, when i compiled it again for the first time since my update to Labview 2014. It compiles with no problem, but when i start the exe and load the first vi it already gives me an error "Built Application or Shared Library (DLL): Missing".

The point is that all the VIs that i want to open are inside an LLB that is supposed to be compiled inside the .exe: infact the path that i use to open is:

 

D:\LabVIEW Data\builds\Sequenzer\Sequenzer2.0.exe\com_lv_sequenzer\trunk\Sequenzer_Functions.llb\Seq_Connect_to_Database.vi

 

And i get error number 7:

Open VI Reference in Seq_Function_Interface.vi->Sequenzer_Main_2.0.vi<APPEND>
VI Path: <b>D:\LabVIEW Data\builds\Sequenzer\Sequenzer2.0.exe\com_lv_sequenzer\trunk\Sequenzer_Functions.llb\Seq_Connect_to_Database.vi</b>
Built Application or Shared Library (DLL): Make sure all dynamically loaded VIs were properly included in the build specification for the application or shared library.
LabVIEW Real-Time: VIs built into executables cannot be accessed through VI Server calls. Use Source Distributions to dynamically call VIs on Real-Time targets.

 

The vi Seq_Connect_to_Database.vi is included in my built (as you can see in the attached screenshot and as it has always been).

 

Do you have an idea of why it is not working anymore?

 

Thanks a lot in advance!

Dario Cassaniti

0 Kudos
Message 1 of 26
(10,125 Views)

Dario,

 

what was your previous LV version?

I understand that the previous EXE was built in an older version of LV....

 

Norbert

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 2 of 26
(10,098 Views)

It was Labview 2012...

0 Kudos
Message 3 of 26
(10,091 Views)

If you're not loading the VI dynamically (e.g. as a plugin): Do you wire in the path to the VI directly or do you use the name/path property of a Static VI reference to get the path to the VI? That should return the path to the VI regardless of where it is located within the build (e.g. inside/outside of the executable).


LabVIEW Champion, CLA, CLED, CTD
(blog)
0 Kudos
Message 4 of 26
(10,085 Views)

That's the way i do it: i read the path of the executable and i build the llb path (and conseguently the vi path) on it...

0 Kudos
Message 5 of 26
(10,082 Views)
What is the path at the VI open? Is it correct? If the VI is included but the path is wrong, you still won't be able to find it.

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 6 of 26
(10,060 Views)