andreasr1505 Posted March 13 Share Posted March 13 I often get the following error message in Affinity designer (2.4.0 Mac mini M1 OS Monterey 12.6). "An error occurred after saving this document: "file name". Saving was successful, but the file can no longer be accessed. The document must now be closed." I have to open a restore file then and save it again as a Affinity Designer document. Is there a way to avoid this error? Can I fix the issue? Thank you so much for your help. Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted March 13 Share Posted March 13 Welcome to the Serif Affinity forums. I'm a bit puzzled that you would need to open a restore file, if the Save completed successfully as the message indicated. That seems odd. To begin diagnosing the cause of the error, please tell us more about your setup, in particular where you're saving the file to. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
Staff NathanC Posted March 14 Staff Share Posted March 14 Welcome to the forums @andreasr1505, We are still looking into issues relating to the 'Fail to save' error following the 2.2 file handling improvements, as Walt's mentioned if you can provide any further information with regards to what location these files are being opened from and saved to (E.G a network drive, cloud drive, external drive etc.) and if the problem can be replicated by saving locally we would be grateful. Thanks Quote Link to comment Share on other sites More sharing options...
GripsholmLion Posted March 14 Share Posted March 14 Hi @andreasr1505. This isn't apropos of your problem, but just a friendly heads-up. If 12.6 wasn't a typo, you should check for OS updates because Monterey is up to 12.7.4 now and there have been quite a lot of security patches lately. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.