index.xml file missing

Discussion in 'Mac Apps and Mac App Store' started by steve jr., Nov 4, 2007.

  1. macrumors 6502

    Jul 4, 2005
    Akron, OH
    Hello. I backed up all my files and did a clean install of leopard. I dumped my files and now, when I try to open a Pages document, I get: "Unable to open “insert_filename_here” because the document is invalid. The index.xml file is missing."

    Any suggestions? And I have noticed some of the files work, and others don't. Seems to be about 50/50. Same with all my Keynote files, except it just says the file is damaged.

    Any and all help is appreciated!

  2. thread starter macrumors 6502

    Jul 4, 2005
    Akron, OH
  3. macrumors newbie

    Jan 5, 2010
    Finally a solution which worked for me!

    I tried all the other suggested solutions for the dreaded "The index.xml file is missing" error when trying to open a corrupted Pages document. I had tried all the suggestions from 2007 to 2009 with no luck.

    Then, the last one I came across recommended renaming the file from "[file name].pages" to "[file name]" and then opening it on my Mac. I tried this, but it still didn't work. So I emailed the file to myself at work where i use PC's, and lo and behold I was able to open the file with the intrinsic Windows XP Compressed Folders. I assume that this could probably be done in Windows in Parallels as well, and other applications like Winzip might work just as well as the Compressed Folders in Windows XP.

    After opening it, I found the .pdf preview file (Thanks heavens for saving a preview in the Pages document) and I sent this back to myself at my Mac. Voila! I opened the PDF in Preview, copied, and pasted the text back into a Pages document (with saved preview!). Hope this helps!

  4. macrumors newbie

    Jul 5, 2009
    Solution: You're on the right track but windows not necessary

    Essentially the .pages file is a folder but Apple makes it no longer seen as one so 'Show Package Contents' is not an option in the contextual menu (right-click). To resolve this error you NEED to have the index.xml file present at the top of the pages package.

    SOLUTION: rename the file to .zip. Double-click this file to unzip and you should now have:
    as a folder in the same location. Open that folder and:
    1. If the
    file is already there it may have just been inaccesible due to file not being saved completely the last time. Rename folder to '
    ', reopen in Pages and hopefully it should work.
    2. If the
    file is missing, I've read elsewhere that there should be a index-new.xml file that you can rename and follow the rest of the procedure in Step 1.
    3. #1 solved it for me so beyond this I'm not sure, perhaps you could borrow this index.xml file from another pages document to recover at least something from a working file.
  5. macrumors newbie

    Nov 21, 2010
    Thank you it worked

    I do appreciate your solution Yidaki. My file is now open in Pages.

    Kind regards
    Wayne :D
  6. macrumors newbie

    Aug 22, 2014
    Need help

    All my pages documents on my desktop will not open as of today. I get the message that the index.xml is missing. I've tried to rename document.pages to but then I can't double click it because it turns into a folder and there are no files with the name of my document in it.

    What happened to cause this and can anything short of swearing off Apple computers help?
  7. macrumors newbie

    May 4, 2015
    This index.xml fix worked for me

    I discovered the index.xml / Pages problem only today – couldn't open any files created in or before August 2014. As these forums are always very helpful, I thought I would share the fix that worked for me (after trying many others).

    The problem: Pages 5.2.2 in OS 10.9.5 does not open Pages documents previous to iWork upgrade of August, 2014.

    Pages 5 says: "file cannot be opened" (not very informative). Pages 4 says: "index.xml file is missing" (a bit more helpful).

    What worked for me: go to the file. Open the file package (right-click the file), unpack the file (double click it). Then back to the problematic file, double-click, open sesame.

    There are a lot of fixes floating around. I guess with different versions of documents and Pages-upgrades different fixes are necessary.
  8. macrumors newbie

    Oct 16, 2015

Share This Page