LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How can I repair a Generic file I/O error on opening a vi?

Solved!
Go to solution

I tried to open a vi while the folder the vi is in was being coppied to a backup location. I got a Generic file I/O error, and the vi wouldn't load. After the copy process completed, I rebooted, and tried again to load the vi. It still failed, so I tried to load the backup file, and it also could not be loaded. Is there anything I can do to save this file? I recently put a lot of work into it, and the working backup I do have is before any of the new work took place.

 

Thanks

0 Kudos
Message 1 of 11
(12,943 Views)
Solution
Accepted by topic author SciManStev

Are you able to open the VI at all? If you can open it, try copying the block diagram into a new, blank VI. Most likely the VI has become corrupted and pasting into a blank VI and resaving can fix the corruption.

 

Unfortunately if LabVIEW closes upon trying to open the VI and you are unable to access the block diagram, then it has become corrupt. There is no way to recover the VI or to extract certain parts of the VI from the file. The only solution is to start with a blank VI and reprogram the corrupted VI again. You may consider running a file recovery scanner on your PC to see if there is any part of it that is recoverable. Though it seems you will have to use your backup version.

 

Jordan G

Message 2 of 11
(12,909 Views)

Thank you! I was afraid of that, but I had to try anyway.

0 Kudos
Message 3 of 11
(12,900 Views)

Could you open the vi? I am facing similar situation and dont know what to do..

0 Kudos
Message 4 of 11
(11,670 Views)

The only thing I could do, was open a much older copy, and redo all the work. I lost quite a lot of time, but I learned to never try to open a vi while it was being coppied somewhere else. I regularly back up my vi's, and just sit idle until the copy is finished, or have the vi open before the copy starts and not try to save until it is finished. Another area to stay away from is trying to do something else when a vi is compiling for an executable. It is OK to do something else when an installer is created, but not when a vi is compiling.

0 Kudos
Message 5 of 11
(11,664 Views)
I just restarted with an old one. Anyway learned a big lesson.
Thank you for your valuable time.
0 Kudos
Message