Word 2008 "Word Cannot Open this Document"

I couldn't find a better forum so I'll put this here.
I have Microsoft Word Version 12.0, and have had it installed for a few months. I set the saving format to compatable by default (so it makes .doc and not .docx). Yesterday I was working on a word file I had saved on my thumb drive and it worked fine. Today I try to open it (both on my Macbook, my iMac and on a PC I had access to) and it gives me the following error: "Word cannot open this document. The document might be in use or might not be a valid Word document". I have noticed that this has happened to half a dozen of my other word files also. I notice that on my Macbook all of the word files have the new plain black and white icons that show the text in tiny writing, while the ones I can't open have the old blue file icons (on other, older computers they seem the same).
So I have three questions:
Is this a problem others have faced? If so, how can I get around it?
Are those particular files just corrupted? If so, is this a problem I ought to be wary of with Word 12?
If they are corrupted, is there any way I can rescue these texts? It's a very important document.
I eagerly await your responses.

Have you tried the Microsoft Word for macs forums? http://www.officeformac.com/ProductForums/

Similar Messages

Word Web App cannot open this document due to an unknown error. If the problem persists, try opening the file in Microsoft Word.

Word Web App cannot open this document due to an unknown error. If the problem persists, try opening the file in Microsoft Word.
Can anybody pls help me how to resolve this for which got strucked !!!!
Cheers !!
Praveen
Thanks in Advance !!! Cheers !!! Praveen

Hi Satheesh,
Thanks for quick Reply !!!
can u pls have a look that the below are Log Errors am getting .
Pls suggest me how to resolve that the all the services are in the running state only ,
1. Could not find default ServiceProxy or it does not implement
IWacServiceApplicationProxy.
2. Default service proxy not found while trying to get setting
WORDVIEWERSILVERLIGHTONLY.
Rgrds//Praveen
Thanks in Advance !!! Cheers !!! Praveen

Word cannot open this document. The document might be in use, the document might not be a valid Word document, or the file name might contain invalid characters (for example,\ /).

I recently upgraded to a new Macbook Air running Lion, from my 2007 white Macbook running Snow Leopard. I had Office for Mac 2004 on the 2007, but had to upgrade to Office for Mac 2011 to be compatible with Lion on the Air. Now when I try to open my documents on the Air that were saved under Office 2004 on the old computer, I get the following message: Word cannot open this document. The document might be in use, the document might not be a valid Word document, or the file name might contain invalid characters (for example,\ /).
Any suggestions? Thank you.

Ha,ha,ha.....I figured it out. But for anyone else who's having this problem, it seems that while Office 2004 allowed dates in this format: 00/00/00, Office 2011 doesn't like it at all. I just changed the format in the document names to 00-00-00 and all is well. Documents are opening beautifully!

Error word web app can not open this document for viewing in office web apps 2010

Hi
i am receiving office web apps error.
i installed sharepoint 2010 on windows server 2012 datacenter,
and installed office web apps 2010 and sp2
adil

Hi Adil,
From the error message, I recommend to check the things below:
Check if Word Viewing service is started in Central Administration. If it is started, stop and re-start it.
Check if the Word Viewing service proxy is created.
Check if the Word Viewing service proxy is associated with web application with issue.
If above cannot work, please check the ULS log for further research.
More reference:
https://amalhashim.wordpress.com/2013/01/29/sharepoint-word-web-app-cannot-open-this-document-for-viewing-because-of-an-unexpected-error/
Best regards.
Thanks
Victoria Xia
TechNet Community Support

After migrating to a new MBP, when saving or opening documents, I sometimes (but not always) get a warning such as: "Word cannot save this document due to a naming or permissions error on the destination volume." Can someone please explain?

I recently migrated from a MBP with OS 10.6 to a MCB with OS 10.8. Some glitches are popping up. Here's the one on my mind at the moment:
When saving or opening documents, I get a warning such as: "Word cannot save this document due to a naming or permissions error on the destination volume." Can someone please explain?

