Beschädigte Datei mit verschiedenen Fehlermeldungen /damaged file with different error messages

[Guest]

Hello dear people,

Unfortunately my English isn’t very good, so I’ll try to explain the problem in German first, then in English.

 

 

Ich arbeite seit Monaten an einem Fotobuch mit inzwischen fast 140 Seiten und habe das große Problem, dass die Datei nun beschädigt ist und verschiedene Fehlermeldungen auswirft.

Zuerst erschien nache einiger Zeit immer die Fehlermeldung, dass das Dokument beschädigt sei und geschlossen werden müsse.

Unzählige Male habe ich daraufhin versucht, das Dokument aus alten Sicherungen wieder aufzubauen, aber ständig erschien wieder diese Fehlermeldung.

Daraufhin habe ich mich in diesem Forum angemeldet und das Problem in einem anderen Thread geschildert. (Link)

Mir wurde sehr nett versucht zu helfen und wir konnte das Problem wohlmöglich etwas eingrenzen: ein Foto erschien nach dem Öffnen des Dokuments immer erst mit „Störpunkten“ und mir wurde unter anderem geraten, das Bild erst ganz aus dem Dokument zu löschen und dann neu zu platzieren.

Ich habe also das Bild aus dem Dokument gelöscht. Bei dem Versuch, die Datei direkt untern neuem Namen abzuspeichern, erschien aber dann folgende Fehlermeldung:

"Fehler beim Laden des Dokuments – Bei dem ersten Laden der Dokumentdatei ist der Zugriff abgebrochen. Das Dokument muss nun geschlossen werden."

Ich konnte das geschlossene Dokument zwar wieder öffnen, aber immer wenn ich jetzt etwas speichern möchte, erscheint nun folgende Fehlermeldung: "Fehler beim Speichern des Dokuments – Fehler beim Speichern. Änderungen an der Datei sind nicht erlaubt.

Manchmal erscheint auch die Fehlermeldung, dass das Eigentumsrecht der Datei nicht verififiziert werden kann und das Dokument wird geschlossen.

Ich kann das Dokument nun nur noch nach jedem Schritt unter neuem Namen speichern, das Dokument scheint mir insgesamt ziemlich beschädigt zu sein 😞

Hat hier vielleicht noch jemand eine Idee, was ich noch veruschen könnte? Oder wäre es eventuell sogar möglich, dass auch ich meine Datei hochlade und einmal ein Experte – ich bin absoluter Laie – darüber schaut?

Ich hatte mich für dieses Projekt extra etwas in Affinity eingearbeitet und habe unzählige Stunden auf dieses Projekt verwendet.

Über Hilfe würde ich mich sehr freuen und bedanke mich vorab für eventuelle Unterstützung!!!

Liebe Grüße, Maui

 

 

Since many months I’m working on a book with photos and nearly 140 pages but now the document is damaged and different error messages appear.

First there was the error message that the document is damaged and has to be closed. I tried many times to recreate the document with the help of old documents I saved before but nearly every time the error message appeared again.

That’s why I joined this forum and asked for held in another thread before. (link)

Some very friendly people tried to help me and maybe we could find one fault: one of the photos in the document appeared with some „disturbing points“ on it when I opened the document and needed longer than the orther photos zu appear correctly.

Someone gave me the advice to delete the photo and to put in in again afterwards. So I deleted the photo but before I put it in again, I wanted to save the document under a different name.

Unhappily another error message appeared which said that the acces / connection was canceled and that the document has to be closed now.

I could open the document again but now it says always when I want to save it that changes of that file arent’s allowed or that the ownership can’t be verified and the document has to be closed.

The only thing I can do is to save the document under different names.

I think my file /my files has / have some faults 😞

Maybe someone has some advices what I could try next? Or maybe it’s possible to make an upload so that a profi can realize the problem? Unfotunetely I haven’t much knowledge by myself because I never worked with affinity before. Nevertheless I worked innumerable hours on this docoment.

I would be very very happy if someone would try to help me! Thanks a lot for any support!!!

Best regards, Maui

