"Save failed because the file could not be written to"

[Matt Maher]

Hi Everyone,

I'm getting this error message when I try to save or save as. 

 

"Save failed because the file could not be written to"

 

I work on a windows 10 PC. It's on a network, and files are stored on a shared drive. That's all I really know about the computer setup.  Help would be appreciated. 

[bo atkinson]

Similar here on MacOSX 10.14.6

Possibly happens when attempting to update a file, because first efforts to save file do save  as expected.

Also, Save As with a changed name does work if name change is sufficiently changed.

UPDATE-Today it seemed as if this was due to saving to another HD; and perhaps Mac/Mojave failed to regard my spare, internal disk as my designated disk for saving files... After further work on a folder with 35 new "afphoto" files,  the "Save As" function was not reliable, (after a few more ,new save-attempts). 

 

The ability to edit many photo files is important, so I wish I had not started this work collection, because, at this point Affinity does not save my most recent "afphoto" work!  Perhaps a clue is evident for the developers here, that the problem allows some work arounds but finally stops saving work files of users, perhaps because too many afphoto files are open, but I have lots of RAM and disk space. Closing off some windows does seem to help.

Edited February 22, 2021 by bo atkinson
unreliability

[emmrecs01]

@bo atkinson

You've posted to the "Publisher bugs found on Windows" forum area with a problem in Photo on a MAC.

Perhaps a moderator will move your post to the correct forum area.

[Matt Maher]

10 minutes ago, emmrecs01 said:

@bo atkinson

You've posted to the "Publisher bugs found on Windows" forum area with a problem in Photo on a MAC.

Perhaps a moderator will move your post to the correct forum area.

 

[Matt Maher]

15 hours ago, bo atkinson said:

Similar here on MacOSX 10.14.6

Possibly happens when attempting to update a file, because first efforts to save file do save  as expected.

Also, Save As with a changed name does work if name change is sufficiently changed.

UPDATE-Today it seemed as if this was due to saving to another HD; and perhaps Mac/Mojave failed to regard my spare, internal disk as my designated disk for saving files... After further work on a folder with 35 new "afphoto" files,  the "Save As" function was not reliable, (after a few more ,new save-attempts). 

 

The ability to edit many photo files is important, so I wish I had not started this work collection, because, at this point Affinity does not save my most recent "afphoto" work!  Perhaps a clue is evident for the developers here, that the problem allows some work arounds but finally stops saving work files of users, perhaps because too many afphoto files are open, but I have lots of RAM and disk space. Closing off some windows does seem to help.

 

From what I have read from other threads, when an affinity program opens a file- it doesn't open the entire file. Some of the data is still in the storage location. I think my problem is that I'm working off a shared drive and I rarely restart my computer,  it seems that restarting my computer daily has fixed this problem. Maybe because it's a "fresh" connection to the shared drive, and before it wasn't.

 

Maybe if you restart daily or eject & reconnect to the external drive, it would help?