Since this is isolated to a single file, try exporting it to Interchange Format (.inx), then open and save the resulting file as a new InDesign file.
Since the problem occurs during export, that may not be possible. Another option to try would be to copy all elements, page by page, and "paste in place" into a new document the same size. If you used layers, be sure to enable "paste remembers layers" in the layers panel menu.
This kind of problem is often indicative of an underlying font issue. You said there are only three fonts, and you should verify that in Type > Find Font... Try replacing, at least temporarily the fonts in use with something else that you know to be reliable from other documents. You might want to do this before the other steps.
Peter

Word Web App (2013) can't open this document ... Because the service is busy

I have just set up Office Web Apps Server in a SharePoint 2013 test environment as per document here:
http://technet.microsoft.com/en-us/library/ff431687.aspx
Although I had some issues with Excel Web App at first, I've solved this and excel seems to work ok, However, the Word Web App just sits there spinning and ultimately give the error dialog:
"Sorry, Word Web App can't open this document because the service is busy. Please try again later" The Same link as above has a simple solution :
Did you install Office Web Apps Server on a domain controller? Office Web Apps Server cannot run on a domain controller. Office Web Apps Server must be installed on a separate server that is part of a domain. For more information, see
Software, hardware, and configuration requirements for Office Web Apps Server.
I certainly did not install on a DC - its a standalone server.
ULS Logs are growing by 2K per second even when I am not doing anything on the server.
VERY FRUSTRATED!

So after further research we have found the following:
Un-bind and unindstall Web Application Server
Clean Server
Reinstall (by Mistake to the C: Drive)
Bind and Provision
WOW it works!
Un-bind, deprovision, Uninstall, Web Application Server
clean Server
Re-install to the D: Drive
Provision and Bind
wow - it DOES NOT work
Again - repeat the first scenario
and once again IT WORKS
SO Why doesn't it work on the D Drive - We've checked IIS Setting and Permission - there don't seem to be any differences.
SO - Why isn't this working when changing the default installation location, is it just me? Has anyone gotten this working installing to another drive?
Thanks
James Moore

Went to open a file in words and got message. "You need a newer version of Pages to open this document." I have latest version. All other files open w/o a problem. Please help.

Went to open a file in words and got message. "You need a newer version of Pages to open this document." I have latest version. All other files in words open w/o a problem. Please help.
Thank you.
<Email Edited by Host>

You have 2 versions of Pages on your Mac.
Pages 5.2 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.2 can open Pages '09 files but may damage/alter them. It can not open Pages '08 files at all.
Older versions of Pages 5 can not open files from later versions of Pages 5.
Once opened and saved in Pages 5 the Pages '09 files can not be opened in Pages '09.
Anything that is saved to iCloud and opened in a newer version of Pages 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.
Apple has removed almost 100 features from Pages 5 and added many bugs:
http://www.freeforum101.com/iworktipsntrick/viewforum.php?f=22&sid=3527487677f0c 6fa05b6297cd00f8eb9&mforum=iworktipsntrick
Peter

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

Another "there was an error opening this document. this file cannot be found"-question

Hello people, as the title suggests, i have another question regarding the "there was an error opening this document. this file cannot be found" error. I have searched on Google and on these forums but i havent found an answer to my particular case (sorry if i overlooked it).
I work at a supportdesk for a company that uses Windows XP with Adobe Reader version 8.1.3.
Users are getting this error when they access a PDF file placed on a (mapped) networkdrive. Contrary to some other cases i have found on this forum, spaces are handled without a problem. But a comma in the name of one of the folders that contain the PDF file are what causes this error.
i.e.:
Opening the following path results in the error:
L:\X, Y & Z\adobe.pdf
Removing the comma so the path becomes:
L:\X Y & Z\adobe.pdf
works just fine.
So far our workaround has always been to simply remove the comma and move on, but I've been wondering why this comma is such a problem for Adobe Reader. As far as i know Adobe Reader is the only program we use that has this issue, M$ Word works just fine with it to name an example.
To sum my questions up:
- Why is comma (,) a problem for Adobe Reader?
- Have i missed any patches/new versions where this issue has been addressed?
- What is Adobe's stance on this, and are there any plans to "fix" this?

