LV 8.2 Generic file I/O error

[GS]

I keep getting the following error in LV 8.2:

LabVIEW:Generic file I/O error. Cannot save VI.

It happens on several different VIs. If I keep trying eventually the VI will be saved. I never got this error in LV 8.0.1. What's going on?

George

[Wiebe@CARYA]

Hi,


Do you still have enough space on the C drive? If it's (nearly) full you'll get that problem...


Regards,


Wiebe.


"GS" <x@no.email> wrote in message news:1156858807926-409718@exchange.ni.com...
I keep getting the following error in LV 8.2:
&nbsp;


LabVIEW:Generic file I/O error. Cannot save VI.
&nbsp;
It happens on several different VIs. If I keep trying eventually the VI will be saved. I never got this error in LV 8.0.1. What's going on?
&nbsp;
George

[GS]

I've got tons of room on my C drive. Actually this is being stored on a network drive. I just checked and that drive looks pretty full. The odd thing is if I rename the VI it will save fine. So when it doesn't save I'll rename it and then rename it again with the original name. It seems like if a full drive is the problem then I wouldn't be able to save at all.

George

[Wiebe@CARYA]

"GS" <x@no.email> wrote in message news:1156947008165-410311@exchange.ni.com...
I've got tons of room on my C drive. Actually this is being stored on a network drive. I just checked and that drive looks pretty full. The odd thing is if I rename the VI it will save fine. So when it doesn't save I'll rename it and then rename it again with the original name. It seems like if&nbsp;a full drive is the problem then I wouldn't be able to save at all.
George



Sorry it didn't help. It was my only idea about what it could be...


Regards,


Wiebe.

[shoneill]

Are you saving to a Win XP machine?

If so it might be a file premission (MS?) problem.

We have very similar problems here where we can't save to a network drive even though there's lots of space.  If we re-try about 20 seconds later, it often works, or if we save locally and then copy, it works too.

And this happens in almost ALL programs here, not just LV.....

Just an idea

Shane.

[GS]

I'm not sure what our network servers are, but all our workstations are XP. I suppose it's coincidence that it just started happening when I swithced to LV 8.2. I have to figure this out because it sure is annoying. I guess it's good to know that I'm not alone in this.

George

[ruedi_76]

This is just to confirm that we got exactly the same problem after we have switched to 8.2. Any help would be great!?

Rodolphe

p.s : in attachment the file error message....

[TiTou]

Hello, I'm having the same anoying problem...

The work-around I found is to "save as", keep the same name and click "replace". I never used LV 8.0 I went straight from 7.1.1 to 8.20.

So this "bug" is certainly anoying, but it is a bug... The least one can expect from a bug is to be anoying, no ?

The point is that what anoys me most with LV8.20 is not that bug but the fact that I can wire as I like, the artificial inteligence that determines the wire path has been change from previous versions and won't let me do what I've been doing since LV 5. This is absolutely unacceptable  !!

Introducing "clever" tools like this (or like the auto-select tool) is a good idea, some like it some don't, but forcing everybody to use these is the worse thing to do !
This AI to draw wires was introduced in LV7 but we had the choice to enable it or not, now it's locked ! THIS HAS TO BE CHANGED FOR NEXT VERSION !

Message Edité par TiTou le 09-12-2006 05:30 PM

[Kalin_T]

Dear all,

This was reported to R&D (# 42G7H7O5) for further investigation. Unfortunately, the CAR was closed because we were not able to reproduce the problem. A possible workaround is to select "Save As", Substitute copy for original, keep the same name, select "yes" when prompted to replace the existing file.

We appreciate your feedback! If you have an example that reproduces the problem all the time, please let us know. We'll be happy to reopen the case.

Best regards,

[GS]

>A possible workaround is to select "Save As", Substitute copy for original, keep the same name, select "yes" when prompted to replace the existing file. <

Unfortunately that doesn't work all the time. What seems to work almost all the time is to save the VI with a different name and then save the one with the new name as the original name.

George