02-25-2009 06:29 AM - last edited on 03-02-2009 08:50 AM by Support
I was developing a project in Labview 7.1 and had saved it on vista when the vista OS decided to enter suspend, Labview 7.1 stopped responding as a result and I had to reboot. I will never trust vista again but when I try to open the VI I get the following error:
Fatal Internal Error : “objheap.cpp”, line 579.
And the following text file report is created. What I am wondering is there any way to restoring or uncorrupting this VI which is attached. Sub VI’s are not included but if you can get the VI to open even without them then the problem is sorted.
####
#Date: 25 Feb 2009 12:13:28
#OSName: Windows NT
#OSVers: 5.1
#AppName: LabVIEW
#Version: 7.1
#AppKind: FDS
D:\lvmerc\src\source\objheap\objheap.cpp(579) : DAbort: Heap has insane block size
$Id: //labview/branches/Mercury/dev/source/objheap/objheap.cpp#3 $
0x009DFC85 - LabVIEW <unknown> + 0
0x007080AC - LabVIEW <unknown> + 0
0x007079E1 - LabVIEW <unknown> + 0
0x00A66716 - LabVIEW <unknown> + 0
0x00706B02 - LabVIEW <unknown> + 0
0x006073AE - LabVIEW <unknown> + 0
0x0070532B - LabVIEW <unknown> + 0
0x00A653E5 - LabVIEW <unknown> + 0
0x00A66911 - LabVIEW <unknown> + 0
0x009ED231 - LabVIEW <unknown> + 0
0x005ADED7 - LabVIEW <unknown> + 0
0x004B7F79 - LabVIEW <unknown> + 0
0x004B7EA7 - LabVIEW <unknown> + 0
0x004B7CF9 - LabVIEW <unknown> + 0
0x004B8492 - LabVIEW <unknown> + 0
It also managed to corruptly my library file for the project which I cannot open also and is attached,
Thank you
02-27-2009 04:01 AM
Hello Paul,
I have been looking into your error code as well as the attached files of your VI and LLB. Pasting in your error code is proving very helpful in trying to help you. I initially tried to open your files in my system, where I would possibly be able to resave them for you, however it looks like I will have to try a different approach.
As I understand it, you have been using LabVIEW 7.1 Full Development System with Windows Vista. LabVIEW 7.1 was released during the years when only Windows 2000 and XP were available. With the release of Windows Vista in later years, National Instruments produced LabVIEW 8.2.1 with support for Windows Vista Business or greater.
Please reply with the following information:
Are you using Vista 32-bit or 64-bit?
Are you still able to open the LabVIEW Development Environment to produce new VIs?
Have you tried to open other VIs (after backing them up) with LabVIEW 7.1?
Regards,
02-27-2009 06:56 AM - last edited on 03-02-2009 08:51 AM by Support
Thank you for your time on this,
I am using Vista 32 bit and the labview environment installed on the computer is working fine. It will open and save VI’s without error as long as vista does not go into suspend when a VI is open which is what caught me out. I know labview 7.1 is not designed for vista and we have purchased the latest version of labview from yourselves through Seamus here in Ireland, however I have not updated it on my computer but will do now. Thinking about this I would say its more a corruption caused by vista trying to enter a suspend mode and saving data to disk as opposed to the labview environment itself saving and corrupting VI’s which has always worked perfectly for me.
Paul Clarke
03-02-2009 11:56 AM
Hello Paul,
I have looked into your VI and Library files that you have sent. At the moment, from my research, I have seen that it is not usually possible to recover a corrupt VI. Once the error occurs, the only solution is to rebuild a new VI. You will have to look for a backup copy of your VI, if you have one, and make your latest changes to it.
In terms of recovering library files, that has often had some small success, depending on the level of corruption. I am currently looking into that, and I will see if I can make an internal changes to the file that may allow us to open it.
Have you upgraded to a later version of LabVIEW for use with Vista? It is advised that you also backup all of your VIs before using the newer development system.
Regards,
03-10-2009 04:56 AM
Hello Paul,
I wanted to verify that I have tried to correct you Library file, however, it seems that it is unrepairable as well. Sometimes, it is possible to try and repair a library or project file by editing some of the Markup Language that composes it. However, when opening your file in an editor, the internal data is also corrupted.
Regards,