Ok, nevermind, we just found the problem
It's not Adobe Reader that is causing this, but another program the company uses to manage/distribute/authorise programs that users are allowed to access (Scense). I had never even considered another problem could have caused this for Reader.

Word 2008 will not open in Lion

I upgraded to Lion last night and had no problems with Word 2008 opening. Now, after a few restarts, Word 2008 will not open. When I click the icon on the dock, I get the following error message:
Microsoft Word.app/Contents/MacOS/Microsoft Word
0x8fe53000 - 0x8fe859c7 dyld (195.5 - ???) <134323A7-49DC-3A9D-ACFD-32FAD0FD6BA2> /usr/lib/dyld
Model: MacBookPro7,1, BootROM MBP71.0039.B0B, 2 processors, Intel Core 2 Duo, 2.4 GHz, 4 GB, SMC 1.62f6
Graphics: NVIDIA GeForce 320M, NVIDIA GeForce 320M, PCI, 256 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353637334648302D4346382020
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353637334648302D4346382020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.100.98.75.6)
Bluetooth: Version 2.5.0f17, 2 service, 12 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: Hitachi HTS545025B9SA02, 250.06 GB
Serial ATA Device: MATSHITADVD-R UJ-898
USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0x26100000 / 2
USB Device: Built-in iSight, apple_vendor_id, 0x8507, 0x24600000 / 2
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x06600000 / 4
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8213, 0x06610000 / 5
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0236, 0x06300000 / 3
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x06500000 / 2
Can anyone help explain what's going on?
Thanks!!

Hi,
No, no problems here with Office 2008, or 2011. Some people seem to think that 2008 had to be installed before the Lion OS was installed. I have reinstalled in on one of our machines that had issue with 2008, and I have installed after the Lion install was done. I had to install it twice as the first time didn't take.
You might try to reinstall Office 2008 - when I did it, the machine seemed to respond faster to opening Office documents, and we have had no glitches, so far, and that has been a couple of days.
I feel there are some possible issues, adn that Mickey Soft is working on it - I would expect an update from Mickey Soft, soon. It's not an Apple problem, as I see it, as over two dozen machines were updated that had Office 2008 on them, and ony one machine had issues.
Cheers,
M.

Message'there was an error opening this document.The file cannot be found'

Using xp home and when I click to download the pdf file, it will give 3 options been 'open'/'save'/?. When I choose the 'open' option, it will give me the above message "there was an error opening this document.The file cannot be found"
owever if I choose to "save" and I will be able to open the file and read it. In this pc its using Adobe Reader 8.1.2 with a patch. It was working fine prior to this sudden occurance of the error.
Strangely I have another pc with the same specification, I was able to choose "open" and be able to read the file. Can anyone help to resolve the issue by using the "open' option instead of "save, then open". Greateful for your prompt response.

Fyi, in addition to my earlier post, the other pc is using Adobe 8.1.1 and no other patch. I was trying to find 8.1.1 version but could not find a trust worthy site to load from. Do you think the error caused by using the 8.1.2 version? Thanks

There was an error opening this document. This file cannot be found

