LabVIEW 8.5 Development System error message on VI start

[MR2068]

Hello,

I have an issue with LabVIEW 8.5 not opening a VI that previously was in use with no problems.  When the VI is started, a dialog box titled "LabVIEW 8.5 Development System" is displayed over the LabVIEW splash screen.  The text shown in the dialog states, "LabVIEW 8.5 Development System has encountered a problem and needs to close.  We are sorry for the incovenience."  The technical information includes Code: 0xc0000005 under Exception Information.  I am running Windows XP Professional Version 2002 Service Pack 3.  The same error is displayed when I try opening the VI on another computer running Windows XP Professional Version 2002 Service Pack 2.  Is there a work-around for this error?  I tried placing the VI on the block diagram of a blank VI and got the same error.

[SunainaK]

Hi MR2068,

When this VI was priorly in use, were you using the same computer and version of LabVIEW? Was there anything you changed on the VI, before you opened it again?

[MR2068]

Hi Sunaina,

Thanks for the reply.  Yes, I was using the same computer with the same version of LabVIEW when this VI was in use.  I did not change anything in the VI prior to the problem, however, there has been an issue going on with the VI for some time.  Whenever the VI is closed a dialog box comes up informing of unsaved changes.  The options are to save, don't save, or cancel.  Usually I click don't save and the program closes.  This time another user was using the program and save was selected.  The program was unable to be opened after this.  I loaded a previous version of the program (a few revs behind) from a backup.  This program also has the unsaved changes problem.  The changes listed are VI recompiled and SubVI call(s) modified.  No matter how many times I select save, the changes always appear the next time the program is closed.  Could something have been corrupt in the program from having unsaved changes for a long time?

Thanks

[SunainaK]

Hi MR2068,

I think doing a mass compile of the backup VI may allow for you to not see this unsaved changes each time.

This document: http://digital.ni.com/public.nsf/allkb/654877E62A97B72986256C95006F9B24 walks you through how to do a mass compile. 

[MR2068]

Sunaina,

Thank you - I will try the mass compile on the backup.  Is there any chance of salvaging my latest revision program that crashed?  I would at least like to see the revision history notes so I can restore the changes that were lost with the latest program.

Thanks again.

[SunainaK]

Hi MR2068,

It looks like the Revision History is stored within the VI. I am very sorry about that.

http://zone.ni.com/devzone/cda/tut/p/id/9924

[MR2068]

Hi Sunaina,

I wanted to share a work-around to retrieve the Revision History that my intern discovered.  He was able to open the VI in a text editor.  Even though only garbled text was visible at the outset, he searched for some key words he knew would be present in the actial revision history text.  The text editor found these words - the revision history was actually present in the text version of the VI.  He then parsed out the revision history from the rest of the VI and created a document was just the actual text of the revision history.  Thanks for your help.

[SunainaK]

Hi MR2068,

Thank you for posting this to the forums! I am also glad to hear you were able to recover your revision history.