Generic file I/O error, the file is not a valid labview file

[divya]

Hi,

I have created a project in LV 8.0. Now I am getting the following error when I try to open it...'Generic file I/O error, the file xxxxx.vi is not a valid labview file.' I have tried to open all the subvi's used in my application and I am able to open all of them.

I found that this condition may occur if the hard disk is full. So I tried to open my vi from another PC but I am getting the same error everywhere. What am I supposed  to do ?? Please help me out if anyone has a solution to this...

Regards,

Divya

[DuffmanSays]

Hello Divya,

Do you get this error when opening the project file or the main VI in your application? I ask because it may be possible that a VI can become corrupt. I am surprised that it says "Generic File I/O Error," but can you recall any circumstances under which this VI may have become corrupted?

Do you have a computer running LabVIEW 8.2? I would be interested to see if this version would successfully open the files. If this is something you might be able to post, I can attempt to open the project or VI in LabVIEW 8.2. I hope this is useful for you. Thanks,

Mike D.

[divya]

Hi Mike... Thank you for your reply...

I get this error when opening the main vi in my application. I can't recall anything which may have corrupted the file. The earlier version of the main vi of which I had saved a copy does not give any problems while opening. I had made many changes in the next version of my application which is lost now... Do you think that the file may be corrupted? Is there no way to retrieve it?

I do have a system running LabView 8.2 and I have tried to open this file with that version. But I am still getting the same error.

Divya

Message Edited by divya on 03-22-2007 10:42 PM

[parthabe]

Hi Divya,

Check if the VI's size is > the one U re stating as Ur earlier version, without that so many changes. If it >, it may not ve got corrupted. Problem could be something else.

Else, if it shows some drastically low size ( like too less kb ), then it has got goofed up completely. Can U recall if there was some power breakdown related things when U were working on it as unsaved condition...

Why I'm telling U this is in my off, when I was working on a 26-28 MB sized VI, one guy tripped of the main switch unknowingly.

I had lost itcompletely. But U can retrieve it by looking for it in the Documents & Settings\User(Current User)\Local Settings\temp, or in that hierarchy in some hidden folder, it would ve got stored in some bizzare name, say alphanumeric name, with the correct size.

If U run this, it ll perfectly run & also the size ll be ok too...

Try it out & update here soon.

[divya]

Hi Partha,

This condition has occured after a power breakdown. I had already saved my vi but it was open when there was a power breakdown.

But my file's size is not drastically small like what happened to you. I tried to find it in the Local Settings\temp folder but I could not find it at all. What will the extension of the file be in the temp folder ? Is it ' .vi ' ?? or will it be some other extention ??

Thanks,

Divya

[parthabe]

Hi Divya,

They re most probably stored as .vi extension only, I think... But names are bizzare !

I ve attached a screenshot of what I ve got presently in that folder. See those names & infer accordingly.

Do remember that it is a hidden folder, so U ve to modify the settings in the Folder Options tab of the Windows explorer, & retrieve back those settings after U analyze the folder, to avoid the risk of others meddling with that folder...

Hope this helps U.

[divya]

Hi Partha,

I have tried to look in the temp folder as you told me to. You are right, it is a hidden folder. But I did not find any vi which was of the same size as my file... I sorted all the files in the temp folder by date but could not find any vi on that specific date which means that it was not saved in the folder right ??

Thanks,

Divya

[parthabe]

I ve really run out of answers. sorry...

Someone else has to pitch in with an alternate solution.

Good luck !

[divya]

Its OK... Thanks for taking interest ...

Divya

[DuffmanSays]

Hello Divya,

While I have not heard of an instance such as Partha's, a power failure is definitely the kind of circumstance that may cause a VI to become corrupted. LabVIEW 8.2 actually has an auto save feature that allows you to recover VIs after such an occurrence, but if you were working in LabVIEW 8.0, the VI may not be recoverable. In any case, I'd still be interested to take a look at this VI. If it is not something you can post here on the forums, I would suggest emailing in for National Instruments support. As I mentioned, there may not be a way to recover this VI from corruption, but I'd like to be sure that this is the case. Thank you very much for your time, and I apologize for this inconvenience!

Mike D.
National Instruments
Applications Engineer