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

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

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.

Similar Messages

An error occurred loading VI. LabView load error code 1: LabView load error code %ld: %p"

I have been developing a VI file that has
been working fine, until now. I am using 8.6.
Every time I attempt to open this file
I keep getting:
How do I fix the error code:
Labview: Memory is
full.
An error occurred loading VI. LabView load error code 1:
LabView load error code %ld: %p”
On a separate dialog:
“Not enough memory to complete this
operation.”
I ran VI analyzer which told that the
VI:
One or more errors occurred during
analysis.
Testing errors tab – Vi not loadable
and my file name. At the bottom in the error description I got:
“Error 74. Memory or data structure
corrupt. <my file path> and <file name>.”
Could not be opened.
Is there anything I can do to recover
the file?

Hi kevin_khan,
I went ahead and tried to open it and got the error attached.
Peter T
Applications Engineer
National Instruments
Attachments:
test.png ‏14 KB

LabVIEW load error code 1: LabVIEW load error code %Id: %p

One of my VI crashed while trying to save some data to file, I then tried to save the VI afterwards, but message with Out of Memory popped up again and the IV closed down. So now I can´t open my VI, then I try I get the "LabVIEW load error code 1: LabVIEW load error code %Id: %p" message and I have been given no opportunity to recover an older version of the VI then I close down and open LabVIEW again!!! So my VI is lost or what?
This is a huge problem for me, hope someone can help...
Regards
Jesper

Hi Jesper
For the future you should be good with LabVIEW 2012 (Normally realeased after NI Week in Austin in beginning of August). From what I know about this problem it have not been mentioned to be solved in a fixpack before release of LabVIEW 2012.
If you are reading in large files that uses more memory than avaliable and do wan't to avoid LabVIEW from crashing then you could add more RAM to your PC. If you are using Windows 32-bit you could try to edit the boot.ini file for Windows to allow Windows to allocate more memory to LabVIEW as explained in the following article:
Extending Virtual Memory Usage for 32-bit Windows
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/enable_lrg_ad_aware/
You could also try upgrading to Windows 64-bit this will allow much larger memory operations, and Windows 64-bit will let LabVIEW allocate more memory.
To use Source Code Control on your computer you will need:
1) A Source Code Control server with space to store the backup VI's and previous versions on (this can be your own PC). All Source Code Control providers that follow the Microsoft Source Code Control API. We have a list of tools that we have been tested that can be found here (note that some is free and other is not):
Which Third-Party Source Control Providers Can I Use with LabVIEW 8.0 and later?
http://digital.ni.com/public.nsf/websearch/26EC5904169430CE8625706E00743997?OpenDocument
2) After installing the server you need to configure LabVIEW to communicate with this server. In the article below under the section "Configuring LabVIEW to Call the Microsoft SCC API" you can see how to do this:
Software Configuration Management and LabVIEW
http://zone.ni.com/devzone/cda/tut/p/id/4114
3) You are good to go. Source Code Control uses the two most know functions "Commit / Check out." When you Check out a document you will be able to edit it, and when you then commit the changes then it will be saved with a new version number on the server. For each commit you will be able to select "Revert to previous version" to go back and restore a previous commited VI. You can use these functions on the VI it self or as I prefer from the Project Explorer.
Bisides the advantage of being able to restore previous versions, Source Code Control is also a great tool if your are multiple users working on the same project. You will i.e. be able to be 2 or more developers working on the same VI at the same time and then merging your changes to one VI when you are finished.
Best Regards
Anders Rohde
Applications Engineer
National Instruments Denmark

Building an Application in Windows to be used in Linux (with the Run-Time Engine)

