.Numbers" could not be opened

After restarting my computer for some updates, this file no longer opens.
are there any known ways to recover in these situations? except for from backups obviously.
cheers all for any help.

I used the advice here http://hints.macworld.com/article.php?story=20090225034801527
and managed to open up the contents of the document, I got the following
QuickLook (folder)
    Thumbnail,jpg
BuildVersionHistory.plist
F154FBetcetcetc.chrtshr
index.xml
not sure what I can use those to achieve...

Similar Messages

  • The document "03540 phone numbers" could not be opened.

    strange problem with numbers:
    suddenly have following message:
    The document “03540 phone numbers” could not be opened.
    have it on every file I try to open with numbers. Pages works normally.
    Anyone experienced something like this?
    How to get round it?
    Mark

    tried to open with time machine (yes, I do backups   :-)    but how does this system work?  I can get a preview of the file, but again can' t open it.
    a new file I created, I do am able to open it.

  • The document "navidad.numbers" could not be opened.

    I created a document during december, and now I can't open it. It's really important, I need help here.
    I doesn't gives me any explanation only the pop up saying: The document “navidad.numbers” could not be opened.
    Message was edited by: jaimemtz

    jaimemtz:
    This might not help you at this point, but maybe if someone else comes along later, it will help them solve their problem.
    I just had this exact same problem and from the looks of your document title, my fix might work for yours as well.  I fixed the file by editing the index.xml file in the corrupted numbers file.  Numbers '09 doesn't save documents as folders by default anymore, but you should be able to unzip them to folders using something like Unarchiver, 7zip, or a similar program (I used my default archive extraction program, which is called "The Unarchiver").  My problem was that I had put an obscure unicode character in the name of one of my tables.  Look at the console output in Console.app and see if something similar doesn't show up.  I just went into the text file, changed the offending characters to something from ASCII, and renamed the (unzipped) folder to have the .numbers extension, and the file openned without any issues.
    Anyway, like I said, probably won't help at this point, but maybe it will help someone else later.
    David

  • The document "abc.numbers" could not be opened [Numbers 09]

    I’m getting the document “abc.numbers” could not be opened message. I’ve seen this posted about Numbers ’08 but I’m getting this dreaded message with Numbers ’09.
    I’ve unzipped the file and cannot find anything that looks out of the ordinary to me. The buildVersionHistory.plist looks fine, as does the index.xml and QuickLook folder. When I compare these to a new, empty numbers file I can’t see differences besides those expected.
    Any help would be very much appreciated!

    May you attach the beast to a mail and send them to my mailbox ?
    Click my blue name to get my address.
    I wiil try to discover what is wrong.
    I guess that something is wrong in the index.xml file.
    I received several documents with this kind of problem.
    In some of them, the xml file was truncated, in others, it appeared as a 'correctly built' file but Numbers was unable to decipher it. One erroneous character is sufficient to render such a file unusable.
    This is why I wrote many times : backup, backup, backup…
    This means : keep consecutive copies as my backup script is able to build.
    Yvan KOENIG (VALLAURIS, France) samedi 23 janvier 2010 16:05:04

  • The document "AUGUST2010CHBOOKREGISTER.numbers" could not be opened.

    Ummmm. This document was made with a ready made template from inumbers. Really need to get the info out of it.
    Thanks for any help in advance.

    The problem is certainly not the template.
    I never lost a line of datas with documents build from one of them.
    If you have backups in time machine refusing to open, the problem seems serious.
    I guess that Time Machine was already at work the last time you worked on the document.
    If I am right, *_at least the late backup saved before the last opening must be readable._*
    Yvan KOENIG (VALLAURIS, France) mardi 17 août 2010 22:08:28

  • Numbers document - could not be opened

    I have my family budget spreadsheet that I use daily. I only have one copy. I went to open today and it has come up with The document “xxx.numbers” could not be opened.  I can preview the document. I can see it as an attachement on my iphone and view it.  However it will not open on my iMac.  Any suggestions.

    Right-click on the file and choose Get Info.
    At the bottom of the info window is a section for Permissions.
    Ensure you're listed with read and write priveleges.
    If not, click the lock icon and provide your password to unlock the section, then change your priveleges to read & write using the dropdown (click on the little arrows in the privelege box).
    And you really should have a complete system backup - Hard Drives do fail!

  • How to open a Numbers doc after message "The document (name) could not be opened." is received?

    I opened an Excel file with multiple worksheets by doubleclicking on it, saved it as a Numbers file and made lots of changes to it. Now I can't open it at all. All I get is the message "The document (name) could not be opened."
    Any ideas?

    It seems that your doc is corrupted.
    Try to rename it from ********.numbers to ********.numbers.zip
    then double click it
    You will get a new ********.numbers file with the structure 'package'.
    Try to open it by double-click.
    Sometimes it works.
    Yvan KOENIG (VALLAURIS, France) jeudi 22 décembre 2011 13:16:28
    iMac 21”5, i7, 2.8 GHz, 12 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.2
    My iDisk is : <http://public.me.com/koenigyvan>
    Please : Search for questions similar to your own before submitting them to the community

  • TS4009 The document "Name" could not be opened. (Numbers file @ iCloud)

    I have a file saved at iCloud that can not be opened anymore.
    Numbers says: The document “Name” could not be opened.

    I've solved my problem by following instructions here:
    http://www.freeforum101.com/iworktipsntrick/viewtopic.php?t=308&mforum=iworktips ntrick
    Step-by-step:
    1. renamed .numbers-tef file to .pdf;
    2. control cliked - then - Show Package Contents
    3. double clicked index.xml.gz - index.xml has been created!
    4. renamed back .pdf to .numbers
    5. double cliked file and Bingo! Numbers opened the file.

  • Cannot open Pages documents that I've worked on.  I open a new document, work on it, then save and close it.  When I try to open the document again, I get the following message: The document "[name]" could not be opened. The file isn't in the correct form

    I cannot open Pages documents that I have worked on and saved.  When I try to reopen Pages documents that I've saved, I get the following
    message:
    "The document “[name of document]” could not be opened. The file isn’t in the correct format.
    The file might be corrupted, truncated, or in an unexpected format."
    I have downloaded the latest update to iWork, but that doesn't help.
    I use Mac OSX 10.6.7
    I am using Pages '09 version 4.0.5 (852)
    If anyone can help, I would greatly appreciate it.
    Best regards,
    New York Mac User

    A few general trouble shooting tips that may apply here:
    1. If you used Software Update to do the OS update(s) to reach 10.6.7, go to http://support.apple.com/downloads/ and download and apply the Mac OS v10.6.7 Combo Updater. The Combo Updater contains some fixes that were not included in the incremental updaters used by Software Update.
    1a. Check that you have the current version of Pages (and of the other iWork applications) installed. All three applications' current version numbers end in .0.5
    2. A common cause of malfunctioning applications is a corrupted preferences file (.plist file). Your Pages '09's plist is at yourname > Library > Preferences > com.apple.iWork.pages.plist
    Quit Pages, locate the file and Drag it to the Desktop (or to the Trash).
    Restart Pages and attempt to open one of the files.
    If all is well, Trash the plist file and empty the Trash.
    If there's no change, AND you've made changes to the Preferences that you wish to keep, drag the file back to its previous location, replacing any new one that has been created.
    Regards,
    Barry

  • Disk utility reports "Device could not be opened" - error when trying to format a new drive in a Mac Pro 1,1

    MacPro 1,1 Quadcore 3 GHz (2006 "Woodcrest")
    32 GB RAM
    ATI Radeon HD 5770
    OS X 10.7.5 Lion
    I have encountered the following behavior when trying to format a new drive with disk utility. This description has also been send via the Mac Pro feedback as a bug report to Apple.
    On searching the web and forums with this particular error message and behaviour I could not find any usful results. So maybe the following description may be helpful for some users.
    Best regards.
    1. Drive Bay 1 contains the original 250 GB Startupdisk. It works without errors.
    2. Drive Bays 3 and 4 contain each a WD Caviar Black 2 TB SATA 3 HDD. They work without errors.
    3. I have purchased a third WD Caviar Black 2 TB HDD.
    4. In Drive Bay 2 there has been a Seagate 750 GB HDD, which worked in conjunction with all the other drives without error.
    5. I exchanged the Seagate HDD in Drive Bay 2 with the new WD Caviar Black 2 TB HDD.
    6. On starting the system, it will report to initialize the new drive.
    7. On trying to initialize the new drive with disk utility it reports the error [translated from German] "Erasing of the volume has failed. The device could not be opened."
    8. I thought that the drive is faulty. Thus I created an RMA-Case at WD. They exchanged the drive without problems.
    9. On getting the exchanged WD Caviar Black 2 TB drive I put it in Drive Bay 2 as before.
    10. On trying to erase and format the exchange drive I got the same error message "Drive could not be opened."
    10.1 On selecting the physical drive in the devices list, disk utility reports all information in the bottom area of its window as usual, e. g. hard disk description, connection bus, type and place, capacity, write status, SMART-status, partition scheme.
    10.1 On leaving that drive selected in the devices list and clicking the info-button, disk utility will also report additional information as usual, e. g. Name, Type, partition scheme, media-identification, media name, media type, device tree, … , number of relocated sectors, etc.. All this information appears to be valid, as can be compared to the other devices information inside the other Drive Bays. Also the disk numbering scheme appears to be standard - 4 HDDs give the numbering disk0, disk1, disk2, disk3.
    10.2 From that information I conclude that the SATA-bus and connectors electrically work properly, the drive has spun up and can be accessed by the system normally.
    11. I powered down the computer, took out the HDDs from Drive Bays 3 and 4 and put the caddy with the new exchange drive in Drive Bay 4 [Maybe, I could have also just left it alone in Drive Bay 2, or 3].
    12. After powering on the system, disk utility will quick format the exchange drive without any error message. Also, when erasing again by selecting the option to write zeros to the drive, disk utility will finish without error.
    13. After disk utility finished formatting, I put back the original drives into Drive Bay 3 and 4 and put the now newly formatted drive back into Drive Bay 2.
    14. After switching on the computer the system start and login proceeds without any error message. All drives appear as expected on the desktop.

    If anyone is reading this still looking for what caused the issue and how to fix it here is what I discovered.
    The antivirus program our company uses, Bitdefender Antivirus Plus, was causing some of the PDF files not to open. After troubleshooting the different modules and settings the culprit was..
    Scan SSL in Privacy Control Settings. Turning it OFF solved the problem and all the PDF files that previously would not open now open just fine. This issue has been sent to Bitdefender for them to review. If you use a different antivirus program and are having this issue try locating the Scan SSL setting and see if turning it off solves the problem.

  • The document could not be opened

    I was working on a Numbers '08 document that consists of a few sheets. Last saved it an hour or so ago and now it won't open saying "The document "blahblah" could not be opened". Of course, there is no fresh backup as I have just entered a ton of data in the last few hours. There is a log being posted to Console that looks like a few lines in the form of +Numbers[538]: Object (0x3024500 of class __NSDictionary0) named "NSMutableDictionary-0" was already registered with another name "NSMutableDictionary-16".+ followed by +Numbers[538]: Caught the following exception while trying to open blahblah.numbers, * -[NSCFArray insertObject:atIndex:]: attempt to insert nil+, followed by more lines that look like +Numbers[538]: NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionary0 0x3024500 references name "NSMutableDictionary-0" instead of "NSMutableDictionary-44"+, and the last line is +Numbers[538]: Failed to open document, but no unrecoverable error+. I tried downloading iWork 09 trial, updated to the latest version in Software Update, same error. The document does display in QuickLook though. Trashed the prefs, restarted, all to no avail. Is there any app that understands the Numbers format that could be used to open/import and reexport the data, or perhaps some tool to fix the affected document? All other Numbers documents I tried open fine.
    On a (probably) unrelated note: after updating to Snow Leopard both Pages and Numbers stopped showing anything in the Open Recent submenu. Not sure it might be in any way related.
    I'll appreciate any ideas on what to try as I absolutely don't fancy re-typing all that data again into a new document.
    TIA

    KOENIG Yvan wrote:
    wh1tebalance wrote:
    I was working on a Numbers '08 document that consists of a few sheets. Last saved it an hour or so ago and now it won't open saying "The document "blahblah" could not be opened". Of course, there is no fresh backup as I have just entered a ton of data in the last few hours.
    Why "of course" ?
    When we work seriously, we save seriously and you didn't do that.
    Saving seriously means: save every 10 (about) minutes and keep the result of these repeated save task.
    No matter whether I work seriously or not, I have a habit of pressing Command-S every 1-2 minutes whenever it's available. I do this automatically and without thinking, ever since I started using Word 6. Used to work for me until today and needless to say, I have never seen documents get corrupted like that, for no obvious reason. If by "seriously" you mean cloning my HD every 10 minutes, then I guess I'm not very serious about saving my progress. Then again, I don't work for NASA.
    The minimal scheme is to use only save but activate the preference named "Back up previous version before saving".
    I wasn't aware of this option, thanks for pointing it out to me. Hopefully it will work for future incidents like this (although if Numbers is prone to such nasty data-losing bugs perhaps it's time to change the application).
    Given what you describe, the index.xml file describing the contents of your document is missing or corrupted.
    It's not missing, but obviously corrupted.
    You are a lucky guy as you may read the doc thanks to Quicklook.
    I guess..
    I am able to rebuild a document when the index is corrupted but readable with TextWrangler but I do that only for users working seriously !
    I might as well recreate it all from scratch.
    Perhaps I should rephrase my questions:
    • is this a known situation (a newly introduced bug related to Snow Leopard or something?) and if so perhaps someone may have come up with a way to fix the document?
    • or are there any apps that understand enough of the Numbers format that might just import the data from the document without getting stuck on whatever it is that Numbers gets stuck on?
    • any other ideas that might actually help?

  • Document could not be opened

    I am getting an error message "Document could not be opened" on the Numbers app - What is the best way to recover the document? Will the folks in the Genius Bar in the local Apple shop be able to help?

    First thing to do, assuming that it's named azerty.numbers, rename the doc as azerty.numbers.zip
    Double click it.
    If it behave the logical way, you will get a new document azerty.numbers of structure package.
    With a bit of luck you will be able to open it.
    If it doesn't, send the original to my mailbox. I would try to revive it.
    Click my blue name to get my address.
    Yvan KOENIG (VALLAURIS, France) jeudi 15 décembre 2011 21:05:47
    iMac 21”5, i7, 2.8 GHz, 12 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.2
    My iDisk is : <http://public.me.com/koenigyvan>
    Please : Search for questions similar to your own before submitting them to the community

  • TS3991 "The document "Document Name" could not be opened"... Why?

    I have 10 Numbers documents on iCloud, but 7 are unable to be opened.. It says: “Document Name” could not be opened" on all my devices.. iPad, Macbook and iPhone...

    http://www.videolan.org/vlc/download-macosx.html

  • My document.numbers can not be opened how can i recover the version from yesterday i was not using time machine and it was not in icloud. is there an app i can buy that might help

    my document.numbers can not be opened how can i recover the version from yesterday? i was not using time machine and it was not in icloud. is there an app i can buy that might help

    Thanks Andy,
    I wish I could have told my sister about this as she could not open my homepage back before my new iWeb site. She now can open my site without the yet in case denial window does appear = I thank you.
    I think my iWeb site works as Noone has said otherwise from any platform etc...
    Alex L
    I do agree that should not have to be a consideration for any users so i agree that it would be great if Apple could allow simplicity to run seemlessly.
    I have had this problem since Homepage, and here is
    what has worked for me. I send out the link, and
    then for PC users I send the link with "<" after the address (without quotation
    marks. e.g., <http://site.com>).
    I also put a note that if that doesn't work, to just
    copy and paste the link into a browser. With that I
    have only had 1 person say they still can't open.
    Everyone else gets it to work.
    It's a lot to do and seems like a hassle, but you get
    used to it.
    Hope this helps!
    Andy Martini
    PS - APPLE! When are you going to fix this??! It
    seems like such a small thing yet you guys have been
    stumped for YEARS on this!

  • Warning, could not re-open xxyy.ear

    Hmm
    So, I'm happily trying to implement container managed relationships. I realised that I need local interfaces not remote ones, so I changed the two or three entities .. I created local interfaces (but didn't delete the remote ones (yet)) .. there's nothing to change in the bean itself is there? .. and noticed that in Sun's deployment tool I wasn't able to change those beans to use a local interface. That leads me to think that I'd missed something somewhere.
    Anyway, I tried to deploy and got a RemoteException: Error while validating XML deployment descriptors: Element "session" does not allow "ejb-ref" here.
    I had a look through the descriptors, and realised I'd missed out converting one of the beans, so I created local interfaces for that too. With me so far? OK, here's the crunch.
    The deploytool hung. I left it for half an hour (I've a slow m/c, running Linux), and it did nothing. So I closed it, closed the machine, and restarted.
    Now it says it "could not re-open xxyy.ear". It's "Trying to set an ejb-local ref on an ejb while the ejb does not define local interfaces."
    I tried to open the ear using the deploytool and it said the file is corrupt or cannot be read.
    What does this sound like to you? Did I miss something while creating local interfaces? Here's a localHome:
    import java.rmi.*;
    import java.util.*;
    import javax.ejb.*;
    public interface ProductLocalHome extends javax.ejb.EJBLocalHome
         // creates and initialises a bean instance
         public ProductLocal create (String pCode, String pName, String pDescription, boolean pDeprocated, boolean pDiscontinued, ProductTypeLocal pProductType) throws CreateException;
         public ProductLocal findByPrimaryKey (String primaryKey) throws FinderException;
    }Here's a local
    import java.rmi.*;
    import java.util.*;
    import javax.ejb.*;
    public interface ProductLocal extends EJBLocalObject
         // persistent fields
         public String getCode();
         public String getName();
         public String getDescription();
         public boolean getDeprocated();
         public boolean getDiscontinued();
         //public int getProductType();
         // notes say set methods aren't exposed to the public
         //public void setCode(String pCode);
         //public void setName(String pName);
         //public void setDescription(String pDescription);
         // select methods (carried over from ProductType)
         // public Collection getProducts() throws FinderException;
    }See anything wrong? Would I need to change anything in the bean to use local rather than remote interfaces?
    That ear file seems to be binary, is there another file with the deployment descriptors in that I can tinker with?
    If I have torebuild the file, I'm not sure where to start .. with the front end or the back end.
    J

    Sorry, I'm not sure why that message above is so wide.
    Anyway, would it work to bring back xxyy.ear from backup? Although it's a few weeks old (I knowwwww), actually my progress is pretty slow so that would be better than re-creating it from scratch. But would it work, or would I need to bring all the other files with it? If it did work on its own, it does create lots of files which seem to be sequentially numbered, would it handle finding a future number already in existence?
    J

Maybe you are looking for