LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

generic file i/o error

I have Labview 8.5.1 and I'm trying to save as a duplicate hierarchy to a new location and I get a brief message that says something about the path being too long, and then I get a dialogue box that says: LabVIEW: Generic file I/O error. I need to save a duplicate hierarchy so I can upload my .VI and get some help on it, but this is making it difficult.

0 Kudos
Message 1 of 12
(4,983 Views)

Had a search already? Please post back if you are still facing the problem.

 

Mathan

0 Kudos
Message 2 of 12
(4,944 Views)
Yeah, I've had a search but can't seem to find the same exact problem that I'm having. In the past I have saved duplicate heierarchies and it seems to save my .vi in one folder and then all the special files from the toolboxes I've used in the .vi in a seperate folder so it can be opened and viewed by someone without those toolboxes. This time around it just seems to save my .vi without the rest of the stuff.
0 Kudos
Message 3 of 12
(4,929 Views)

Hey bcglaxer,

 

At first glance it looks like maybe the file path you are trying to use to save your vi is simply too long. As I recall, the Microsoft Windows limitation for the total length of a path is 255 characters, so it would make sense that if you have a particularly long file path that you might see this error. It is also not a stretch to figure that your actual vi may not exceed this limit and is thus saved just fine, but the additional files from the toolboxes being saved to a separate folder could have exceeded that limit. Thus, displaying the 'file path is too long' message and the generic I/O error.

 

What happens if you change the path of the vi you are attempting to save to another location that would be well within the 255 character limit, say your desktop. Do you still receive both messages you mentioned in your first post?

 

If you are still experiencing this problem, perhaps a screen shot of those warnings and error messages will help.

 

Hope this helps,

 

-Ben

Hope this helps.
-Ben

WaterlooLabs
Message 4 of 12
(4,909 Views)

BCho wrote:

 

What happens if you change the path of the vi you are attempting to save to another location that would be well within the 255 character limit, say your desktop.


I would not suggest the desktop since that will probably make things worse. The Desktop would have a path of (on XP at least) "C:\Documents and Settings\userid\Desktop". I would suggest saving it directly to the root "C:\"

Message 5 of 12
(4,904 Views)

No dice in My Documents or in the C root directory. I've attached some screen shots. Thanks for your help everyone!


Brian

Download All
0 Kudos
Message 6 of 12
(4,901 Views)

I can think of several other reasons that you may get a Generic File I/O error, including:

1. The disk you are trying to save to is out of disk space. Also if any disk ( including network drives ) is full it can cause problems. (This is by far the most common cause).
2. The directory you are trying to save to is read only or has some other restriction on it.
3. The user doesn't have access to a network drive that is being referenced in the project.

Do any of these seem to apply?

-Christina
0 Kudos
Message 7 of 12
(4,866 Views)

Nope, plenty of space, I've tried multiple directories and can write to them, and I'm an administrator.

 

😞

0 Kudos
Message 8 of 12
(4,841 Views)

Hey bcglaxer,

 

The error you are seeing is strange considering the all of the previous suggestions don't seem to be the cause. I would suggest trying to do this with a different vi, but it seems that you have been able to do it in the past. Another suggestion I might have is see if the error is particular to the sub-vi's that you are using.

 

Alternatively, you could try to create a source distribution from the project environment. It should save all the necessary sub-vi's much like saving the vi hierarchy. Check out this Knowledgebase for a little more information on creating a source distribution.

 

I hope this helps!

 

-Ben

Hope this helps.
-Ben

WaterlooLabs
0 Kudos
Message 9 of 12
(4,821 Views)

Hello,

 

I had the issue during saving file.

Did you find solution?

 

Thanks,

0 Kudos
Message 10 of 12
(4,363 Views)