Getting LabVIEW load error code 59 using LabVIEW 2010 with a Run Time Engine.

[JoeySpinella]

Hi Holm,

---

@Holm wrote:

Is there a explain to why this flag is set (separate compiled code from source file) .

This force you to build a new exe file every time. And that is costing time is much faster to have the same exe file and just change the single Vi and then re-run the exe

---

Separating the source code from the compiled code is useful for Source Code Management when versions of the VI must be checked out and modified. This benefit is described in this Help File.

If you are trying to retroactively edit the VI referenced in a built executable, leaving that box unchecked will allow you to maintain that functionality, as previously discussed in this thread. I hope this explanation helps!

[beuvink]

Hello all,

I experienced a similar issue when running a vi on a runtime system in LV2012. The SSE option didn't solve the issue. Problem can be reproduced in the following steps:

(1) Create an empty project

(2) Create an empty vi in this project

(3) Make an executable .exe from this vi (try with both SSE settings)

(4) Close labview and run this executable.exe (something like lvrt.exe in Labview 5, before you could build applications)

(5) Now from this executable, via the file->open menu, open a vi in the vi.lib (e.g. vi.lib\platform\system\beep.vi)

If you now get the same error as you are experiencing for the reason you visit this thread (the hex code in the starter topic and the error 59), there is a known solution but this requires some advanced tweaking. I contacted NI support and they were able to solve it. The request ID was #1315886.

So if you can reproduce the issue you are facing with these steps above.. there is a way out.