LV 8.2 Generic file I/O error

[Jaegen]

This problem does still exist in 8.5.  See here.

Jaegen

[THailey3]

Jaegen is correct.  This is still a problem and arguably much worse in LabVIEW 8.5.  See the LabVIEW 8.5 Known Issues and search for 42G7H7O5.

VI Save Failures to Shared Network Drives
In rare cases, LabVIEW prevents saving to an existing VI on shared network drives. When this occurs, LabVIEW acts as if it has saved the VI to disk when it has not.

In LabVIEW 8.2.x, an error was thrown.  In LabVIEW 8.5, LabVIEW acts as it it has saved the VI and clears the "dirty dot" incorrectly.  This is being investigated and will more than likely be fixed in an upcoming release.

[Anthony_de_Vries]

Considering that lots of people will be saving to network shares, I would suspect the problem is at least partly server related.   I've always saved my stuff on network shares, and don't seem to run into these problems.  (used LV 7.1, 8, 8.2, 8.2.1, 8.5  on WindowXP client, Suse Enterprise server)

What kind of network share are you guys using?   A real Windows server, or a Linux server with Samba, or....      In case of a Linux server, maybe try to see what happens when saving on a network share of an XP workstation?

[baptie]

We are having the same problem, we save over a network and I seem to get the problem with every Existing VI I try to save.

I have a bad habit of clicking the close window Icon, then when I get the option to save changes I say yes!

But get Generic File I/O Error and I loose all the work I have been working on

Cntl S about 10-15 times before a file saves & I am not keen on having a full project on my local laptop.

---

42G7H7O5 VI Save Failures to Shared Network Drives In rare cases, LabVIEW prevents saving to an existing VI on shared network drives. When this occurs, LabVIEW acts as if it has saved the VI to disk when it has not. Workaround—1. Save to local drive instead of network drive. 2. Select "Save As", Substitute copy for original, keep the same name, select "yes" when prompted to replace the existing file. Date Added—09/26/2007

---

Has there been any news on this 'Bug' getting resolved?

[Pablop]

baptie,

There is a patch for 8.2. I have no problems saving to server locations now.  Not sure what to tell you for 8.5. I'm holding off using it at this point.

RE: your habit of hitting the "close" button, you can always "cancel" to abort the save then use the "save as" work arounds. If you aren't on 8.5 though, just install the patch.

[baptie]

Sadly we are already upgraded to 8.5.

Thanks for getting back to me

We wait with baited breath!!!!

[TiTou]

We have Windows Server 2000 and we're having this issue with LV 8.20 and 8.5.

If I remember well someone said that upgrading to Windows Server 2003 solved the issue with LV 8.20, I hope it also solves the issue for 8.5.

[griffindore]

Hi TiTou,

You can apply the LabVIEW 8.2.1 patch to correct the problem in LabVIEW 8.2. For LabVIEW 8.5, I wouldn't hold my breath about an upgrade to Windows Server 2003 correcting the issue. As Travis stated, this "will more than likely be fixed in an upcoming release." Happy Holidays!

[TiTou]

Hello Mike,

I guess you're right, but it's very frustrating to have to wait untill the next release... To work with 8.5 I have to duplicate my whole project on my local hard drive or to save all my VIs in a LLB (by the way I wander why the issus does not affect LLBs ). When is 8.5.1 or 8.6 or whatever you'll call it, will be released ?

I have a personal problem with LLBs, I can deal with small LLBs but I wouldn't put all my eggs in the same bag when I have hundreds of eggs...
And working in local... well... it's strictly forbidden by our company guidelines for obvious reasons.

[pgaastra]

Sorry, no new news.

Can anyone tell me if Version 8.5 has overcome the Generic file I/O error (problem not being able to save to network drives)?

I have version 8.2.  I was going to download the 8.2.1f4 patch, as mentioned a few posts to this thread ago, but it says you need version 8.2.1.  Somehow we never got 8.2.1 ( I am on version 8.2) and I don't see it as a download on the NI site.

I am getting the save failing quite often and doing the repeat save even 20 times doesn't work for some files.  Running the Process monitor software as mentioned previously in this thread does work.