LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LV 8.2 Generic file I/O error

I just wanted to add my name to the list of users with this problem: on moving from LV 7.1.1 to 8.2.1 I suddenly have this problem when saving to a network drive.  We actually had this same problem here with an older version of LV (6, I think), but it went away (at least for 7.1 and 7.1.1 - I'm not sure about 7.0), but has suddenly reappeared in 8.2.1 (we skipped 8.0 and 8.20).

Given the fact it most definitely is not there in 7.1.1, and now most definitely is there in 8.2.1, I have to claim it is a bug.  It may, of course be due to certain network/server configurations.

This is a major issue - I have a very complex folder structure set up on my network drives, and migrating them to my hard drive would be very impractical.  This issue also makes the use of "Save-All" extremely annoying.

Jaegen
Message 21 of 61
(2,890 Views)

I am still very annoyed about this problem.  I am not going to move my files to my local drive either.   So I keep doing the save as and am up to version 17 of some files.  I quite often mess things up because I open the wrong version.  It's also a nuisance if the same VI is used in more than one place. 

I asked the Info-LabVIEW mailing list if many people there were having problems.  I think I got at least one reply from someone that they didn't have any problems.  Most of the replies told me that I was unwise to save my files to a network drive.

0 Kudos
Message 22 of 61
(2,889 Views)
NI closed the case because they could never get the problem on their server. But it is defineitely server related. I've been using C: for quite awhile now, no problems with "save all".

Kind of lame, such a high end piece of software, you'd think this bug would be squashed fast. Who doesn't use servers nowadays? Its the only thing that gets backed up around here.


pgaastra, you gotta get a handle on those versions, their gonna bite. I suggest using C: for development in a single folder structure, then regularly copy te structure over to the server for backup.

Good Luck!

~~~~~~~~~~~~~~~~~~~~
Paul Johnson
Renco Encoders, Inc
Goleta, CA
~~~~~~~~~~~~~~~~~~~~
0 Kudos
Message 23 of 61
(2,884 Views)

I used to do the Save As but then discovered that it will eventually work if I keep saving it. Sometimes it can take ten tries, but often times it only takes a couple of retries. Much easier than going through all the renaming hassle.

George

0 Kudos
Message 24 of 61
(2,871 Views)
Have you found that the "repeated tries" technique works with the "Save All" command?
~~~~~~~~~~~~~~~~~~~~
Paul Johnson
Renco Encoders, Inc
Goleta, CA
~~~~~~~~~~~~~~~~~~~~
0 Kudos
Message 25 of 61
(2,862 Views)

I haven't tried it with "Save All".

George

0 Kudos
Message 26 of 61
(2,854 Views)
Thanks for the tip about repeated tries to save without doing save as.  I did try repeatedly but not up to ten times.  I'll do that from now on.
0 Kudos
Message 27 of 61
(2,838 Views)
R&D is still looking into corrective active request 42G7H7O5
0 Kudos
Message 28 of 61
(2,823 Views)
I've moved a current project back to the server and the repeat technique does seem to work so far. I haven't had to go upt to ten yet.


~~~~~~~~~~~~~~~~~~~~
Paul Johnson
Renco Encoders, Inc
Goleta, CA
~~~~~~~~~~~~~~~~~~~~
0 Kudos
Message 29 of 61
(2,816 Views)

Persistence is my one consistency. In this case it pays off.

George

Message 30 of 61
(2,813 Views)