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

[Randall_T]

I use a vi compiled with a run time engine to run separate vi’s in my application directory. Once a file association is made with this exe file any Vi in my application directory is available to be loaded as needed. This is a process that has been very successful for me over the years and would prefer to continue using this process. Most of my applications are running in LabVIEW 8.6 and have moved them to 2009. First indications are in 2009 this process is still working. However, I plan to go on to 2010 before upgrading my test stations.

In 2010 I get the error 59: “The source file’s compiled code has been separated, and this version of LabVIEW does not have access to separated compiled code.”

The same dialog box also presents, (Hex 0x626)  “Cannot open a VI with separated compiled code in a Run Time Engine that has no access to the VIObjCache.”

What can I do in the build that will get around this error?

Thank you

[Verne_D]

Hi Randall,

Could you post a small example that demonstrates this error? I'm not finding a ton on information about this coming up in the circumstances you're talking about and it might help me offer further advice.

[Dennis_Knutson]

As the help says

Note  The LabVIEW Run-Time Engine cannot compile code. If you intend to load or run a VI using the LabVIEW Run-Time Engine, do not separate compiled code from the VI.

Uncheck the 'Separate compiled code from source file' option in VI Properties and try it.

[Randall_T]

---

@verne D wrote:

Hi Randall,

Could you post a small example that demonstrates this error? I'm not finding a ton on information about this coming up in the circumstances you're talking about and it might help me offer further advice.

---

Here is a zip file with what I believe provides enough information to repeat this. I have also turned this into a service request but there is no solution yet.

The read me file included explains a little bit more about the setup.

Thanks for your help.
 

[Randall_T]

---

@Dennis Knutson wrote:

As the help says

Note  The LabVIEW Run-Time Engine cannot compile code. If you intend to load or run a VI using the LabVIEW Run-Time Engine, do not separate compiled code from the VI.

Uncheck the 'Separate compiled code from source file' option in VI Properties and try it.

---

Thanks for the suggestion. I have not found any code with this option selected. I posted an example of two files one that reads a text file and works fine. The other just has the simple error it gives me the error when loaded.

I do appreciate you taking time to help.

Thanks

[EWiebe]

I had the same issue.

This helped for me:

The error which was shown on Target Machine (where only the LV-RunTime is installed) told me:

(see attachment1)

So I searched for "Simple Error Handler.vi" in my project (including vi.lib)

And found thatit is used in :Simple Error Handler:

So I searched for Simple Error Handler.vi

and found under "C:\Programme\National Instruments\LabVIEW 2011\vi.lib\Utility\error.llb\General Error Handler CORE.vi"

I opened the "C:\Programme\National Instruments\LabVIEW 2011\vi.lib\Utility\error.llb\General Error Handler CORE.vi", looked into its properties and saw that the checkbox "Separate compiled code from source file" was checked.

I unchecked it, created EXE again, and it is running on the target now.

[Randall_T]

Thank you for the solution. I am sure this works until the next vi in the vi library gets this option selected.

 The bigger issue is I was doing something that National Instruments did not support. When I started in the days of LV 4.0 it was recommended to me that I use this method as virtually all my applications were for in house projects. This is still my preference because it gives the most versatility and allows modifications of single files rather than compiling the entire application.

The final solution I ended up with for those who may be having the same issues. My recommendation for what it is worth, is to compile the application as an executable. This is from what I can tell the only acceptable and supported method. Using this method the problem is solved.

I have accepted this as the solution. I still don't like it. I could list the reasons why but it is a mute point.

Thanks again for taking the time to respond to this issue and offer the solution you found.

[Holm]

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

[emherrma]

I had this same error on a project I was working on. So I tried to do the same thing to fix it and unchecked the box. Now I get a an error 14. "Could not load data space type map". Ugh.

[JasoNI]

Hello,

I noticed that you have emailed in about the error 14 issue as well. We can communicate via email and post what we find on the forum so that others are able to use the information as well.

Jason

Applications Engineer