LV2009f2 vi corruption

[viScience]

Hello all,

I have a rather dire situation in which a top level vi that was being run from the project was corrupted. If I try to open it I get the dreaded error code 3 - could not load from panel.
I had been running the vi for several hours and then stopped it normally. I then tried to do a build and it failed. I was late to pick up my son so I did not read all of the details of the error message but rather as I do every night did a backup. This morning I find that the vi is corrupted, the backup now is corrupted and the last exe has been wiped out since the build failed. The vi looks ok from the file size so I have some hope that NI might have tool to analyze the problem and fix it. Does anyone have any comforting words of hope to share?  I am also attaching the vi in case some kindly NI person may have diagnostic tools to fix it.

[Ray.R]

I fear that the news is not good.  It is corrupted. 

I would wonder why your backup got corrupted and the exe dissappeared?

- strange -

[LV_Pro]

It is possible that NI can look at it, might have a means to determine what is corrupted, but I would go through the "real" problem resolution channel for that, this thread should get a look by an NI engineer, they are tasked to look at unresolved questions, but it isn't the official path.

Ray, he lost the exe when the build attempt apparently overwrote the original, and lost the backup when he, in haste, backed up the corrupted one. Been there, done similar.

[Ray.R]

outch!

Murphy's Law for sure...

Not sure if NI can help.  When it happened to me I was outta luck...

That's why I now zip backups and date them.....  every day..

[viScience]

I have an AE helping with this now and am awaiting a response from NI R&D.

Lessons learned:

1. Will now use SCC (TortoiseSVN) so that my daily backups are revisioned

2. Will use my existing backup tool to backup the SVN repository.

[pallen]

Been using TortoiseSVN since I started working at a new place.  (All the way across the street from the last place)

It's a great tool.  But I'm still going to be creating zip backups of every version before I commit.   I've run into a number of weird problems with Tortoise and if I hadn't had my backups I'd have lost quite a bit of work.  

[viScience]

Could you be more specific?  If you cannot rely on Tortoise to keep revisions then you might as well throw the whole thing in the trash.

[waldemar.hersacher]

What configuration do you use? Lokal, SVN server or Apache integration?

We have never lost any files within the last three or four years we are using SVN. Today we use TortoiseSVN as a graphical frontend. But we are testing PushOK which will integrate SVN into any SCCAPI enabled appplication like LabVIEW and others.

So you wolud also like to hear what went wrong in your case.

[falkpl]

If you are running vista (XP might also have this) if you get the properties of a folder (right click>>properties, goto previous versions tab) and look at previous versions a backup is periodically made.  This saved me once where I forgot to make a zip of the code and it got corrupted, I was able to get a backup from just hours earlier.

[pallen]

It's very likely a problem with the operator and not the software.

Just yesterday I ran into trouble after I had reverted my code to an older revision.  I made changes to the reverted code, and then tried to commit those changes as a new version.  

I thought everything went alright.   It wasn't until I was working from home yesterday that I realized that my main VI was broken because several of my SubVIs had not updated correctly.  I'm not sure where my new versions ended up.  But if I hadn't had the zip  backup I think I would have lost them and about 8 hours worth of work.  

I'm pretty sure I did something incorrectly by rolling back to an older version and trying to continue from that point.  Perhaps that should have been a branch?  I'm really not sure.  I do know that I tried several times to re-commit the "good" code I had.  But that Tortoise simply wouldn't let me put that code as it was into the existing repository.   It would force me to update.  When I did update, it didn't matter how I resolved the conflict  ("use thiers" "use mine" etc.) the result was that I always ended up with something missing.  

Today I exported my working code out of the repository and then created a new one.  So far..it seems alright.  But as a result, I don't think I'm ready to give up the backup that I know works.