LabVIEW error 44 and corrupting programs

[oldmanXJ]

Here is the save error I get.  I can abort, then save again and it gets saved.  Every once in a while it corrupts the file you are saving.

[oldmanXJ]

Once corrupted, here is what I get.

I can replace only the Tput Sensitivity Tool.vi and it once again works.....kind of.

[yometric21]

I am having the exact same issue.

It works fine if i keep my files local on my C: drive, but if i try to save to a network drive i get an intermittent save error 44.  

If you hit OK, then cancel on the file dialog that pops up, and then close the project without saving the changes it will corrupt the file every time (failed to load dynamic library because of missing external symbols...).  

If you hit OK, then Current Folder on the file dialog prompt (anywhere from 2-5 times usually works for me), it will eventually save the file.  It seems like as long as the file eventually gets saved it wont be corrupted.  This is very irritating and a huge time waste though.

I just installed LabVIEW 2016 but i still have the same issue there.

I recently switched jobs and never had this issue at my last job, also running LabVIEW 2015 and saving files to a network drive.  One thing to note is that i am using Windows 10 now, where I was on Windows 7 at my last job.  It seems like every post i've seen about this problem the person is on Windows 10, so I am considering asking my IT department to install windows 7 for me instead to see if that solves it as a next step.

[oldmanXJ]

Thanks for your input.  You described what I am seeing perfectly.  It is a royal pain.  We keep the files on the server because we have multiple test benches and want exactly the same code running on each.  The server is backed up twice a day by IT.  The testers are not backed up.

Having to image everything local is not acceptable in our application for security and logistical reasons.  From the message it appears that they are storing the file as a temporary file first.  It may have to do with them doing behind the scenes backups or something similar after a successful new version is loaded, then renaming the new file to the original name. 

They may be trying to do a rename or move on the old file, followed by a rename on the new file.  Win10 is multi-threaded/tasking and may be trying to rename the new file concurrently with the work on the old file and a file collision occurs.

You would think NI would fix this since it has been around quite a while.  I do believe it is related to Win10 as well.  I never saw it until I upgraded.  ALL of our computers are upgraded to Win10.

Once compiled, you aren't opening the project files and I don't see any problems, but during development and debug it is causing my blood pressure to go up. 

[donkdonk]

Same here.

Win 10 and LabVIEW 2015 SP1 32bit (15.0.1f1) causes the 'File permission error' dialog to pop-up.

After several attempts I succeed in saving it. Up to now no known problems with corrupted files for me.

[oldmanXJ]

Just an update on this.  The save as function has the exact same issue with file permissions and corrupting the file.

[oldmanXJ]

You also get the same result saving an typedef.

[ChrisStrykesAgain]

CAR 597858 was fixed in LabVIEW 2017. See the 2017 LabVIEW Bug Fix List for details: http://www.ni.com/product-documentation/53584/en/

[HDRM]

I ran into the same issue today with my new Windows 10 machine and LabVIEW 2015 SP1.

I'll try LV2017 instead and hope it works.

The issue with LV2015 is a big pain as we decided LV2015 to be our official LabVIEW version throughout the whole company, including sophisticated SW installation procedures via company's Asset Companion / Software Center...

I going to inform my colleagues since I am one of the first guys with a Windows 10 machine here.

Kind regards

Manu

[yometric21]

I switched to LabVIEW 2017 a few weeks ago and have not had this problem since switching.