[Dan C]

Hallo @Maui,

Es tut mir leid zu hören, dass Sie Probleme haben!

Erstens ist Ihr Englisch vollkommen verständlich – Sie können hier in den Affinity-Foren natürlich gerne auch auf Englisch oder Deutsch posten, je nachdem, was Sie bevorzugen.
Bitte beachten Sie, dass ich persönlich leider kein Deutsch spreche und meine Antworten daher übersetzt werden.

Im Hinblick auf dieses Dokument bedauern wir auf jeden Fall, dass Sie beim Speichern und Bearbeiten dieses Dokuments auf viele Probleme gestoßen sind.
Aus dem Thread, den Sie verlinkt haben, kann ich ersehen, dass andere Mitglieder des Forums Sie über die bevorstehenden Änderungen in Version 2.2 informiert haben, um zu versuchen, diese Dateifehler für unsere Benutzer zu beheben und hoffentlich die Wahrscheinlichkeit zu verringern, dass dies auftritt. Da sich diese Version jedoch noch in der Betaphase befindet, ist sie noch nicht für die Produktionsarbeit geeignet, und ich glaube nicht, dass diese Änderungen vollständig auf „alte“ Dokumente angewendet werden, obwohl wir hoffen, dass dies die Stabilität des Affinity-Dateiformats verbessern sollte.

In der Zwischenzeit möchte ich eine Kopie Ihrer .afpackage-Datei anfordern, um die Angelegenheit weiter zu untersuchen. Bitte öffnen Sie Ihre .afpub-Datei in Publisher und navigieren Sie dann zu Datei > Als Paket speichern.
Die App fordert Sie auf, einen Ausgabeordner anzugeben (ich würde empfehlen, einen neuen, leeren Ordner zu erstellen), der das Affinity-Dokument und alle darin verwendeten Bilder/Dokumente/Schriftarten in diesem Ordner speichert.

Nach der Erstellung laden Sie bitte diesen vollständigen Ordner für mich auf den folgenden Link hoch:

https://www.dropbox.com/request/7ZacJ5wqS8PWyRfPJlC9

Bitte antworten Sie abschließend hier, um mir Bescheid zu geben, sobald diese bereitgestellt wurde.
Vielen Dank im Voraus!

[Guest]

