Alex_M Posted May 10, 2018 Share Posted May 10, 2018 Hi, I was working on a document in Affinity Photo and when I tried to save the file the following error appeared (see attached). Why did this error appear and how do I save my file now? It would be a major pain in the *ss to start all over again with this document if I close Photo. All my disks have plenty of space (hundreds of GB) and I can freely copy/paste files to any location. I'm not able to save the .aphoto document even on the desktop. The strange thing is, I can save to JPG fine, it's only when I save to .aphoto that I get this error. What now? Quote Affinity Photo 2.4.2 for Windows ◾ OS: Windows 10 Pro x64 ver. 22H2 ◾ CPU: AMD Ryzen 7950X 16-core ◾ RAM: 64 GB DDR5-6400 ◾ GPU: MSI GeForce RTX 3090 Suprim X 24GB / driver 526.98 ◾ NVMe SSD Samsung 980 Pro 1 TB ◾ Monitors: 2x Eizo ColorEdge CS2420 24" Link to comment Share on other sites More sharing options...
toltec Posted May 10, 2018 Share Posted May 10, 2018 There are a few posts about that. They may help search for "file could not be written to" here is one Quote Windows PCs. Photo and Designer, latest non-beta versions. Link to comment Share on other sites More sharing options...
Alex_M Posted May 10, 2018 Author Share Posted May 10, 2018 Thanks, I checked them all but none of the threads provided any solution. Do you know what should I do to successfully save the document? I still have it open. Quote Affinity Photo 2.4.2 for Windows ◾ OS: Windows 10 Pro x64 ver. 22H2 ◾ CPU: AMD Ryzen 7950X 16-core ◾ RAM: 64 GB DDR5-6400 ◾ GPU: MSI GeForce RTX 3090 Suprim X 24GB / driver 526.98 ◾ NVMe SSD Samsung 980 Pro 1 TB ◾ Monitors: 2x Eizo ColorEdge CS2420 24" Link to comment Share on other sites More sharing options...
firstdefence Posted May 10, 2018 Share Posted May 10, 2018 @Alex_M Create a new Document with the same document specs ie. size dpi etc, Copy and Paste off of the layer into the new document and save the New Document to Documents or Pictures, Then close the new document down and try opening it back up, it that works and all the layers and your work is intact I think it would be safe to close the old document down. ronnyb 1 Quote iMac 27" 2019 Somona 14.3.1, iMac 27" Affinity Designer, Photo & Publisher V1 & V2, Adobe, Inkscape, Vectorstyler, Blender, C4D, Sketchup + more... XP-Pen Artist-22E, - iPad Pro 12.9 (Please refrain from licking the screen while using this forum) Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions Link to comment Share on other sites More sharing options...
Alex_M Posted June 18, 2018 Author Share Posted June 18, 2018 Thanks @firstdefence, I will try this next time it happens again. Quote Affinity Photo 2.4.2 for Windows ◾ OS: Windows 10 Pro x64 ver. 22H2 ◾ CPU: AMD Ryzen 7950X 16-core ◾ RAM: 64 GB DDR5-6400 ◾ GPU: MSI GeForce RTX 3090 Suprim X 24GB / driver 526.98 ◾ NVMe SSD Samsung 980 Pro 1 TB ◾ Monitors: 2x Eizo ColorEdge CS2420 24" Link to comment Share on other sites More sharing options...
Staff MEB Posted June 18, 2018 Staff Share Posted June 18, 2018 Hi Alex_M, From where have you opened that file? Was it stored on an external drive/NAS or cloud sync folder? Or was it on your internal (system) drive? Quote A Guide to Learning Affinity Software | Affinity Quick Reference Link to comment Share on other sites More sharing options...
Alex_M Posted June 19, 2018 Author Share Posted June 19, 2018 I've opened the file from a mapped network drive. That is, an HDD on another PC on the network. Quote Affinity Photo 2.4.2 for Windows ◾ OS: Windows 10 Pro x64 ver. 22H2 ◾ CPU: AMD Ryzen 7950X 16-core ◾ RAM: 64 GB DDR5-6400 ◾ GPU: MSI GeForce RTX 3090 Suprim X 24GB / driver 526.98 ◾ NVMe SSD Samsung 980 Pro 1 TB ◾ Monitors: 2x Eizo ColorEdge CS2420 24" Link to comment Share on other sites More sharing options...
Alex_M Posted June 22, 2018 Author Share Posted June 22, 2018 It just happened again! I tried what @firstdefence suggested but it didn't help. What's going on? This causes me to lose work. Quote Affinity Photo 2.4.2 for Windows ◾ OS: Windows 10 Pro x64 ver. 22H2 ◾ CPU: AMD Ryzen 7950X 16-core ◾ RAM: 64 GB DDR5-6400 ◾ GPU: MSI GeForce RTX 3090 Suprim X 24GB / driver 526.98 ◾ NVMe SSD Samsung 980 Pro 1 TB ◾ Monitors: 2x Eizo ColorEdge CS2420 24" Link to comment Share on other sites More sharing options...
carl123 Posted June 23, 2018 Share Posted June 23, 2018 This is a well reported problem when working on non local drives and until it is fixed the ONLY safe solution is to work on the file on HDDs local to your PC/Mac then do a final save as to were you want it stored. Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time. Link to comment Share on other sites More sharing options...
Alex_M Posted March 25, 2019 Author Share Posted March 25, 2019 Save failed... again! I tried saving everywhere - my documents, my SSD, my HDD, desktop... nothing worked. I had to close the document and lose my work. Quote Affinity Photo 2.4.2 for Windows ◾ OS: Windows 10 Pro x64 ver. 22H2 ◾ CPU: AMD Ryzen 7950X 16-core ◾ RAM: 64 GB DDR5-6400 ◾ GPU: MSI GeForce RTX 3090 Suprim X 24GB / driver 526.98 ◾ NVMe SSD Samsung 980 Pro 1 TB ◾ Monitors: 2x Eizo ColorEdge CS2420 24" Link to comment Share on other sites More sharing options...
ebbe Posted December 30, 2021 Share Posted December 30, 2021 I see this post startet in 2018 - now its the end of 2021, and I still frequently have this problem in Affinity Photo. Working from the internal hard drive on mye MAC (Currently Big Sur, but had this problem on earlier OS-es also). When I try to save file I get: "The file could not be created" If I try to save as a new file I get: "Save failed because you do not have permission to create a file in that location." So my *guess* is that Affinity somehow sometimes looses its permission to write to disk from time to time. My only solution so far is to close Affinity Photo (loosing my work), and restart the application, which then works fine again. I don´t like to rant or be negative, but if this issued is not fixed within the next release, I am forced to turn back to the Adobe world. One thing is the utterly annoying problem that you cannot trust a major software program to save its own files. But working in a news company with tight deadlines, I can not allow myself to use a program that intermittently forces you to redo your work. It´s a shame, because I really LOVE the workflow of Affinity. Quote Link to comment Share on other sites More sharing options...
sastjw Posted August 24, 2022 Share Posted August 24, 2022 You can always save it as a high quality pdf. Affinity lets you edit pdfs so you're safe like that. Quote Link to comment Share on other sites More sharing options...
SteveLA Posted April 17, 2023 Share Posted April 17, 2023 I have both Affinity Designer and Photo. When I got the dreaded "file could not be written to" error while working on an artboard in Designer, I noticed that I had to option to open the file in Photo, which I did. It opened in Photo and I was able to save the file. Then I was able to shut down Designer and reopen it. Hope this helps. Quote Link to comment Share on other sites More sharing options...
Alex_M Posted April 28, 2023 Author Share Posted April 28, 2023 Hello Affinity team, I'm still getting this error in 2023 with Affinity Photo 2.0.4. It happens much more frequently than with Photo version 1.x. Every other document I try to save now shows this error. The screenshot below is from a document I've just tried to save. I'm getting a bit fed up with all these errors when saving my documents... Quote Affinity Photo 2.4.2 for Windows ◾ OS: Windows 10 Pro x64 ver. 22H2 ◾ CPU: AMD Ryzen 7950X 16-core ◾ RAM: 64 GB DDR5-6400 ◾ GPU: MSI GeForce RTX 3090 Suprim X 24GB / driver 526.98 ◾ NVMe SSD Samsung 980 Pro 1 TB ◾ Monitors: 2x Eizo ColorEdge CS2420 24" Link to comment Share on other sites More sharing options...
MelsB Posted June 10, 2023 Share Posted June 10, 2023 I have this problem too. Local: MacBook Air M1 64GB 2TB Affinity Publisher 2, 2.1.0 Quote Link to comment Share on other sites More sharing options...
guategeek Posted June 13, 2023 Share Posted June 13, 2023 I never had this problem with Affinity 1.0 apps, but ever since the 2.1 update I get this all the time. Yes my files are in an external USB drive, but they have been in this drive for months now and it was never a problem before. This is on windows 11 in my case though seeing all these posts looks like its a core Affinity problem. Quote Link to comment Share on other sites More sharing options...
MikkelJP Posted July 29, 2023 Share Posted July 29, 2023 (edited) So I think I might have solved this for some. The issue seems to have something to do with embedded files in my case. If Affinity loses track of the embedded data for one reason or another it will prompt this message, which kinda makes sense because it has no idea what it is saving. While this is sometimes obviously because of a bug, there may still be some hope for your unsaved work. The solution: If you go into the resource manager and replace/relink your embedded files, you should be able to save again. I have attached a short video to show the process, although it should be quite straightforward. Hope this works for most of you guys. Screen Recording 2023-07-29 at 02.46.15.mov Edited July 29, 2023 by MikkelJP Quote Link to comment Share on other sites More sharing options...
Andrusoid Posted September 8, 2023 Share Posted September 8, 2023 I've had this issue from time to time. Today, I went to the resource manager and selected all of the embedded resources and change them to linked files. Oh and first I saved a collection to a new folder in my Publisher files folder. Quote Link to comment Share on other sites More sharing options...
yokohama_al Posted September 12, 2023 Share Posted September 12, 2023 On 7/29/2023 at 9:49 AM, MikkelJP said: So I think I might have solved this for some. The issue seems to have something to do with embedded files in my case. If Affinity loses track of the embedded data for one reason or another it will prompt this message, which kinda makes sense because it has no idea what it is saving. While this is sometimes obviously because of a bug, there may still be some hope for your unsaved work. The solution: If you go into the resource manager and replace/relink your embedded files, you should be able to save again. I have attached a short video to show the process, although it should be quite straightforward. Hope this works for most of you guys. Screen Recording 2023-07-29 at 02.46.15.mov 29.93 MB · 20 downloads This worked for me. Thanks a million. MikkelJP 1 Quote Link to comment Share on other sites More sharing options...
MikkelJP Posted October 6, 2023 Share Posted October 6, 2023 No problem. I am glad I could help! Quote Link to comment Share on other sites More sharing options...
Staff Affinity Info Bot Posted October 24, 2023 Staff Share Posted October 24, 2023 The issue "Saving Failed increasing frequency of reports" (REF: AFP-4826) has been fixed by the developers in build "2.2.1 Release". This fix is in the current customer release. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us 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.