LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LV 8.2 Generic file I/O error

I've been getting this error ever since installing 8.2.

I hope NI comes up with a patch or something, its kind of annoying to have to use Save As. Sometimes I have to pick a new name or it won't work. Then I have detrius scattered about and I hate that!




~~~~~~~~~~~~~~~~~~~~
Paul Johnson
Renco Encoders, Inc
Goleta, CA
~~~~~~~~~~~~~~~~~~~~
0 Kudos
Message 11 of 61
(3,580 Views)

Hello,

i have the same problem since LabView 8.0 and now I use LabView 8.2 and the bug did not disappear. Sometime it helps when you close the block diagram and save the VI via the front panel.

Best regards,

Hans-Peter Kreuter

KAI GmbH

Villach, AUSTRIA

0 Kudos
Message 12 of 61
(3,535 Views)
My whining and complaining has convinced NI R&D to consider reopening the issue. I've been working with an applicaition engineer since last week.  The may finally figure this one out!
~~~~~~~~~~~~~~~~~~~~
Paul Johnson
Renco Encoders, Inc
Goleta, CA
~~~~~~~~~~~~~~~~~~~~
0 Kudos
Message 13 of 61
(3,519 Views)

I sure hope so. It's really annoying.

George

0 Kudos
Message 14 of 61
(3,517 Views)
The current open corrective action on this case is 42G7H7O5. However, now that I've moved my files from the company server over to my local hard drive (not a desirable long term solution), I am not experiencing the problem.

Just curious if others experienced this problem on local hard drives or only on saving to servers?


~~~~~~~~~~~~~~~~~~~~
Paul Johnson
Renco Encoders, Inc
Goleta, CA
~~~~~~~~~~~~~~~~~~~~
0 Kudos
Message 15 of 61
(3,481 Views)
Our observation is that the "Generic file I/O error" has to do with saving the VI's on a network.
We have not seen this error when saving everything to a local harddrive.
 
Regards,
 
Paul
0 Kudos
Message 16 of 61
(3,468 Views)

Is there still no resolution to this?

We have the same problem here.  It's only a problem when saving to a network drive.  If the VIs are on my C drive I have no problem.

I

0 Kudos
Message 17 of 61
(3,440 Views)
I just spoke with the application engineer today (on another subject) and the problem is an active R&D request. No soulution yet.

However, as I'm sure you have read above, saving to the local hard drive (rather than a server) seems to eliminate the problem. Not a solution, but a work around. I haven't had the problem since moving the files to my local hard drive.

Have you?



~~~~~~~~~~~~~~~~~~~~
Paul Johnson
Renco Encoders, Inc
Goleta, CA
~~~~~~~~~~~~~~~~~~~~
0 Kudos
Message 18 of 61
(3,439 Views)

To Paul Johnson.

I haven't moved my files to my hard drive but I created a simple test vi with a sub vi.  With these located on my server I could get the Generic file I/O error for about half of the save attempts.  I copied the same vi's to my local C drive and repeated the experiment and could not get a single Generic file I/O error. 

One thing I notice:  On the network drive, when I do the save I get a little notification window saying it's saving.   It's there for such a short time I can't read it.  When I save on the C drive it's instant and I can't see if the window pops up at all.  Perhaps it's a timeout issue when it takes too long to save?

I am using LV8.2 Windows XP and our network whatever you call it is Microsoft, not Novell.  I think I didn't have the problem with LV8.0.X but I'm not sure.

Anyone know what percentage of the LV users have this problem?

0 Kudos
Message 19 of 61
(3,426 Views)
It does not appear to be wide spread. Maybe the majority of users save their work only to local hard drives?
~~~~~~~~~~~~~~~~~~~~
Paul Johnson
Renco Encoders, Inc
Goleta, CA
~~~~~~~~~~~~~~~~~~~~
0 Kudos
Message 20 of 61
(3,426 Views)