Thank you so much for offering your help and for telling me that my English is okay 🙂 (I didn't knew that threads could be translated and don't wanted so be impolite by writing German in an English forum. Nevertheless maybe it's easier if I answer directly in English and nobody has to translate ist?)

I just made the upload.

Thanks for any help and best regards, Maui

[thomaso]

25 minutes ago, Maui said:

(I didn't knew that threads could be translated

Nowadays it is availble on 1-click to everybody with a browser plug-in. Compare the video in this post:

[Dan C]

Many thanks for providing that for me!

I cannot immediately see any issues with your document, although there are some interesting things to note.

Firstly, when opening your .afpackage, I'm informed that all 549 images are present, and 0 are missing - 

However once the file then loads, I'm informed that certain resources are missing and I find that 93 images are listed as 'Missing' in the Resource Manager -

Just to confirm, are all of your images for this file within the same location on your Desktop? Was there any indication that not all images were initially saved with your .afpackage file?

Secondly, I notice that your Linked resources have an interesting use of different character symbols within their names. Although this shouldn't technically be an issue, I have seen oddities occur previously when using non-traditional characters. Is there a specific reason that many of your linked images contain a combination of the following characters within the file name?

≈ > ;( 

Many thanks once again!

[thomaso]

20 minutes ago, Dan C said:

I have seen oddities occur previously when using non-traditional characters. Is there a specific reason that many of your linked images contain a combination of the following characters within the file name?

≈ > ;( 

Can you specify "non-traditional" characters to make users possibly avoid them? It seems in macOS nearly every character can be used for folder or file names without complaint of the macOS Finder. The only character I am aware of that gets blocked by the Finder is the colon :

@Maui, I am curious how the image folders got named, possibly by a software? I am wondering because of the character that looks like a tiny 'Pd' with reduced kerning, while I can not find it on my keyboard.

[Dan C]

29 minutes ago, thomaso said:

Can you specify "non-traditional" characters to make users possibly avoid them?

As far as I'm aware, there are no definitive characters that aren't supported by Affinity, besides those not supported by the OS itself, such as the colon you've mentioned.

However the 'approximately equals to' ( ≈ ) character in the file name that you have also pointed out is the most unusual from OPs file names and could potentially cause an issue within Publisher - though I am uncertain this is the exact cause, it simply seems the most likely based on the fact that there are no obvious issues with the document itself and I am not yet experiencing any of the same error messages with the file in my testing.

[Oufti]

On 7/26/2023 at 5:07 PM, Dan C said:

As far as I'm aware, there are no definitive characters that aren't supported by Affinity, besides those not supported by the OS itself, such as the colon you've mentioned.

However the 'approximately equals to' ( ≈ ) character in the file name that you have also pointed out is the most unusual from OPs file names and could potentially cause an issue within Publisher - though I am uncertain this is the exact cause

Since APFS does not include any system-wide normalisation, in certain circumstances (mostly when using volumes with other file systems than HFS+ or APFS, or with volumes inherited from older versions of the OS), MacOS or apps used with it had sometimes some troubles with normalisation of special characters (let's say in short non ASCII ; in fact mainly the composed characters like accented letters, those which can be either represented by a single character, like é, or a combination, like ´ combined with e, which also results in é but not the same character…) 

It then cannot open files when there is such a character in its path. 

— This technical article is mainly focused on volume names problems but it explains the general cause and gives at the end some possibly useful clues for developers: https://eclecticlight.co/2023/05/16/volume-names-mount-points-and-normalisation/ 
This older but more fundamental one can also be worth reading in complement: https://eclecticlight.co/2021/05/08/explainer-unicode-normalization-and-apfs/

 

@Maui A possible solution — if the cause of the OP problem was related to this above — is simply to:

1. Select the icon of the offending folder or file, with the "special" character,
2. Press the key Enter to select its name and
3. Press it a second time to confirm the name.

This will "re-encode" correctly the name containing these characters and your files within this folder and its sub-folders should now open normally… 

 

[Guest]

Thanks a lot for your answers, Dan C and  thomaso 😊

Yes, before I created the „afpackage-file“, all photos were placed in the same file.

It’s „mysterious“ because after creating the file „afpackage“, there were all 642 photos in that new file I created and I used for the upload. There was no error message that something has gone wrong, too.

Did the 93 missing photos didn’t arrive at you, Dan C, or had they just the status „missing“ while they were in the file „images“ nevertheless?

Oh, the names I gave the photos could make trouble? Thanks for letting me know! I will change them within the next days! (@thomaso: I didn’t use a software that named the photos, I did it by myself and had my own system. This symbol „≈“ I placed in the photo-names by copy and paste 🙈)

But one thing is really really good: after I created the „afpackage-file“, I used this file to continue with my book, saved it as a normal file again and now there is no more error message when I try to save it anymore 👍

[Guest]

Oh, while I wrote my answer, you posted another advice, Oufti. Thanks a lot 😊
I only unerstood some parts because my knowledge of computers and softwares isn’t very big, but I understood the steps 1, 2 and 3 and I will try them!! Thanks a lot again!

[thomaso]

1 hour ago, Maui said:

It’s „mysterious“ because after creating the file „afpackage“, there were all 642 photos in that new file I created and I used for the upload. There was no error message that something has gone wrong, too.

@Dan C, the two different summaries (after @Maui's packing / after your opening) seem to indicate that it could be useful to additionally mention the file size of the package in the summary either as total or speparately for its folders / .afpackage file. This might give an additional hint over the result of the package process, e.g. if the packing computer compares the size(s) with the initial sizes of the linked resources on disk.

1 hour ago, Maui said:

But one thing is really really good: after I created the „afpackage-file“, I used this file to continue with my book, saved it as a normal file again and now there is no more error message when I try to save it anymore 👍

Great news and a useful note for other users in a similar situation. – Now I a, curious: were the number of linked images complete after unpacking, or did it open with less than the packed 642 resources?

[Guest]

Fortunately the status of all 642 photos in the "afpackage-file" is "linked" after opening 👍😅

I created an own file for that package (photo 1), this file includes the fonts, the photos and the afpackage-file (photo 2) and the whole file takes 1,42 GB of my storage space.

[thomaso]

Thank you @Maui, I think for a comparison with the data that were available for / opened by @Dan C it may be more interesting to see not just icons with folder names but your Finder's list view of this parent folder "Maui", unfolded and showing the containing "Images" folder size and the ".afpackage" file size, like so:

[Guest]

Hello again 👋

I don't know why Finder's list doesn't show how much storage space the whole files need 🤔

I just can see how much storage space the fonts and images need separately if I open the files 😬

[Oufti]

In the Finder, you can look at the infos for the folder (⌘-I) containing your main document and its files, or you can tick "Calculate size" (or whatever it is in your language) in the window presentation options (circled button with ellipsis, in the window tool bar.)

[thomaso]

Sometimes macOS takes time to calculate and display folder sizes.

However, now we know the size of this image folder and its number of files (1.42 GB minus ~16 MB | 648 objects minus ~5 objects) and @Dan C might compare them with the uploaded data in the dropbox. I wonder – while the 93 missing resources represent the deviation of 93 images in the package summary of the downloaded versus your packed data – if the total file folder sizes and/or the .afpackage file size in the downloaded data do differ accordingly.

[Guest]

Thanks  Here is a screenshot with all informations

[Dan C]

Apologies for the delayed response here as I have been out of the office for a few days.

On 7/27/2023 at 6:06 PM, Maui said:

It’s „mysterious“ because after creating the file „afpackage“, there were all 642 photos in that new file I created and I used for the upload. There was no error message that something has gone wrong, too.

Did the 93 missing photos didn’t arrive at you, Dan C, or had they just the status „missing“ while they were in the file „images“ nevertheless?

I can confirm that all 642 images were received as expected and the size of the overall .afpackage folder matches the folder on your mac - it's only when opening your .afpackage that the 93 images aren't imported on my end - though I can see that they are imported when opening the .afpackage on your mac so I will be investigating this as a separate issue, as I don't believe it is related to the original issue you've reported here.

On 7/27/2023 at 6:06 PM, Maui said:

But one thing is really really good: after I created the „afpackage-file“, I used this file to continue with my book, saved it as a normal file again and now there is no more error message when I try to save it anymore 👍

I'm glad to hear this - does this remain true after editing the file for a few days?

On 7/27/2023 at 7:26 PM, thomaso said:

the two different summaries (after @Maui's packing / after your opening) seem to indicate that it could be useful to additionally mention the file size of the package in the summary either as total or speparately for its folders / .afpackage file. This might give an additional hint over the result of the package process, e.g. if the packing computer compares the size(s) with the initial sizes of the linked resources on disk.

Good idea, thanks for the feedback thomaso - I'll be sure to log this as an improvement request with the team

[Guest]

Thanks, Dan C 🙂

Quote

 

I'm glad to hear this - does this remain true after editing the file for a few days? 

I hope so but I don't know because actually I have no more photos I could add – the book now contains photos from childhood to today and I have to take new pictures first 😅
Maybe it's possible to use this forum again when I notice it doesn't work again within the next months?

Thanks to everyone who helped me!!!

[Dan C]

No problem at all, I certainly understand!

On 8/6/2023 at 7:52 AM, Maui said:

Maybe it's possible to use this forum again when I notice it doesn't work again within the next months?

Absolutely - we hope that no further issues should occur but we're happy to help should you need it and you're welcome to create a new thread or post here as required 

[Guest]

Thank you so much! 😊

[Affinity Info Bot]

The issue "User .afpackage - Importing file claims 0 missing, though 90+ images are marked as missing after opening" (REF: AFB-8152) has been fixed by the developers in internal build "2.2.0.1951".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
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.