Error: The document "filename.pages" couldn't be opened.

I got a new Mac Mini and put 2009 iWork on it and immediately ran the update. I can't open any documents!! All I get is "The document “filename.pages” couldn’t be opened." What is going on? I have a legitimate iWork disc and DO not want to have to buy anything again!

It is ALL documents I have made in ANY iWork program previously. I have included a couple.
I have also discovered that I cannot create any NEW documents. The template window comes up but is a black screen. If I hit "New Document" from the open window nothing comes up.
file://localhost/Users/jaimewilliams/Desktop/boysschedule.pages
file://localhost/Users/jaimewilliams/Desktop/bills.numbers

Similar Messages

  • When I try to open a pages document on my mac book pro it says "The file 'thesis.pages' couldn't be opened." But i can open the same file on my iPad and iPhone without a problem.

    When I try to open a pages document on my mac book pro it says "The file 'thesis.pages' couldn't be opened." But i can open the same file on my iPad and iPhone without a problem.

    Thanks very much for the instructions.  I encountered this problem this morning myself and the recommendation fixed the problem immediately.  When things like this happen with iCloud and Pages it makes me wonder if I might be better off using something else, having just recently had to fix the problem that the current Pages can't read documents I created with a much earlier version until they were "upgraded" by an interim version.

  • The file "Untitled.pages" couldn't be opened.

    Hi, how do I correct this error - I can't save anything in pages!
    - The file “Untitled.pages” couldn’t be opened. -
    Thanks,

    You have to tell us more.
    What version of Pages?
    Where are you saving to?
    The message is an opening error and you are saying you can't save?
    Which is it?
    Why is it called Unitiled?
    Peter

  • Preview gives error "The file ... couldn't be opened because you don't have permission to view it."

    Yesterday I could access all my pdf´s with Preview. Today I get the error "The file ... couldn’t be opened because you don’t have permission to view it." upon opening a pdf file with Preview. All other pdf viewers open the files with no problem.
    I repaired permissions with disk utitlity with no success.

    I booted into recovery and repaired disk permissions with the disk utility from there. That fixed it. Apperently it repairs more stuff than when you´re booted into the OS. But what an annoying bug, this happened twice to me already by now...

  • I keep getting this error: "the following disk images couldn't be opened"?

    I just downloaded airparrot and keep getting this message everytime I try to open the .dmg file : the following disk images couldn't be opened.
    I have tried re-starting my computer and re-downloading the file several times. Airparrot has not gotten back to me despite several emails. I'm really frusterated and wondering if anyone has any suggestions?

    If itn won't open then it is a corrupted download.

  • I almost always receive the message "[filename] file couldn't be opened" when opening an existing Pages file in iCloud. Does anyone know how to fix this?

    I am using a MacBook Pro running Yosemite 10.10.2, using Pages 5.5.2.
    I've tried signing off and on, and restarting my MacBook, which sometimes works, but the problem re-occurs. Same problem using Apple Numbers and iCloud.
    Opening local files seems to work more consistently.
    This issue has made Pages and iCloud fairly useless to me. Does anyone have any ideas how to correct this?
    Thanks.

    Hi Ibo,
    This is what just worked for me:
    In Finder, I've dragged all Pages files from the iCloud Drive to the Documents folder on my iMac. (Finder asks your confirmation to remove the files from iCloud; confirm that)
    Once they were on my local hard drive, the files could be opened again.
    It looks to me as if something has changed in iCloud quite recently, leading to this mess. Not the first time, I've had this before. Now it's back. Sigh. And, as you wrote, it renders iCloud fairly useless. Back to Dropbox I suppose.

  • Problem with Pages.  I have recently been unable to open Pages, or any documents from Pages on my iMac.  Pages seems to be in the Cloud and can open a list of the documents in Pages, but can't open any of those documents.

    Recently unable to open Pages or any documents therein.  It seems to be stuck in the Cloud.  Although I can open a list of the documents I can not open any of the documents. 

    The answer is simple...  If you want to remedy this, then don't save them as PDFs.
    Word opens Word and text documents.  Not PDFs.
    Also note that this forum is for troubleshooting Apple Software Update for Windows, a software package for Windows designed to update Apple products that run on Windows, and not related to Microsoft Office or your question in any way. If you have issues or questions about Office, it's probably best you post Office related questions on Microsoft's own forums for their Mac products.
    http://www.officeformac.com/productforums

  • The document "x.pages" could not be saved. No such file or directory

    I have a client machine that connects to an xserve/xraid that gets the error "The document 'thefilename.pages' could not be saved. No such file or directory" while attempting to save a file.
    The file in question does exist on the server as does the directory. In fact the file was opened from the server for editing. It's the saving back to the server that is causing an issue.
    The file can be saved to the desktop then copied back to the server, overwriting the old file but cannot be saved directly.
    Adding to the odd behavior is that the issue is not consistent. However it appears to happen most often later in the work day.
    I found a thread with a similar question but no answer and the thread was locked and could not be added to.
    Any ideas for a fix?

    tsavill wrote:
    I experience the same issue with iWorks Numbers when saving a locally worked-on file back to the network server. It only started happening after upgrading my local iMac to Snow Leopard (OS 10.6.1)- the server is running on Leopard (10.5.?). I suspect the problem lies in this upgrade incompatibility. Apple are taking their time fixing it-still occurs with OS 10.6.4. Or are the saying I should upgrade the OS on the server as well?
    (1) To check if there is an incompatibility, check if the file saved locally is in good health before moving it on the server.
    (2) Here we are end-users like you so we can't respond to questions asked to Apple.
    (3) I'm a bit surprised that you get corrupted files using a product which doesn't exist. There is no iWorks product. Apple never distribute such a product !
    Yvan KOENIG (VALLAURIS, France) mardi 19 octobre 2010 10:16:40

  • Saving iWork Document in Mavericks: "** Couldn't be opened"

    When trying to save a file from the dropdown menu or when closing a document the following message appears: The file “Untitled.pages” couldn’t be opened.
    Also the same problem with Keynote and Numbers.  Has happened since upgarding to Mavericks and the new associated iWork.
    Only a problem in my iMac.  Macbook is coping fine.
    Can work round it by using the dropdown on the title bar, but thats not ideal.
    Help!?

    When trying to save a file from the dropdown menu or when closing a document the following message appears: The file “Untitled.pages” couldn’t be opened.
    Also the same problem with Keynote and Numbers.  Has happened since upgarding to Mavericks and the new associated iWork.
    Only a problem in my iMac.  Macbook is coping fine.
    Can work round it by using the dropdown on the title bar, but thats not ideal.
    Help!?

  • The file "x.numbers" couldn't be opened.

    I don't use numbers on the Mac often, so don't know how long this problem has been there for (I generally use the iPad version).  When I try and open any of my iCloud saved versions it comes up with an error: The file "x.numbers" couldn't be opened.  This happens with all of my documents, all of which open fine on the iPad or iCloud.com.  If I download the document from iCloud it will open from my computer.  If I then save it back to the cloud I can no longer open it.  Everything is up to date, with the latest version (OS 10.9.4, Numbers 3.2).  Any advice?

    Hi Stephen,
    Apple Menu > System Preferences > iCloud
    Have you ticked Documents & Data?
    Regards,
    Ian.

  • Textedit won't allow me to save .txt file "The file "Untitled.txt" couldn't be opened."

    I have searched for this but couldn't find the answer for it. Everytime I use textedit and then tried to save my file I get the following error "The file "Untitled.txt" couldn't be opened." I am trying to save the file to my desktop with .txt extension but still not able to do so and it is driving me crazy.

    I have recently upgraded to Mavericks 10.9.2 - there are a number of glitches that I have noticed. Hopefully Apple will remedy the issues soon.
    Recently TextEdit has been behaving weirdly.
    I type a document and go to save and I get the following:
    I think you'll agree that the document exists, this is a screenshot of it.
    I know there is a "/" in the name and that Mac doesn't like it but the same problem exists with whatever name is used and in whichever location is selected for the save.
    Having run Macintosh since OS 8.6 I do have some working knowledge of how to resolve problems. My immediate action was to reboot the system. Nothing - same issue. I then moved to the Preferences directory (~/Library/Preferences) and did the usual trashing of the applications preferences. I noticed that in Mavericks there are way more associated preferences for each app. Nothing ventured, nothing gained, I trashed the lot and emptied the trash. I was not able to empty the trash entirely - the system informed me that one of the documents was in use. I did not have TextEdit running. I removed the offending file from the command line using rm.
    I then rebooted the system again and opened TextEdit and tried again and lo and behold the documents were able to be saved. However on inspection of the Preferences again I now find that TextEdit seems to have no preferences? See the Spotlight search below.
    Whilst I tend to adhere to the adage "if it ain't broke - don't fix it" in this case I would really rather like to see the TextEdit Prefs.
    Maybe there is a Mac-guru out there that can explain a) what is going on here b) how to reinstate some prefs for TextEdit as it would seem pretty normal that they exist. and c) what happens if TextEdit throws a wobbler again, I have no prefs to trash
    At this time of writing TextEdit seems to be behaving normally aside from the above mentioned prefs issue.

  • The document "SpeechSynthesisServer.app" could not be opened because it is damaged or incomplete.

    I just upgraded from Mac OSX 10.6.8 to OSX 10.8.
    I logged into my account for the first time and had this error:
    The document “SpeechSynthesisServer.app” could not be opened because it is damaged or incomplete.
    From what I've been able to find, the SpeechSynthesisServer.app has to do with the Text-to-speech recognition.
    Initially, I was unable to get text-to-speech to work correctly.  But after I reset the key command, it worked.
    Is this something I should worry about?

    jfaughnan wrote:
    I think this bug may hit people whose user accounts have gone through a few versions of OS X AND are going directly from Snow Leopard to Mountain Lion. In my case my user account started out with 10.2 - so it's picked up some cruft.
    There are several items in my non-admin user Preferences:Users and Groups:User:Login Items that are not in my Admin account user including an item called SpeechSynthesisServer. It had a yellow warning triangle next to it and the data type was unrecognized.
    I removed it from Login Items, logged out, logged in, and the bug was gone.
    The LoginIn item is referencing a system app, that app is still present post upgrade:
    /System/Library/Frameworks/ApplicationServices.framework/Versions/A
    /Frameworks/SpeechSynthesis.framework/Versions/A.
    I suspect the app is still important. DON'T TOUCH ANYTHING IN SYSTEM/LIBRARY. Just leave it alone
    iTunesHelper was also on the one user's LoginItems and I removed it.
    I think there are a couple of bugs with the Login Item migration from SL to ML. For example, a disk image I mounted showed with a yellow icon too. I removed it, added it back in, and it was fine.
    Thanks jf.  That's helpful.
    I installed ML an hour or so ago, going from 10.6.8 to 10.8.2.  Having read quite a few comments I decided to take my time over this.
    ML downloaded fine. About half an hour maybe.  Installed itself then my iMac was restarted and, hey-presto, I'm back in business with a new OS. 
    Bit worried that my iMac was now rather sluggish, but not overly so because some kind person had posted on the App store that his Mac speeded back up after he had restarted.  This proved the case for me too.
    Went through all the set up screen re iCloud and App store.  All the while I noticed my external backup drive was very busy too. Must be using it as temporary space I thought to myself.
    Anyway, I decided that the first thing I should do is run Software Update.  I had several items that needed updating and whilst one of them was installing, that dreaded message that all you guys are talking about popped up.  I took a screen shot for later.
    https://dl.dropbox.com/u/11373233/MacDiscussions/SpeechSynth%202012-12-08%20at%2 016.05.39.png
    Not long after this my iMac's sceen turned black.  I assumed this was due to the screen saver cutting in.  It had done so about every 5 minutes during the time ML was downloading - apparently without causing a problem. I left it a while, then fired up the screen again.  Then I got a dreadful fright when a message came up full screen telling me my iMac had encountered a problem and it was having to restart! 
    I decided toplay it cool and let everything play through and let the Mac restart, see what happens. Turned out I was worrying unnecessaryily, all I needed to do was run Software Update again.  I downloaded the items individually this time, not all in one go like before.  All seems okay - at the moment.
    I still don't know what this SpeechSynthesisServer.app problem is.  Text to Speech still seems to work.  I wonder if it has anything to do with the new Voice recognition that I'm itching to try out. 
    Anyway, I'm leaving Voice recog alone for now until I'm more familiear with ML.
    "DON'T TOUCH ANYTHING IN SYSTEM/LIBRARY."  I notice that the Library is now hidden from us. Maybe what you say is the reason why?
    By the way, I think I worked out why my iMac was sluggish when I first fired up ML.  Spotlight was rebuilding it's database!
    Message was edited by: El Deanio

  • Printing error: The document could not be printed. There are no pages selected.

    I know this has been asked multiple times by different people with different scenarios but none of the troubleshooting has yet worked for me.
    I have a PDF document that has been exported directly out of InDesign that gives me the above message. If I print the document one page at a time, it prints just fine. But if I print it as a whole document, or if I select a subset of pages, it gives me the No Pages Selected error (even when said subset of pages will print individually). I have tried exporting the document using various settings, I have tried converting any embedded documents to images first, I've copied the original InDesign file and tried exporting out of the copy, I have saved the PDF as an optimised PDF with all private application data removed etc, I've tried printing off other computers, I have even tried some of the apparent fixes that have worked for other users. Nothing has worked so far. All other documents that I print work fine, it is quite literally a single PDF that will not print.
    I'm running Creative Cloud for PC and all drivers are up to date.
    Any ideas?

    I have the same problem with my brother printer's

  • TextEdit: "The document 'filename.txt' could not be saved."

    This error is occurring frequently, to the point of extreme frustration. I keep a plain text file open all day at work and use it to keep track of minor things like calls and notes. Routinely, when I go to save this file, it reports the error message in my title. It also reports this error message occassionally:
    The document “filename.txt” could not be autosaved.
    Originally, I thought that it might be Dropbox doing it (since the file was in Dropbox). So, I moved it to my desktop and set up a cron to copy that desktop file into Dropbox every 60 seconds. In other words, Dropbox should have absolutely no bearing on the desktop file.
    Still, the error persists.
    So, when this happens, I copy the file's text to my clipboard, quit TextEdit without saving, then restart TextEdit, paste the text back in, and save. Between 30 seconds and 30 minutes later, I have the same issue again. I have to do this more times a day than I can count.
    Any help would be greatly appreciated.

    Associated console messages:
    4/18/12 4:53:39.622 PM [0x0-0x98d98d].com.apple.TextEdit: [ERROR] GSLibrary.c:_AddGenerationInternal:393  Failed to consume sandbox extension; error 12 (Cannot allocate memory)
    4/18/12 4:53:39.623 PM TextEdit: NSFileVersion tried to tried to add a new generation and failed. Versioned file URL: file://localhost/Users/myshortname/Library/Containers/com.apple.TextEdit/Data/D esktop/filename.txt, contents URL: file://localhost/Users/myshortname/Library/Containers/com.apple.TextEdit/Data/D esktop/filename.txt, error: Error Domain=GSLibraryErrorDomain Code=1 "The operation couldn’t be completed. (GSLibraryErrorDomain error 1.)" UserInfo=0x7f8d5ab49e60 {}
    4/18/12 4:53:39.623 PM TextEdit: NSDocument failed to preserve the old version of a document. Here's the error:
    Error Domain=GSLibraryErrorDomain Code=1 "The operation couldn’t be completed. (GSLibraryErrorDomain error 1.)" UserInfo=0x7f8d5ab49e60 {}

  • "ePub_Best_Practices_EN.pages" couldn't be opened. The required index.xml file is missing.

    I've been trying to open the "ePub Best Practices” sample document located at Creating ePub files with Pages but every time I try to open it in Pages '09 4.1, I get the error "“ePub_Best_Practices_EN.pages” couldn’t be opened. The required index.xml file is missing."
    Is the file from Apple's site corrupt? I see a bunch of people online have used it successfully, but I don't know when they downloaded it.  When I open the Zip file the only file inside is "ePub_Best_Practices_EN.pages" which does not open in Pages.
    Thank you!

    Hi Peter,
    Could I get the Pages 2009 version as well?
    I tried clicking on your name and looking for a way to e-mail you, but either it's no longer there or I'm missing something. What am I doing wrong? Or, is there another way to contact you w/o posting my e-mail address here?
    Best,
    -David

Maybe you are looking for