Labview save error code 3: FP heap

Since installing SP1 for Labview 2011 I've started getting this error from time to time:
So far I've been lucky and not lost much work due to this, but I'm sure it's just a matter of time. I haven't made any significant effort yet to try and find what circumstances cause it - can anyone shed any light on it?

Spruce wrote:
Since installing SP1 for Labview 2011 I've started getting this error from time to time:
So far I've been lucky and not lost much work due to this, but I'm sure it's just a matter of time. I haven't made any significant effort yet to try and find what circumstances cause it - can anyone shed any light on it?
Do you have very big typdef control because I have encountered the same error when I tried to duplicate one of my giant cluster and saving the vi.
The best solution is the one you find it by yourself

Similar Messages

Labview 2009 save error code 3 : FP heap.

Hello experts,
I'm currently trying to upgrade from Labview 8.6.1 to Labview2009. At the moment, I'm having problem saving vis which were O.K with version 8.6.1.
And it appears a lot of vis affected by this error. I was wondering if it is a bug of Labview2009 and better stay away until it will be fixed? Thank you.

Hi NitinD,
It feels like some of the typedefs are causing troubles rather than VIs themselves. I attached one of the typedef which I still get this save error in LabView9.0.
Cheers.
Attachments:
SA info.ctl ‏9 KB

Known causes for Error Code 5: BD Heap

I spent a few hours this morning fighting with an internal error code 5 BD Heap error every time I tried to copy a section of my block diagram and save it, and finally figured out the sole source of my problem:
When copying sections of the block diagram, never copy a structure that contains a feedback node whose initializer lies outside that structure, unless you find the initializer and select it too.
I think this also counts as an "Insane Object" error. You can also fix it by deleting the feedback node and replacing it but if I tried to do this after a save attempt LabVIEW fatally crashed; so I'd suggest you do it as soon as you have copied the code, before you try to save anything.
If anybody has other known causes for this error, please post them for the benefit of others here.
Ryan R.
R&D

Hi, Ben,
I have the same error (see attached images). I have no idea how to do with it.
And my code is not even finished, whenever I made some change, it said save error code 5 bd heap.
What can I do? Please help.
Thanks
nan
Attachments:
Capture10 3 a.JPG ‏16 KB
Capture 10 3 b.JPG ‏16 KB

Save Error code 44

Hi all,
I am using labview 13.0 and I'm trying to save my project in another location using "Save As->Duplicate .lvproj file and contents" with all dependencies. I select a location on my computer and it starts running. After it has run through a few files, I get the following error:
Labview: Generic file I/O Error
Cannot save class "setMaximumHeaterPowerMessage.lvclass"
Labview save error code 44: could not move temporary file to destination.
I press OK and it asks me to select an "Emergency Backup Destination for "setMaximumHeaterPowerMessage.lvclass" I do so and then get:
Labview: Generic file I/O Error
Cannot save class "setMaximumHeaterPowerMessage.lvclass"
I press OK and the saving process stops.
Googling the problem only led to a couple articles talking about virtualbox, which I am not using. I have enough space on my hard drive.
Does anyone know what is causing this problem and how I can fix it?
Thanks in advance
Solved!
Go to Solution.

Believe it or not but, it was because the path names of some files were too long

Save error code 48

I'm running LV in Classic on OS X 10.2 Been working great for months. Last night, LV decided it can't save my files anymore. I get the following message: "File permission error occurred. LabVIEW Save error code 48: Could not move temporary file to destination."
Worse than not being able to save, LV then erases the original. I really need help with this one! Thanks in advance

Hi. Thanks for your response. This was strange problem in that I have been using LabVIEW for months on my machine w/o this issue arising. I think what might have happened is that my last update of virus definitions might have done something (Norton Antivirus) as the problem started right after that.
I did re-install LabVIEW but to no avail. What did work was giving myself administrative priveleges on the computer. I'd rather not run it that way. I would like to keep my regular account free of administrative power as the kids sometimes jump on there. So, it is working now, but if you have any other thoughts to let me return to my previous settings, I'd appreciate it. Thanks.

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

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: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 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

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 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

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

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?

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 save error code 3: FP heap

Similar Messages

Maybe you are looking for