Hi All,
I have an LabVIEW project I have developed in a Windows environment. I can create an Application (.exe) using the Build Specification -> Application Builder which works fine on the development platform.
I now want to distribute the application to a Linux Environment. The OS is openSUSE v10.3 (with GNOME). I have downloaded the two rpm files needed for the run-time engine and installed them, as per here:http://digital.ni.com/softlib.nsf/websearch/97E14BA3E0C14A89862572C300567733?opendocument&node=13207...
Now, the question is; how do I create an Application in Windows which can be used on the Linux Box? According to the Application Builder instructions, it's simply a case of removing the .exe extension in the Target File Name options, however, this gives an error "Invalid Extension."
If I do create an exe and manually remove the extention is doesn't work on the Linux enviroment (typing ./application).
Has anyone had experiance of this?
Many Thanks for Any Help,
Oliver
Windows XP SP 2
Labview 8.2.1
openSUSE v10.3 (with GNOME)
LabVIEW Run-time Engine Version 8.2.1 for Linux

The cross-platform nature of LabVIEW refers more to the code than to the executable.
LV (given the appropriate development version) can compile the same source code into a Windows (using LV for Windows), Linux (using LV for Linux) or Mac (using LV for Mac) program.
This means you will still have three versions of your program, one for each platform.
If you want to distribute VIs (without block diagrams), you will also need different versions of these as without the block diagram, they cannot be re-compiled for a new platform.
Shane.
Say hello to my little friend.
RFC 2323 FHE-Compliant

LabVIEW load error cod %ld: %p

All of the sudden, when I tried to open a VI, I got an error message that said, "LabVIEW: Resource not found. An error occured loading VI 'VI name.vi". LabVIEW load error code 1: LabVIEW load error code %ld: %p". I tried to revert that particular VI to the previous version through source control, but that didn't help. Does anyone know what I need to do to fix this? Thanks!
Kudos and Accepted as Solution are welcome!

It was fine, and now I can't open the VI. It is possible that I forcefully closed the VI a few times with ctrl+alt+del. The name.vi is the host vi for an fpga application. It interacts with user, calls .NET DLL to communite with a DUT, pass data to/from FPGA, etc.
I had already looked at the link that you posted. Not sure does it apply to me.
Kudos and Accepted as Solution are welcome!

Why I get Labview load error code 16?

"Labview load error code 16 preventing me from opening the VI"
"I'm having some problems opening a particular VI. I get an error called: "Resource not found"; "Labview Load Error Code 16; Could not load data space link information." This VI cannot be opened, but I would like to somehow get into it (some important codes are in it). The Labview version is 7, the size of vi is about 1.08 Mb, and the system is on a Windows 98. Thanks in advance."

Hello James,
Thank you for contacting National Instruments.
Try opening the VI with another version of LabVIEW. You can also try placing the VI as a subVI and then viewing its block diagram.
You're also welcome to post your VI, and we can try to open it up here.
I hope this helps!
Matthew C
Applications Engineer
National Instruments

What can I do about "LabVIEW load error code 38: Failed to uncompress part of the VI."

While attempting to load an executable LabVIEW application for LabVIEW 2009 SP1 on a Windows-XP machine when the following pop-up message occurs. "LabVIEW: Memory or data structure corrupt. An error occurs in loading VI 'NI_Gmath.lblib: Backward Bracket Search.VI'. LabVIEW load error code 38: Failed to uncompress part of the VI. The VI is most likely corrupt." What seems odd is that the same LabVIEW application loads fine when logged on as a privileged user account, but fails to load on a private user account.
Attachments:
2012-07-18 LabVIEW Load error code 38.jpg ‏1314 KB

Here's a thought:
So when something is decompressed, a temp folder is often used.
I have no idea why LabVIEW would be decompressing anything, but I suspect it is trying to put the decompressed file into a temp folder where the user does not have write permissions.
In the .ini file for your executable, you can add a line that specified the location of the temp folder to use:
tmpdir=C:\Temp
On my Win7 machine, the location is:
C:\Users\MyUserName\AppData\Local\Temp
On WinXP, it is probably:
C:\Documents And Settings\YourUserName\local settings\temp
Try changing the tmpdir key in your ini file to something to C:\Temp and see if that helps.
- john

LabVIEW load error code 10?

