04-21-2016 12:38 PM
Hello,
I am running Labview 2014 on Windows 7. After closing my VI, I suddenly can't seem to be able to open the VI again. I get the error message "Unable to open file - End of file encountered". I have seen a similar situation on the forum ( http://forums.ni.com/t5/LabVIEW/Can-t-open-Vi-end-of-File-Encountered/td-p/3197399 ) but have not seen a satisfactory solution or an explanation of a possible cause of the error. I have attached the VI file that I can't open.
Any help appreciated, thanks a lot in advance!
04-21-2016 01:00 PM
It won't open for me either.
The file must have been corrupted somehow. Maybe someone from NI can peek into it to see if there is anything specifically wrong that can be fixed. But otherwise you'll probably have to go to a backup copy you've saved and work from that one.
04-21-2016 01:24 PM
The attachment size is 1KB, which makes it likely there's nothing to do with this file any more. Since you're asking the question, I'm going to assume you're not using source code control, which you should. SVN is free and easy to use, but there are other options.
If you don't have your own backup, current versions of Windows do automatic versioning of files. This appears to be tied to the system restore feature, so if your files are on the system drive, it's likely you can get a copy of the file from the last restore point created by Windows. You can check by right clicking the file or folder in Explorer and selecting the restore previous versions option.
04-21-2016 09:43 PM
Thank you both for your replies. I don't have a backup file for this particular VI, unfortunately, so I guess I will either look into Windows auto-save features or re-write the VI.
04-22-2016 10:14 AM
@ovincent wrote:Thank you both for your replies. I don't have a backup file for this particular VI, unfortunately, so I guess I will either look into Windows auto-save features or re-write the VI.
Yes and while you're at it be sure and investicate SVN or some other source code control system. Even for single developers it can be a life saver.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
16 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
04-22-2016 08:21 PM
So it turns out that Windows backups were not activated so I can't recover the file. Anyway I am not very familiar with the concept of source code control. Is this a backup strategy? I have searched the web for "source code control" and the results were not very clear to me.
Thank you all for your help.
04-23-2016 10:26 AM - edited 04-23-2016 10:26 AM
@Hooovahh wrote:
@ovincent wrote:Thank you both for your replies. I don't have a backup file for this particular VI, unfortunately, so I guess I will either look into Windows auto-save features or re-write the VI.
Yes and while you're at it be sure and investicate SVN or some other source code control system. Even for single developers it can be a life saver.
Not only does is it a lifesaver, it allows you to be pretty fearless and strike out in different directions (branching) knowing that if you reach a dead end, you can always revert back to the trunk and start again.
05-02-2016 10:50 AM
Yet I still use disabled diagram structures when attempting changing some strategies in software, but yes I agree that changes when using SCC can be made with less regard.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
16 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
05-02-2016 11:20 AM
Your file is nothing more than a text file containing a line with four numbers (15.502 10.005 8.000 0.651).
This was never a LabVIEW program, just some random file renamed with a VI extensions. There is nothing to recover. In the worst case, you overwrote the actual VI by accident, so go back to your backups and get the original.