Generic file I/O error. Cannot save VI "filename.VI"

[pgaastra]

Hi, I have LV 8.2.  I am having problems saving VI's after editing them.  I am getting the message:
Generic file I/O error.  Cannot save VI "filename.VI"

I can recreate the problem by creating a blank VI, placing a property node on the block diagram, right clicking on property and choosing, select property and in the window that pops up expanding Application and clicking on Directory path and clicking OK.  I save this VI to disk.  Then I load the file again and delete the property node. Now if I try to save that I get: Generic file I/O error.  Cannot save VI "filename.VI"

Furthermore with the real VI that I am having problems with.  If, when I get the cannot save message, I do a "Save as" and save a copy as "filename backup" and then quit labview without saving the "filename" vi, when I run LabVIEW again I get:

The last time you ran LabVIEW, an internal rror or crash occured at save.cpp, line 821.

I click investigate internal error message now and get told there is a logfile of the error.  The contents of the file on one occasion were, quote:

####
#Date: Thu, 9 Nov 2006 10:56:40 a.m.
#OSName: Windows NT
#OSVers: 5.1
#AppName: LabVIEW
#Version: 8.2
#AppKind: FDS
#AppModDate: 07/27/2006 00:08 GMT

.\panel\save.cpp(821) : DWarn: failed to find instance vi we're holding, caller vi: [VI "Spreeta Automatic Fluidics.vi" (0x05332ed0)] ident: [LinkIdentity "Instance          43 26Spreeta Automatic Fluidics .vi" [ Main Application Instance]
$Id: //labview/branches/Europa/dev/source/panel/save.cpp#112 $
0x008CCBB6 - LabVIEW <unknown> + 0
0x008D17CE - LabVIEW <unknown> + 0
0x0100F864 - LabVIEW <unknown> + 0
0x00528E26 - LabVIEW <unknown> + 0
0x00529342 - LabVIEW <unknown> + 0
0x0052960C - LabVIEW <unknown> + 0
0x004D6D2F - LabVIEW <unknown> + 0
0x004D7C95 - LabVIEW <unknown> + 0
0x004D7CD8 - LabVIEW <unknown> + 0
0x004DBA95 - LabVIEW <unknown> + 0
0x004DBD50 - LabVIEW <unknown> + 0
0x0051FD4C - LabVIEW <unknown> + 0
0x0051FD6F - LabVIEW <unknown> + 0
0x0122CA73 - LabVIEW <unknown> + 0
0x77E735DD - kernel32 <unknown> + 0

.\panel\save.cpp(821) : DWarn: failed to find instance vi we're holding, caller vi: [VI "Spreeta Automatic Fluidics 9 nov BU1.vi" (0x05332ed0)] ident: [LinkIdentity "Instance          45 26Spreeta Automatic Fluidics .vi" [ Main Application Instance]
$Id: //labview/branches/Europa/dev/source/panel/save.cpp#112 $
0x00D0FE4B - LabVIEW <unknown> + 0
0x008C8E17 - LabVIEW <unknown> + 0
0x008D1726 - LabVIEW <unknown> + 0
0x008D212C - LabVIEW <unknown> + 0
0x00C41E5E - LabVIEW <unknown> + 0
0x00C46F31 - LabVIEW <unknown> + 0
0x00C4796D - LabVIEW <unknown> + 0
0x00C497C6 - LabVIEW <unknown> + 0
0x004CCB39 - LabVIEW <unknown> + 0
0x004D7C95 - LabVIEW <unknown> + 0
0x004DF19A - LabVIEW <unknown> + 0
0x77D48654 - USER32 <unknown> + 0
0x77D48723 - USER32 <unknown> + 0
0x77D48999 - USER32 <unknown> + 0
0x77D48FD2 - USER32 <unknown> + 0

End of Quote:

Any ideas?

[JLS]

Hello,

Sorry you've encountered this problem.  The cpp error is a known issue, which is filed under corrective action request number : 42BI4OO5.  In a nutshell, this means R&D is looking into the problem.  I attempted to reproduce the problem as you described below, but I did not get the "Generic file I/O error" as you did.

If you have any further insight or detail which perhaps is the key to reproducing this, please repost, and I'll try to reproduce this again!  In the mean time, does it help to copy and paste your code to a new VI, or does that VI suffer the same problem?

Thank you,

Best Regards,

JLS

PS -

Standard CAR Response:

"This was reported to R&D (42BI4OO5 CAR ID) for further investigation. Thanks for the feedback!"

[pgaastra]

Thanks JLS

You wrote:

>If you have any further insight or detail which perhaps is the key to reproducing this, please repost, and I'll try to reproduce this again!  In the mean time, does it help to copy and >paste your code to a new VI, or does that VI suffer the same problem?

In the example I gave,  i.e. putting in that property node.  If I select all and copy to a new VI and then delete that property node  and save the new VI I don't get any errors.

Since you cant reproduce it, I must have something different in my machine, software/hardware which is different.  It doesn't seem like a common problem. 

Anyway, I can get around the problem by saving the VI to a new version each time it happens.

[JLS]

Hello,

It's great that you can get around it.  At the same time, it's frustrating that I can't reproduce it so we can deal with the issue!  Indeed it seems correlated to your machine in this case 😞  If anything else you think is related to this pops up, repost and we'll explore it again!

Best Regards,

JLS