Can't open Numbers document at all

Recently came to the "other side" and using latest mac book air and as far as I can see I don't have to update anything further. But I'm getting the same message here....see below. This is the same document that I created with the same version of numbers and now I can't open it. Weird thing is it still opens other Excel spreadsheets.

Hi Ben,
Just a thought. Is this something to do with the document name (all those dots ".") ?
Right click (or control click) on the document in Finder and choose Get Info. What does that show under Open with?
Regards,
Ian.

Similar Messages

  • Can't open numbers documents, says index.xml file is missing?

    can't open numbers documents, says index.xml file is missing

    I came across this problem after upgrading to Mavericks.  Here's what I did to solve the problem:
    Issue:  I began working on an existing spreadsheet.  After I saved it and tried to pull it up again later, I got the message "index.xml file is missing...".
    Go to your dock and delete the icon for Numbers (mine still referred to the previous version of Numbers). 
    Go to Applications and drag the Numbers icon to the dock.  This icon now links to the new version of Numbers and  (hopefully)  your spreadsheet should work.

  • Can't open Numbers document

    I spent almost 3 hours building a document, saving all along the way.... closed and opened it .... then changed the file name on my desktop, and now I can't open the file. I get the message The document "target.numbers could not be opened"
    In finder, I can get a quick preview ... just wont open the doc. HELP

    Maybe the doc is corrupted.
    You may attach it to a mail and send them to my mailbox.
    I will check if something is recoverable.
    Click my blue name to get my address.
    Yvan KOENIG (VALLAURIS, France) mardi 29 décembre 2009 16:56:10

  • Can't open Numbers document with newest version

    I have the newest version of numbers installed (3.0.1- at least, I think this is the most updated!), but when I try to open a numbers document, it says I need a newer version of Numbers to be able to open it. What do I need to check/do to access my documents?
    Well, nevermind. I think just quitting numbers and trying to open the document again worked.

    Hi Ben,
    Just a thought. Is this something to do with the document name (all those dots ".") ?
    Right click (or control click) on the document in Finder and choose Get Info. What does that show under Open with?
    Regards,
    Ian.

  • Can't open Numbers document.  Says I need to update, Can't open Numbers document.  Says I need to update

    I'm desperately trying to open a Numbers Document, but it keeps telling me I need to up-date.  However, everything is up to date.

    It looks like you are opening the old Numbers version by mistake. The Mac App Store kept the old Numbers version when you installed the most recent Numbers version in case you want to use it again.
    To fix this, open a Finder window, choose Applications in the sidebar and drag the new Numbers version to the Dock, so you can access to it quickly. Then, open Numbers and open your document from there. You will not get that message anymore.
    An easier solution would be to remove the old Numbers version, but I do not recommend you to do it. Some users have complained about the lack of features of the new version, so you may want to use the old version in the future

  • Can't open numbers document on mac!! Urgent please help

    Ok so i have a macbook air mid 2012. I had to reset my laptop the other day and since then i cannot open my urgent numbers document. I need this very soon so if anyone has any idea of whats going on please help!!! When i try to open it it tells me that the document is empty or that i need to purchase it again. But i have already purchased it. I moved it to trash as well then cleared it then downloaded it again but no luck!
    Thanks in Advance

    Hi Salves,
    Perhaps you now have two versions of Numbers on your machine, Numbers 2.3 (Numbers '09) and the latest version of Numbers (Numbers 3.2).
    The icon on your Dock may still be pointing to Numbers 2.3 (the old version). That will not open a document that has been converted to the new version (Numbers 3.2).
    Look in your Applications folder (inside a sub-folder called iWork '09) for Numbers 2.3. Do not delete this app!
    Look inside your Applications folder (not a sub-folder) for Numbers. That may be Numbers 3.2 (the latest version). Drag that to your Dock.
    Your Dock may now look like this:
    Numbers 2.3 on the left (3 column chart);
    Numbers 3.2 on the right (4 column chart).
    Wayne Contello has written a User Tip for working with the old and new versions of iWork.
    https://discussions.apple.com/docs/DOC-6991
    Regards,
    Ian.

  • I just updated my MAC operating system and when I went to open a recent document in numbers, the document that opened had none of my data and was formatted differently.  Can I get my document with all my information back?

    I just updated my MAC operating system and when I went to open a recent document in numbers, the document that opened had none of my data and was formatted differently.  Can I get my document with all my information back?

    I suggest the easy stuff first:
    1) quite Numbers and restart Numbers
    2) reboot the computer
    After that try opening the same document in another user space

  • Hello; I am using Numbers '09 version 2.1 (436). I tried unsuccessfully to upgrade at one point. Now can't open existing documents. Message "The index.xml file is missing".

    Hello; I am using Numbers '09 version 2.1 (436). I tried unsuccessfully to upgrade at one point. Now can't open existing documents. Message "The index.xml file is missing". How can I correct this ?
    Thank you
    Tom

    I't not iWeb that got damaged but the domain file. The index.xml file is inside the domain.sites file that's located in your Users/Home/Library/Application Support/iWeb folder. Do you have a backup of that file you can revert to?  If so then do it.  Otherwise a long shot but try the following:
    close iWeb.
    delete the iWeb preference file, com.apple.iWeb.plist, that resides in your Home/Library/Preferences folder.
    go to your Home/Library/Caches/com.apple.iWeb folder and delete its contents.
    launch iWeb and try again.
    If that doesn't help continue with:
    move the domain file from your Home/Library/Application Support/iWeb folder to the Desktop.
    launch iWeb, create a new test site, save the new domain file and close iWeb.
    go to the your Home/Library/Application Support/iWeb folder and delete the new domain file.
    move your original domain file from the Desktop to the iWeb folder.
    launch iWeb and try again.
    OT

  • Can't open numbers on my iPhone 5S and iPad mini (1st Gen.) after updating to the new version 2.0.1. Please help!

    Can't open numbers on my iPhone 5S and iPad mini (1st Gen.) after updating to the new version 2.0.1. Please help!

    Okay , you should only delete EMPTY DUPLICATED folders, not preview folders or any others. I would put them all back. Then just delete any DUPLICATED EMPTY folders, do not disturb any other folders. On iOS switch off DOCUMENTS AND DATA under ICLOUD in SETTINGS. Do this on all iOS devices not just the one. Once deleted DUPLICATE FOLDERS on the mac in MOBILE FOLDERS then exit the LIBRARY. Open PAGES on your MAC and view folders on icloud. Check everything is all there as expected. If okay then DELETE and re-install PAGES app on iOS - THEN switch on DATA and DOCUMENTS in ICLOUD. Now open PAGES. If you have Time Machine on you can recover any 'lost' doc files and restore them from your mac from pages application. Try the process again and do not disturb any folders other than ones I mentioned as this is the system files LIBRARY. It is not a place to be over zealous in moving, altering and deleting folders and files. Take care please.

  • Pages 5.0 can't open iCloud documents.  Has anybody run into this issue?

    Here's the story:
    I upgraded to Pages 5.0 and can't open .pages documents saved in icloud.
    It does not seem to be a file incompatibility.  I am creating files in Pages for Mac, saving them to iCloud.  They are immediately unable to re-open. 
    I only get a message saying:  The file “{file name}.pages” couldn’t be opened.
    Documents can be created without issue.  If they are saved to my local drive, I can open them again.
    Obviously, this makes it very difficult to use Pages with any other devices because document syncing is impossible.
    Details on my system:
    Mid-2010 13" Macbook pro
    2.4 Ghz core 2 duo
    8 GB ram
    OS X 10.9

    I was also experiencing same issues without being to open Older Pages Docs from iCloud in Pages 5.  I followed suneson Recommendation and process to the T...    Works perfectly. 
    Important to note you do have to do the second part in order for it to work completely.  I tested just the first half and still had issues.  Once Disabling and Re-enabling Documents and Clearing Cache - works perfectly now.  Thanks Suneson!
    Suneson process:
    Move all of your iCloud documents to a local folder (offline).
    Go to the iCloud preference pane i System Preferences.
    Click Manage... and delete all Pages data.
    The Next Step is required:
    Go back to iCloud preferences and uncheck "Documents & Data".
    Check it again.
    Delete ~/Library/Caches/--anything related to Pages or iWork--

  • Office Web Apps 2013 - Sorry, there was a problem and we can't open this document. If this happens again, try opening the document in Microsoft Word

    Hello
    I had configured Office Web Apps for SharePoint 2013 which was working fine for about 2 months until this morning.
    The error message I get for WORD, PDF and Excel files is:
    The ULS logs on the WFE give me this:
    WOPI (CheckFile) Proof Data: AccessToken Hash '1572676699' [1054 bytes], URL
    01/08/2014 11:01:58.01*    w3wp.exe (0x1368)                           0x09B4    SharePoint Foundation       
         WOPI                              afk59    Monitorable   
    WOPI                              agxqc    Medium      WOPI Signature verification
    attempt failed with public key 01/08/2014
    11:01:58.01     w3wp.exe (0x1368)                           0x09B4    SharePoint Foundation       
         WOPI                              agxqc    Medium      WOPI
    Signature verification attempt failed with public key
    01/08/2014 11:01:58.01     w3wp.exe (0x1368)                           0x09B4    SharePoint Foundation       
         WOPI                              agxqb    Medium      WOPI
    Signature verification attempt failed - no public key    e75ead18-af27-4d44-ba50-b38b408011e8
    01/08/2014 11:01:58.01     w3wp.exe (0x1368)                           0x09B4    SharePoint Foundation       
         WOPI                              ahdzz    Monitorable    WOPI
    Proof: All WOPI Signature verification attempts failed    e75ead18-af27-4d44-ba50-b38b408011e8
    01/08/2014 11:01:58.01     w3wp.exe (0x1368)                           0x09B4    SharePoint Foundation       
         WOPI                              ag7pj    Unexpected    WOPI
    (CheckFile) - Invalid Proof Signature for file Letterhead Template.docx  url: http://site.contoso.com/_vti_bin/wopi.ashx/files/9c5d0d7077aa43e9a9538c02deb57580?access_token=eyJ0eXAiOiJKV1QiLCJhbGciOi
    The ULS Logs on my Office Web Apps server gives me this:
    Error message from host: Verifying signature failed, host correlation:     d197d187-ef9d-42f6-ae4f-c4b8199c1078
    WOPICheckFile,WACSERVER FileNotFound
    WOPI CheckFile: Catch-All Failure [exception:Microsoft.Office.Web.Common.EnvironmentAdapters.FileUnknownException: WOPI 404
    Any idea what may have caused this issue all of a sudden?
    Thank you.
    Yoshi

    Hi Waqas
    Thanks for your help with this. I had a look at both posts, the URL works fine from the WAC server and I am not using a System account to test docs.
    Also, this is a production site that is accessible over the Internet, so we are using https therefore the WOPIZone is external-https.
    Issue #3 in the above blog link does not reflect the same error I see on my servers.
    I also had a look at the information in this link: http://technet.microsoft.com/en-us/library/ff431687.aspx#oauth
    Problem: You receive a "Sorry, there was a problem and we can't open this document" error when you try to view an Office document in Office Web Apps.
    If you added domains to the Allow List by using the
    New-OfficeWebAppsHost cmdlet, make sure you’re accessing Office Web Apps from a host domain that’s in the Allow List. To view the host domains in the Allow List, on the Office Web Apps Server open the Windows PowerShell prompt as an administrator and run
    the Get-OfficeWebAppsHost cmdlet. To add a domain to the Allow List, use the
    New-OfficeWebAppsHost cmdlet.
    I have not added any domains to the Allow list so this did not help either. Should I add the domain?
    Any further help with this is much appreciated.
    Thanks again.
    Yoshi

  • I am getting error when hovering on document in sharepoint online "sorry there was a problem and we can't open this document.If this happens again, try opening the document in Microsoft Word"

     I am getting error when hovering on document in sharepoint online "sorry there was a problem and we can't open this document.If this happens again, try opening the document in Microsoft Word".I am sure that document is not corrupted and
    all. something it showing the preview and sometimes it throwing this error. I hope this error is intermident. When clicking on the link also it throws this error but on refreshing it working fine. I dont know why it is happening. Please helpme  to resolve
    this issue. 

    Hi Waqas
    Thanks for your help with this. I had a look at both posts, the URL works fine from the WAC server and I am not using a System account to test docs.
    Also, this is a production site that is accessible over the Internet, so we are using https therefore the WOPIZone is external-https.
    Issue #3 in the above blog link does not reflect the same error I see on my servers.
    I also had a look at the information in this link: http://technet.microsoft.com/en-us/library/ff431687.aspx#oauth
    Problem: You receive a "Sorry, there was a problem and we can't open this document" error when you try to view an Office document in Office Web Apps.
    If you added domains to the Allow List by using the
    New-OfficeWebAppsHost cmdlet, make sure you’re accessing Office Web Apps from a host domain that’s in the Allow List. To view the host domains in the Allow List, on the Office Web Apps Server open the Windows PowerShell prompt as an administrator and run
    the Get-OfficeWebAppsHost cmdlet. To add a domain to the Allow List, use the
    New-OfficeWebAppsHost cmdlet.
    I have not added any domains to the Allow list so this did not help either. Should I add the domain?
    Any further help with this is much appreciated.
    Thanks again.
    Yoshi

  • Can't open secured documents on windows 7 domain client with mandatory profiles.

    While opening certain PDF files we have the problem that the user is presented with a message that he does not have the rights permissions. This happens twice, after that the users gets an empty page with the message the Adobe version might not be up to date. We use Acrobat Pro 10, but this also happens while using Reader 11.0.8. On our windows 2008 terminal services machine this could be fixed by giving the user rights on c:\ to create and remove a file. :O. On windows 7 this doesn't work probably because of UAC. But we've tried every solution to that available on the internet, disabling uac, changing uac options, changing rights on userprofile folders, changing rights on c:\ but to no avail. When using process explorer we can see it wants to create a temp file p328hkl.tmp or something like that on C but it can't and immediattely after is shows the error on screen.
    Anyone who also has this problem or solved it? There are no problems with simple self made pdf files/scans but only with certain types of pdf files for which it tries to create a tmp file.
    Thanks,
    Peter

    Hi Brogers,
    Thanks for your reaction. We do have AppData redirection in place. We redirect AppData to a share on our data server which works perfectly fine for all other applications. The weird thing is that Reader/Acrobat try to write to C:\ which to my knowledge should not happen, is this maybe a fallback because it can’t write to a different location? Users have full control on their own roaming AppData but not on their local AppData that is made by windows itself while copying the mandatory default profile to C:\.
    I might use the wrong term while saying secured documents. I’m talking about a document created by Raet/Youforce a web application for personal administration. The documents can be opened by other viewers than Acrobat/Reader but then only contain the background and not the text. In Acrobat/Reader they do open normally when Acrobat/Reader can create the .tmp file. Otherwise it will not display the file at all. I would attach such a document to see but since it contains certain info I am not allowed to do so.
    I hope we can work out a solution for this.
    Met vriendelijke groet,
    Peter Gerritsen
    Engineer
    AndoBurg BV
    Voorstraat 31
    3931 HB Woudenberg
    T 033 479 40 80
    F 033 479 40 89
    E [email protected]<mailto:[email protected]>
    I www.andoburg.com<http://www.andoburg.com/>
    Als u niet de geadresseerde van dit bericht bent, verzoeken wij u ons hiervan op de hoogte te brengen en het bericht te verwijderen. AndoBurg BV aanvaardt geen aansprakelijkheid voor schade die voortvloeit uit elektronische verzending van informatie. Aan de inhoud van deze e-mail en eventuele bijlagen kunnen geen rechten worden ontleend, tenzij schriftelijk anders is overeengekomen.
    Van: brogers_1
    Verzonden: vrijdag 19 september 2014 20:10
    Aan: Peter Gerritsen
    Onderwerp:  Can't open secured documents on windows 7 domain client with mandatory profiles.
    Can't open secured documents on windows 7 domain client with mandatory profiles.
    created by brogers_1<https://forums.adobe.com/people/brogers_1> in Enterprise Deployment (Acrobat and Reader) - View the full discussion<https://forums.adobe.com/message/6745441#6745441>

  • Can't open a document I created an hour before with Pages 5.0.1; get message saying my Pages is too old, for me to download 5.0.1

    Can't open a document I created an hour before with Pages 5.0.1; get message saying my Pages is too old, for me to download 5.0.1

    You have 2 versions of Pages on your Mac.
    Pages 5 is in your Applications folder.
    Pages '09/'08 is in your Applications/iWork folder.
    You are alternately opening the wrong versions.
    Pages '09/'08 can not open Pages 5 files and you will get the warning that you need a newer version.
    Pages 5 can open Pages '09 files but may damage/alter them. It can not open Pages '08 files at all.
    Once opened and saved in Pages 5 the Pages '09 files can not be opened in Pages '09.
    Anything that is saved to iCloud is also converted to Pages 5 files.
    All Pages files no matter what version and incompatibility have the same extension .pages.
    Pages 5 files are now only compatible with themselves on a very restricted set of hardware, software and Operating Systems and will not transfer correctly on any other server software than iCloud.
    Note: Apple has removed over 90 features from Pages 5 and added many bugs:
    http://www.freeforum101.com/iworktipsntrick/viewforum.php?f=22&sid=3527487677f0c 6fa05b6297cd00f8eb9&mforum=iworktipsntrick
    Archive/trash Pages 5, after exporting all Pages 5 files to Pages '09 or Word .docx, and rate/review it in the App Store, then get back to work.
    Peter

  • Can't open Office documents from share on Windows 8

    We have a problem with a customer that they can't open Office documents(Word,Excel etc.) on Windows 8.1 image on a network share. The error message is just that the document can't open.
    The documents are on a sharepoint site and we can open the documents within the site and also we can open the Office documents on a Windows 7 image from the networkshares.
    Also can't open the documents if i copy them to the local desktop.
    I think there is a group policy for Windows 8 for this but I don't know for sure?
    Anybody?

    Hi,
    As I understand, the issue is that customers can’t open office documents on windows 8.1 on a network share or copying them to the local desktop.
    Per my test, I can open documents on windows 8.1 on a network share.
    1. By default, Word doesn't trust files in temp directories from your browser. You can add the
    network address and local address to the trusted list. From Word 2010/2013: Click File > Word Options > Trust Center->trust center setting->add new location.
    2. You can create a shortcut on the desktop using the network address and then open the documents by that way.
    3. To narrow down the research scope that you can create a new document library->Download a problematic file (an Excel workbook or a word document) to your local->Upload the local file to the new document library->do the same option to check if
    the same situation will occur.
    There is a similar case:
    http://superuser.com/questions/693871/word-2013-wont-open-files-downloaded-trust-center
    Best regards
    Sara Fan
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected].
    Hi Sara Fan,
    Thanks for your reply.
    I have added the profile to the trusted locations but without success. Also a shortcut is not working. I still can't open any Office document on that location(Error message: location ***.xxxx can't be opened). The problem occurs on every client.
    1. Opening Office documents under local administrator account, domain admin account is working fine
    2. Re-image the machine is not a solution
    4. All locations use the same Windows 8.1 image through SCCM
    3. When the user logon to another location(site) it's working fine and they can open Office documents so it seems site-specific
    4. The problem is specific from 2 sharepoint shares. We can open office documents from other shares.
    5. Can't open Office documents from the library on the sharepoint site(browser), but on another location it's working fine.
    Problem only occurs on Windows 8.1 image with domain users. Other locations of this company do not have the problem. Note, every location have their own OU for users/clients.
    Any other suggestions? 

Maybe you are looking for