HansGenthe Posted July 5, 2023 Share Posted July 5, 2023 Speichern ist fehlgeschlagen. Grund: Eigentumsrecht der Datei konnte nicht verifiziert werden. Das Dokument muss nun geschlossen werden. Diese Fehlermeldung erhalte ich oft bei Affinity Publisher. Die nicht gespeicherte Arbeit ist dann verloren. Erst wenn ich Affinity schließe, kann ich die Datei neu öffnen. Das ist extrem lästig. Ein Grund, sich von Affinity zu treue. Wer kann mir helfen? Quote Link to comment Share on other sites More sharing options...
MikeTO Posted July 5, 2023 Share Posted July 5, 2023 Where are you saving your files? Affinity recommends saving directly to your computer's hard drive/SSD, not to the cloud, a network, or an external hard drive/SSD. Note that with macOS files saved to Documents and Desktop are automatically synced to iCloud so even though there's a copy on your SSD the issues Affinity has with the cloud remain. Try creating a folder directly in Users/your-user-name/ for all of your Affinity projects. Good luck Quote Download a free PDF manual for Affinity Publisher 2.5 Download a quick reference chart for Affinity's Special Characters Affinity 2.5 for macOS Sequoia 15.1, MacBook Pro 14" (M4 Pro) Link to comment Share on other sites More sharing options...
HansGenthe Posted July 6, 2023 Author Share Posted July 6, 2023 Hello, thank you for this message. However, it is very unpleasant for me. Because my new Mac mini works with external storage (4 TB is hardly affordable internally). I store on this SSD drive, which is then synchronised with p-cloud. There are no problems with any application. Do I now have to delete Affinity and go back to Adobe? Is there another solution? Quote Link to comment Share on other sites More sharing options...
Staff Callum Posted July 6, 2023 Staff Share Posted July 6, 2023 Hi Hans, Unfortunately its likely that saving / opening from your external storage is the cause of this issue. Would you be able to work on some files using your internal drive just to see if this issue reoccurs? Thanks C Quote Please tag me using @ in your reply so I can be sure to respond ASAP. Link to comment Share on other sites More sharing options...
walt.farrell Posted July 6, 2023 Share Posted July 6, 2023 For another kind of test, you might disable p-cloud synchronization temporarily, and see if the problem persists while p-cloud is inactive. If it works with p-cloud inactive, that would indicate that something in the operation of p-cloud is interfering with Affinity's access to the file. Perhaps, for example, p-cloud is locking or temporarily renaming the file while Affinity is still using it. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
HansGenthe Posted July 8, 2023 Author Share Posted July 8, 2023 Thanks for thinking along and for the answers. Since the error message reminds me of access rights, I suspect it's not so much the external drive, but rather the question of synchronisation, so it has something to do with p-cloud. I'll check with www.p-cloud.com. 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.