An automation script on one of our QA environments kept tripping on the error: "There was an error opening this document. This file cannot be found". The same script ran fine against our Production servers (hint, which were "whitelisted").
It took a little time to resolve/trace what was happening (but with the aid of ProcessMonitor and tracing all "pdf"-related file activity...)
The problem lies squarely between McAfee (75%), Adobe (20%) and Microsoft (5%):
NORMAL WORKFLOW. IE (Internet Explorer) when popping a PDF document, has to (1) write the document to the IE cache, then (2) launching and "handing off" the document reference to the Adobe viewer (which might then be able to open the document, et al) -- assuming largely a "synchronous" workflow.
BUT "WAIT", HOLD THE HORSES -- McAfee takes ownership and decides infact "wait for us" (during the workflow), it wants to first perform a virus scan on the document (ahead of writing the document to cache) involving potentially large latency (delay) before making the document available to the system. However, instead of "fessing up"-that their scan may be taking too long, McAfee appears to have taken their work "off-line" in violation of the sychronous interface above. I'm guessing the developers at McAfee might have been trying to hide any extra processing overhead being incurred by assuming they could somehow convert this to an "asychronous" event. (This may also have more reach than just PDF's.)
Unfortunately, the browser's "PDF OPEN"-dialog box pops allowing Adobe to launch-and-open the "as-yet-not-virus-scanned-and-thus-not-yet-cached"-document. Thus clicking the OPEN-button will cause the related "...FILE NOT FOUND"-error to be seen (because the file is still in McAfee "limbo").
Note: If you close the ADOBE reader (but don't yet close the popup-OPEN-dialog) you can click OPEN a second time and it will probably now open the document - which McAfee finally finished scanning!
You can observe all these interactions with ProcessMonitor, and use the monitored file states to adjust the timings of events to reproduce both the failure and non-failure scenarios.
- Best Regards, Ziggy
ps. My assessed distribution of "ownership" of the problem is because ALL these parties should be aggressively resolving this for the customer-base!

What, exactly, were you trying to do when you got it, and how?

I cannot re-open files that have been saved in Numbers version09 - it states "You need a newer version of numbers to open this document". This is the latest version

I cannot re-open files that have been saved in Numbers version09 - it states "You need a newer version of numbers to open this document". This is the latest version & also the one I have created/saved???

Jules,
You may delete Numbers 08 if you wish, but some folks like keeping it around. Close all your Numbers docs and Quit the Numbers app, and the other Numbers app if necessary.Then click the Numbers icon on your doc. Then select Numbers > About Numbers, and in the window that pops up, see which version it is. If the Dock icon started Numbers 08, you can cure that by dragging that icon off the Dock and letting it go in a puff of virtual smoke.
Now, to put the Numbers 09 icon on the Dock, double-click one of those known Numbers 09 documents so that Numbers 09 starts up. Verify by checkig Numbers > about Numbers.
Now click and hold the Numbers Dock icon and select the Option for Keep in Dock.
Jerry
Message was edited by: Jerrold Green1 -- I inadvertently posted about Pages rather than Numbers. Just corrected it.

Adobe reader: there was an error opening this document. this file cannot be found.

Windows XP Professional sp2 machine
512 memory
ie sp2
when opening two pdfs from a website links receive the error, "there was an error opening this document. this file cannot be found"
If you save the file to the pc, then open the .pdf it opens ok
other pdfs open ok from browser from same website and different websites
had customer try on another's machine; the two pdfs opened ok
tried Adobe Reader 8.1, 9.0, and Adobe Professional 8.0
uninstalled reader and professional; deleted directories; reinstalled reader and professional(placed into a separate directory); same error
On the machine tried admin accounts, under customer's profile made admin account, renamed the customer's account so that another account was freshly generated, all generated the same error.
Ran ccleaner to clean up files in the registry and temporary internet files, then repaired adobe - same error
repaired internet explorer - same error
scoured web for same error but most were applications trying to open the pdfs, a few errors were for programming php, a lot of questions but few answers in context of current issue. the ccleaner and repairing ie were resolutions i found on the web.
nothing was listed in msoft's ie knowledgebased searched.
any help would be appreciated.

I get the same message when I try to open a pdf attachment in my free AOL e-mail account. This problem just started today for some unknown reason. I have Adobe Reader 9 and never had a problem before. If I forward e-mails with a pdf attachment to my Road Runner account, I can open it with no problem. I can't seem to find any answers to this problem. Frustrating! HELP!!!

Word 2008 "Word Cannot Open this Document"

Similar Messages

Maybe you are looking for