Hello..
I have received an .llb file from support at Anritsu, for a Wiltron 56100a Scalar network analyzer. It contains numerous priceless VI's. Unfortunately, when I try to open it, I get an error..
"An error occurred loading VI ''. LabView load error code 10: VI version (3.1) is too old to convert to the current LabView version (6.1)"
Is there any way I can convert this code at all? It would be most valuable! Would it be possible to get ahold of an older labview version, perhaps 4 or 5, convert to that version, then convert to 6.1? We really need these drivers..
Thanks for any suggestions!

Go here
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=0
Click on "become an Enthusiats".
Write a short bio,
Indicate what catagory,
Submit!
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Labview load error code 15 preventing me from opening the VI

I'm having some problems opening a particular VI. I get an error called: "Labview Load Error Code 15; cannot load default data." This VI cannot be opened, but I would like to somehow get into it (some important codes are in it). The Labview version is 6.1 and the system is on a Macintosh G3 with OS 8. Thanks in advance.

It sounds like the VI is corrupt. Are you able to open it another machine or a different version of LabVIEW?

Labview load error code 10:VI version (8.2b23) is too old to convert to the current

trabajo en la version de LabVIEW 8.2, 20th aniversary edition, Professional y cuando intentaba abrir la parte de examples en la primera ventana me aparecia el siguiente error:
LABVIEW:VI version is too early to convert to the current labview version.
An error occurred loading VI "find examples.vi".
Labview load error code 10:VI version (8.2b23) is too old to convert to the current
labview version (8.2.1f4)
luego de la primera intaslacion de la version 8.2b23 tambien me salia el mismo error, desintale y reinstale pero igual, asi que probe instalar un parche que actuliza a la version 8.2.1f4, pero como ven sigo con el mismo problema ademas de intentar mass compile pero no me funcina al parecer son muchos VIs que hay que compilar... tambien busque el LabVIEW conversion kit, pero son para versiones demasiado anteriores agradeceria me ayudaran a solucionar este problema.
MUCHAS GRACIAS
ATT: Carlos Andres Rosero, Colombia

According to this, 8.2b23 is an illegal, bootlegged copy of LabVIEW.

Labview load error code 21

I have a VI which includes subvi for vision utilities like IMAQ winddraw, wind close etc. I build the exe file for the main VI. What extra files should I include in the exe generation? since when I build the exe file normally and it generates the error labview load error code 21. what other extra files should I inculde?

This should answer the question I think:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/f695b089e3b1cd3286256a4000702136?OpenDocument
MTO

Will hardware drivers work with the run-time engine or only a full version of Labview?

