Benches macOS

14

Any tricks to recover a damaged Keynote d…

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Does anyone have any tips for rebuilding a Keynote file? I'm getting a message that says "Keynote can't open the file because it is damaged."

The problem I have is that it's been a couple of months since I last used the presentation (and it didn't have a problem back then), so my daily, weekly, and monthly backups all have the damaged version of the document on it.

So I don't know how it got damaged ... but now I'm facing rebuilding it.

I've looked at the package, and I see all of the graphics in there. And I see a bunch of screenshots in the Thumbs folder, so that'll help me recreate it. What I'm having trouble finding is a file that contained all of my speaker notes.

Has anyone else had to deal with this? Does anyone have a trick that they can share?

14 replies

Sign in or join Beachball Help to reply.

  1. 0

    KOENIG Yvan

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    All the text items are stored in the index.apxl.gz file.

    Double click it to expand it.

    I encountered two kinds of corruption:

    (a) the index.apxl.gz file doesn't expand. As far as I know, there is no way to repair that.

    (b) the index.apxl.gz file expands as index.apxl.

    You may open the expanded file with most Word Processor tool by drag & drop. I uses the free TextWrangler which is fair enough to highlight operators and operands.

    Search for "<sf:text-body>", your datas will be just afyer occurences of this string.

    Yvan KOENIG (from FRANCE vendredi 17 octobre 2008 12:25:57)

  2. 0

    chuckbo

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Well, that's what I was afraid of ... I'd been comparing the packages of the Keynote docs that opened with this one, and the corrupted one is missing that file. (But don't ask me how it disappeared, since I didn't have any problems with the presentation last time I used it, two months ago.)

  3. 0

    chuckbo

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    The file couldn't be recovered. The only thing that helped a little was to look inside the package. There were thumbnails of each of the slides, so I was able to recreate the order of the presentation, then I just had to completely re-do the effects and all of the notes that I use in the presentation.

    No one ever provided a hint as to how the file suddenly got corrupted, but I wonder if it might've happened when I was editing a presentation and Keynote froze up and I had to abort it. Maybe the file that got corrupted was the one being edited. Remind me to go back to a previous version if I ever encounter a force quit in Keynote again (or in Numbers or Pages).

  4. 0

    KOENIG Yvan

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    From my idisk:

    <http://idisk.me.com/koenigyvan-Public?view=web&gt;

    you may download

    for
    iWork:autoSaveiWork.zip

    Expand it,

    double click on "autosave&zip4iWork.applescript"

    Read the given explanations and apply them.

    When an iWork document is open for more than ten minutes after some changes, it is automatically saved as a native iWork's document AND as a zip archive of the same file. With such scheme, if you clobber a document for any reason, you have the archive as a backup (which may be revived by recovery programs if your HD fails).

    Yvan KOENIG (from FRANCE lundi 5 janvier 2009 18:17:40)

  5. 0

    gbdoc

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    +> I wonder if it might've happened when I was editing a presentation and Keynote froze up and I had to abort it. Maybe the file that got corrupted was the one being edited.+

    Whenever
    any app freezes while you're working with it, the doc you're working on at the time is quite likely (but not necessarily) to become corrupted. So whenever that happens, it's
    always wise to re-open your work as soon thereafter as possible. (In fact, when it's something important, like a presentation or database I'm working on, I don't simply re-open the app, I re-start my Mac.) Then there are two outcomes: either your doc opens OK:
    whew! Or, your doc doesn't open OK:
    **! But then you can try whatever is possible to repair/reconstitute it, and if that fails, you can fall back on your last good back-up.

    And for that reason
    never make a destructive back-up (the kind which overwrites your previous back-up, like with SuperDuper or CCC) until you've sorted the problem out. Of course, your situation is a good example of when Time Machine would have saved you easily.

  6. 0

    KOENIG Yvan

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    gbdoc wrote:

    And for that reason
    never make a destructive back-up (the kind which overwrites your previous back-up, like with SuperDuper or CCC) until you've sorted the problem out. Of course, your situation is a good example of when Time Machine would have saved you easily.

    It's a good exemple of when my autoSave script would have saved you easily.

    It stores date_time stamped zip archive of the documents.

    Yvan KOENIG (from FRANCE mardi 6 janvier 2009 11:52:20)

  7. 0

    chuckbo

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Actually, I just ran into another case this morning -- this time with a Numbers file.

    The file won't open because it says the Index.xml file is missing. That's the same thing that happened with my Keynote file.

    In this case, however, I know that I've never had to abort out of Numbers with this document open or force a machine reboot with the document open or anything like that. I built the doc about a year ago, and maybe 2 or 3 times last year, I opened it, edited one number, and closed it again.

    The thumbnail survives again, so maybe I'll be able to recreate the doc from that file.

  8. 0

    gbdoc

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Aha!!! Maybe you've got a bigger problem underlying both problems. Of course,
    ** happens, especially with electronic data, for all kinds of reasons, some of which may be simply bad karma. But: these two problems, both similar, separated by less than 3 months, are the kind of thing which is pretty unusual, at least on Macs (actually,
    most problems are pretty unusual on Macs, compared with Windows). The fact that they both happened to iWork docs may or may not be related. With such a scenario, I'd begin to look for and try to repair any underlying problem:

    How full is your disk? If it's more than 85%-90% full, you may not have enough contiguous free-space "headroom" for stuff to work right, and you risk damage - even including total, unrecoverable break-down.

    I'd get something like OnyX, Cocktail, Yasu, or applejack (all of which can be dl'd from VersionTracker) to give my disk a good cleaning and combing.

    I'd look at my disk and files with one of the industrial-strength maintenance apps, like DiskWarrior or TechTool Pro (preferably both) (Disk Utility is pretty wimpy, and it's finding of "no problems" isn't terribly reliable). With TTP, you can also do a surface scan (a good idea for a new disk, and then maybe once a year), which also blocks out bad blocks (this will take a veeeery long time - many, many hours, overnight). Also, with TTP, I'd defrag the disk - another long process (though faster than a surface scan), especially if it hasn't been done for a long time.

    Check the disk's S.M.A.R.T. status. If it's anything other than "verified", the disk is on it's deathbed. Back your data up and replace the sick drive ASAP.

    I'd re-install iWork.

    Beyond that: I notice you're using 10.4.2. While that, in itself, shouldn't be the cause your problem, you might consider updating, at least to 10.4.11 (and I'd DL and use the +combo update+, not Software Update), for 2 reasons (unless you have some particular reason to stick with what you're using): first, installing an update replaces a bunch of system-level files with new ones. If any of these were the cause of your problem, they'd be gone. Second, AFAIK, 10.4.11 was the most robust and problem-free iteration of the 10.4.x line. (IMO Leopard's better, and would give you the Time Machine option you don't have now, but it's $, a non-trivial variable.)

  9. 0

    chuckbo

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks for the reply and the suggestions.

    You're right that it could be karma, but to paraphrase Rex Stout's detective, in a variable world, coincidences do exist but should always be suspect.

    I think you're on target by suspecting the hard drive. I had one that died, so this is a new one with lots of space. I don't remember opening the file since the drive died, so it's quite conceivable that I'm seeing the remnant of a problem that's already been solved. And iWork got reinstalled when I got the new drive.

    I've gotten out of the habit of running my DiskWarrior to check things out monthly. I probably need to make that a recurring event in my OmniFocus.

    Couple of extra notes. I am running the latest OS (now it's 10.4.11), but I don't get this profile updated every time I update the system. And I'll get a new machine in March or whenever Snow Leopard comes out. I was actually trying to hold out until one of my most important software products finishes its conversion to OS X, but that's still several months away. So I think I'll be running two machines for awhile.

  10. 0

    KOENIG Yvan

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I knows two ways to get documents with no Index:

    (a) storing the docs on a network where they may be open by two users at the same time. Perfect soluce to kill a document

    (b) open a document in an account which is not the one where it was created. Each time I tried to do that, I killed the document.

    I'm not sure that a HD failure may do that, at least several times.

    As we are all supposed to know, the main rule with computers is BACKUP, BACKUP, BACKUP

    Yes, I shout to be heard 😉

    If we store copies of the native documents, we keep items which can't be restored by recovery programs if something fails at the HD level.

    Using one of my FREE tools allows us to keep

    (1) smaller backups

    (2) date_time stamped backups

    (3) backups which may be revived by recovery tools.

    Remember, insurances are always too expensive … before the accident.

    Of course, I'm not telling you that it would be useless to check your HD. Maybe it is highly filled (Mac OS X heavily uses virtual memory which is in fact HD space).

    In laptops, HD are 2"5 ones.

    I often read "small is beautiful" but remember than most often "small is also fragile".

    Yvan KOENIG (from FRANCE mardi 6 janvier 2009 16:24:23)

  11. 0

    gbdoc

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I can only reiterate your insistence on backup. There are only two kinds of computer users: those who have
    already lost all of their data at least once, and those who have +not yet+ lost all of their data at least once.

    But I'm not sure I agree with (or perhaps understand) some of your other points:

    1. If a doc is OK, it should be openable by anyone who has the app which created it, whether from another user account or an entirely separate Mac. If that's not your experience, perhaps there's something wrong with your user account.

    2. "Copies of native documents", to me, means "native documents", pure and simple, like Finder copies (or the kind made by some bootable-backup apps like SuperDuper or CCC, which are essentially the same). They are simply opened by the app which created them (KN, for instance). As soon as you say "restored", you're talking about some method (using any of a number of "backup" or "archiving" apps (like Retrospect, for instance), usually involving compression) which takes the native file and encodes it and saves the encoded doc. Such a file has to first be decoded, "restored", by the backup app which created it (Retrospect), before it can be used by the "native" app which created it (KN). I've always been reluctant to use those apps, because those two extra steps, encoding and decoding, add a risk of failure I'd rather avoid.

    To return to your backup advice: the price of external storage (external drives) has really gone down over the past several years, and is now in the range of $ .50 - $1.00/GB. That being the case, most usual home/small business users can (and arguably "should") probably keep
    both a full, bootable, native copy of their HD, as well as some kind of archived record of the past, like what you do, or Time Machine does. (Of course, you only have to back up what you don't want to risk losing - but for most of us, that means everything!)

  12. 0

    chuckbo

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I think I wrote my first article about the importance of backups back in 1989, so I've been an extreme advocate of that for a long time. I rotate nightly, weekly, and monthly backups. But the hurdle that this problem has with backups is that the file went bad at some unknown time, and now it's the bad version that's bad propagated through all of the backups. Timed backups, it seems, are effective for recovering from disasters or from sudden accidents. I'll be looking for Time Machine to supplement my backup strategy with its pattern that's a little more variable, activity-based instead of pure time-based backups.

  13. 0

    superpanic

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I have the same problem with a keynote document right now. The document can be viewed using "Quick Look" in Finder. So I will just have to rebuild the presentation from that...

  14. 0

    gissett

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    How can i convert it from the tumbnails ? because ypu can barely read it ...