Save failed because the file could not be written to

[Michael LaBash]

I am been working on a very large document( a book) which is now over 500 pages. I had to take a long break (6 months or so). Now that I am starting to work on the file again, after I have been working (and saving the file as I go) for an hour or so I get an error when I try to save the file that the file cannot be written to. And I lose whatever work I ad done since the last save. I have tried "Save As" with another name, which worked one time, but never again.

The file is saved to my local disk. All fonts and linked images are on the same local disk.

I have been able to re-open the file so far. One time I was asked to "recover" the file. But it is starting to feel dicey. I now make a point of saving my work every few minutes, then I close and re-open Publisher after about a half hour.

I am able to successfully export to pdf the entire document without any problems.

Why is this happening and how can I make it go away? 

Thanks in advance!

My iMac is running Monterey 12.4.
 

[stokerg]

Hi @Michael LaBash,

Where did you purchase Affinity from?  Direct from us or via the Mac App Store?  If via the App Store, can you have a look at this thread and see if it helps. If you purchased direct from us, we can look at getting a copy of the file and all images from you to see if we can replicate the issue.

[PaulEC]

Until you solve this problem, I would strongly suggest that you do try to "save as", (if you can), rather than only saving over the same file. At least, that way, you have some recent backups, rather than relying on just one version. Also, as you can export as PDF, do so occasionally. If all else fails. it's better than nothing as a backup.

[Michael LaBash]

14 hours ago, stokerg said:

Hi @Michael LaBash,

Where did you purchase Affinity from?  Direct from us or via the Mac App Store?  If via the App Store, can you have a look at this thread and see if it helps. If you purchased direct from us, we can look at getting a copy of the file and all images from you to see if we can replicate the issue.

I purchased it directly from you.

[Michael LaBash]

14 hours ago, PaulEC said:

Until you solve this problem, I would strongly suggest that you do try to "save as", (if you can), rather than only saving over the same file. At least, that way, you have some recent backups, rather than relying on just one version. Also, as you can export as PDF, do so occasionally. If all else fails. it's better than nothing as a backup.

Thanks, Paul. That's a good idea!

[Michael LaBash]

It seems like the length of time the file is open and I am working on it is the problem. That's why I am saving often and quitting the app every half hour or so. When I have lost some work I did, then reopen the file and recreate it, I don't have any problems. So it doesn't seem like my image files are corrupt.

Any ideas why this is happening? Is it a memory thing? 

[stokerg]

On 7/22/2022 at 1:41 AM, Michael LaBash said:

It seems like the length of time the file is open and I am working on it is the problem. That's why I am saving often and quitting the app every half hour or so. When I have lost some work I did, then reopen the file and recreate it, I don't have any problems. So it doesn't seem like my image files are corrupt.

 

How long are you working on the file?  Not that it should matter, unless your leaving Affinity open for days on time, which just isn't a good idea for any app.  Also does the file have any linked images/files or are they all embedded?  If they are linked, if you embed them which you can do via the Resource Manager on the Document menu, do you then have the same saving issue?  Would be worth trying this on a copy of your file, just so you always have a backup of it.

[R C-R]

3 hours ago, stokerg said:

Not that it should matter, unless your leaving Affinity open for days on time, which just isn't a good idea for any app. 

Just curious I guess, but why isn't it a good idea?

[Michael LaBash]

On 7/26/2022 at 6:15 AM, stokerg said:

How long are you working on the file?  Not that it should matter, unless your leaving Affinity open for days on time, which just isn't a good idea for any app.  Also does the file have any linked images/files or are they all embedded?  If they are linked, if you embed them which you can do via the Resource Manager on the Document menu, do you then have the same saving issue?  Would be worth trying this on a copy of your file, just so you always have a backup of it.

Embedding the images seems to have taken care of it so far. I have not had any saving errors during the past couple work sessions.