Save for previous failed for some unspecified reason

[B_Strange]

I'm trying to convert a project from LabVIEW 2015 to 2011 and this message pops up. How does one even begin trying to figure this out?

Full message text:

"LabVIEW: File permission error. You do not have the correct permissions for the file.

Save for previous failed for some unspecified reason. Memory could be full or the disk access may not be allowed."

[Ben]

Try logging in as admin.

Ben

[B_Strange]

Thank you for the suggestion. I have already tried this and the outcome is still the same. This one has me a little baffled.

[Ben]

Show VI Hierarchy

Select Show full path in VI label

Float over the VIs (starting from the bottom) and figure out where all of the called VIs are located.

Also switch the "File View" in the Project.

Look at all of the files and what is being used in the project.

Ben

[altenbach]

Alternatively, try run LabVIEW as admin (right-click...run as administrator). Just because you have admin privileges, does not mean LabVIEW has too. 😉

Also check that the resulting paths are not too deep. Maybe save to a shallower location.

[B_Strange]

I appreciate the info, guys. I have tried running as administrator (specifically through the context menu) and saving to a shallower directory (all the way down to the C drive). No change.

What can be done with the directory information in the files tab? I'm inclined to go to properties for every directory and uncheck "read only" but that seems pretty reckless.

By the way, I misspoke earlier: It was LabVIEW 2017, not 2015.

One final note in case this might have any bearing on a potential solution: I am trying to downgrade from 2017 to 2011 only because I accidentally upgraded from 2011 to 2017 and overwrite my backup before realizing my error.

[Ben]

Divide and conquer my help.

Start whacking away at what is used in the project until you get it to back-save.

I asked about file view because of things like third party drivers that are installed in User.lib If those drivers are password protected, it could be the source of you challenge.

Ben

[cbutcher]

---

@B_Strange wrote:

One final note in case this might have any bearing on a potential solution: I am trying to downgrade from 2017 to 2011 only because I accidentally upgraded from 2011 to 2017 and overwrite my backup before realizing my error.

---

Too late and not helpful now, but... Git checkout?

[ChrisStrykesAgain]

Have you tried saving to another drive, like a USB flash drive?

[B_Strange]

I really thought the external drive solution would work. I wonder what it could possibly be trying to change locally. Guess I'll start going through dependencies one by one.