Hello.
I'm trying to get a quatech I/O card to work. The instructions with the drivers we were given state "you must have labview installed before installing these drivers".
A program I wrote on my machine works fine with those drivers and does toggle outputs on the card, but when I build it into an executable on our test unit (doesn't have a full version of Labview, just the Run-Time engine) the card doesn't work.
We installed the run-time engine on the unit, then the drivers.
I guess my question is: Do most drivers work with both the full version of Labview and the run-time engine? Or do I need to somehow 'convert' these drivers to work with the run-time engine?
Th
anks for your help!
Dave Neumann
[email protected]

Dave:
I can't determine which dll is required but if there are more than one that
shipped with the quatech I/O card try to placing one dll at a time in the
same directory as the exe so that you can determine which one is the
required one. If that doesn't do it then it may need more than jsut one of
the dlls so placing all that came with the quatech I/O card s/w driver
package in the same directory as the exe should do the trick.
Best of luck.
-Tom
"Neumannium" wrote in message
news:[email protected]..
> Tom,
>
> Thanks for your reply. One of the problems I'm having is figuring out
> which .dll I would need to include (I'm not a software guy).
>
> Would the .dll your speaking of be different th
an the one which is
> installed with the drivers? I'm looking at a .dll that is installed
> when you install the labview drivers for this card, but the run-time
> engine still doesn't want to get the card to work. (The file installed
> when I install the drivers is called 'daqlv32.dll' and I don't know
> how to find any other .dll's I might need)
>
> Actually, it appears the card 'is' being seen by the run-time engine,
> but I'm getting impulses rather than distinct changes of state.
>
> Anyway, thanks for the help.
>
> Dave Neumann
> [email protected]

Installer LV7.1 - LabVIEW load error code 21: An external subroutine required for execution could not be found.

Bonjour,
Je cherche à créer un installer portatif utilisant les drivers NI-DAQmx 8.7.1 et NI-CAN 2.6.0.
Je dispose d'un code LV 7.1 et j'ai installé l'application builder 7.1.
Mais une fois l'application installé sur un PC vierge de Labview, j'obtiens le message suivant:
load error code 21: An external subroutine required for execution could not be found.
Ce message est répété plusieurs fois (pour différents VIs) puis le programme ne se lance pas.
J'ai bien veillé à installer les drivers NI-CAN et NI-DAQmx correspondant au préalable sur la machine cible.
En chercant sur le forum, plusieurs pistes m'ont été proposé:
La version NI-DAQ
L'intégration du Run time Engine
Un problème de DLL
J'ai vérifié ces 3 points mais cela n'a pas règlé mon problème.
Résolu !
Accéder à la solution.

Bonjour,
Merci de ta réponse.
En fait, j'ai bien inclu le runtime engine de Labview qui était effectivement la source de l'erreur.
L'installation de NI-DAQmx v 8.7.1 provoque la mise à jour de la version du runtime engine (passage de 7.1 à 7.1.1).
J'ai donc désinstallé Le runtime engine 7.1.1 (ce qui a provoqué la désinstallation de labview et NI-DAQ).
Puis je suis passé par une version plus ancienne de NI-DAQ (7.2) que j'ai adapté (inclusions de DLL et de VIs).
Les messages d'erreurs ont alors tout simplement disparus!

Labview 7.0 is compatable with Labview Imaq6.1 , vision builder 6.0 and Imaq run time engine 6.0.

Sir,
My system is PXI 8174 and i an using NI 1411 card for my application. I want to know the compatability of the softwares. Whether Labview 7 is compatable with Labview Imaq 6.1 , vision builder 6.0 and Imaq run time engine 6.0.

Hi,
Assuming you meant IMAQ Vision 6.1 instead of IMAC 6.1, this software was intended to run on LabVIEW 5.1, 6.0, and 6.1. I have heard of it being used with LabVIEW 7 on occasion, so it may be possible to make it work, but this has not been tested and is not officially supported. Vision Builder 6.0 should run; however, it was developed long before LabVIEW 7.x and will not generated code for LabVIEW 7.0 and later. The Vision RTE version should correspond to the version of Vision you are using. For instance, if the program was developed with Vision 6.1, the computer should have the Vision 6.1 RTE installed. With this being said, if you plan to use LabVIEW 7, I recommend updating your other software.
Regards,
Ryan M.
Applications Engineer

What is LabView load error code 34?

I'm using the 30 day evaluation version 7. I created a very basic instrument I/O .vi to test the capabilities of the software. The .vi works fine on the development machine, but when I try to open it on a different machine, which has the LabView 7 Reader installed, I get the above error. I'm guessing it's because it is a trial version, but I want to make sure I'm not missing anything.
Thank you.
Jack Remiasz
Industrial Measurement Systems, Inc.

Karra,
I believe that the following Knowledge Base entry answers this question:
"LabVIEW Error Code 34 when opening a VI in the LabVIEW Player"
Any VI that we open in the LabVIEW Player must be signed. Error 34 will pop up when we try to run a non-signed VI. We can sign our VIs by using the LabVIEW Professional Development System 7.x and the LabVIEW Player VI Creation Toolkit. Please refer to the link above for more information. Hope that helps!
Craig H.
NI Applications Engineering

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

Similar Messages

Maybe you are looking for