Slow word 2007

My word 2007 is responding so slowly to commands i cannot work on it.
Also when I save a file, send it ti my other laptop which is running fast, the document which is 74 pages long reopens with only 2 pages, 1 of them blank and the other is my first page which has text in it.
I have updated windows. Tried running the computer in safe mode and word will not even open in this mode?

Hi Dougall2014,
What is your current situation?
In addition to the suggestions provided by the others, please also refer to the following KB article for Word related issue:
How to troubleshoot problems that occur when you start or use Word
Further, experts on the following forum may share some insights regarding the issue here:
https://social.technet.microsoft.com/Forums/office/en-US/home?forum=word
Best regards
Michael Shao
TechNet Community Support

Similar Messages

Word 2007 Issue - Slow Opening Files

Hi,
I'm hoping someone else here has had or recognizes the issue I'm having.
When I open a file in Word 2007 whether its on the network or local, it takes an age to open.
If I open up word first, its lightning quick.
There are no add-ins (except smart tag), everything else is inactive.
Anyone recognize this? or put me in the direction of further tests I need to do?
Here is a process monitor capture here ive removed file locking, name collision and successful.
Im now stuck...
Thanks
Phil

Try This
OPENING .xls & .doc SLOWLY
If documents take a long time to open when double clicking the file in Explorer do the following:
Open Explorer, select “Tools” then “Folder Options”.
Select “File Types” tab then type in doc to locate the file extension.
When “DOC Microsoft Office Word 97 – 2003 Document” is highlighted click the “Advanced” button. If there is no advanced button click the “Restore” button. Now click “Advanced”.
Under “Actions” highlight “Open” then click “Edit”.
Click in the “Application used to perform action” window the press the “End” key to go to the end of the text.
There should be a /n /dde at the end of the line, press spacebar then enter “%1” (including quote marks).
Un-check the “Use DDE” box.
Click “OK”.
Click “OK”.
Click on DOC to highlight it then type in docx, repeat the above for docx files.
Click on DOCX to highlight it then type in xls to locate the file extension.
When “XLS Microsoft Office Word 97 – 2003 Worksheet” is highlighted click the “Advanced” button. If there is no advanced button click the “Restore” button. Now click “Advanced”.
Under “Actions” highlight “Open” then click “Edit”.
Click in the “Application used to perform action” window the press the “End” key to go to the end of the text.

Bug? Accessibility Tags Converting from Word 2007

This seems like a minor issue, but it's one that could create a lot of frustration for a disabled person using a screenreader to read tabular data in a PDF.
As you know, Acrobat plays nicely with Office apps allowing users to create tagged (structured), accessible PDF documents from MS Office files. I just created a simple docx file with a table (attached), and when I converted it to PDF, I noticed a difference in the tags it creates compared to conversion from Word XP. As you see in the Word file, the table is very basic, except that one of its column headers is split into two cells. This is actually a very common technique for presenting table data. In order to automatically tag the header rows as table header cells <TH> in the PDF, I set the first two rows to "Repeat Header Rows."
Converting from Word 2007 with the "Save as Adobe PDF," or any other method that uses the Acrobat plugin, creates a tag tree that is missing a <TH> tag. I found the problem when I was testing a file with JAWS screenreading software. Using the JAWS "current cell" command (Ctrl-Alt-Numpad 5) to announce the column headers. It reads the wrong header for the current cell due to the missing <TH>. So, in my example file, it announces $2 and $5 as 2010 amounts rather than 2009. That could be pretty confusing to a screen reading user, to say the least.
I then compared the result to the new Word 2007 "Save as PDF or XPS" feature. That feature tagged the file properly and the header columns match up.
Compare the attached "save-as-adobe-pdf.gif" to"save-as-pdf-xps.gif". Note the empty (but necessary) <TH> tag in the latter image.
Just as a sanity check I had a coworker with Word XP convert the file. Those tags were correct too. So, this must be a problem between Acrobat and Word 2007.
Anyone have other observations on this? I'm going to be leading some accessibility training and right now, it looks like using the Word 2007 conversion feature is the way to go.
I'm using Acrobat 9 Pro.
Thanks,
Joe

Hi Joe,
I sense your frustration. For any organization that has to or wants to engage in providing accessible online information
a serious logistics support issue raises its head. To do PDF, HTML, whatever the proper way (and it can be done)
requires more resources (training, knowledge, hardware, software, changes to work flows, perhaps some more staff).
The is no "work smarter with less & pump out more" in this venue.
Yes, it is helpful (and necessary) to "be one" with the S508 "paragraphs" - WCAG 1.0 - WCAG 20.
However, once anyone begins to provide PDFs that must be "accessible" the first, single most important reference is ISO 32000.
The Adobe PDF References that preceded PDF becoming an ISO Standard are useful; but, ISO 32000 is the standard.
In this documentation there is full discussion of what *must* be done to provide an accessible PDF.
Without a firm understanding of this content, other information tends to bring about a defused opacity of focus which can
contribute to major conceptual errors vis-a-vis accessible PDF.
Leonard Rosenthol's AUC blog entry provides a link to the ISO permitted Adobe version (free) of ISO 32000-1.
http://www.acrobatusers.com/blogs/leonardr/adobe-posts-free-iso-32000
Additional, useful information is found in these two documents:
(1) - PDF Accessibility API Reference (from the Acrobat SDK)
https://acrobat.com/#d=J7bWW4LvNoznh8fHCsfZDg
(2) - Reading PDF Files Through MSAA
https://acrobat.com/#d=uIOvkVTP74kag3bXFJLIeg
About JAWS - Yes, much used. However, not the exlusively used AT application.
If I use Windows Eyes, NVDA, a braille reader, or something else then what?
JAWS *does not* define "it is accessible"...
re: (1)
"Game away and if it ...."
   Consider "Stop before right on red".
   "Compliance" is Stop on Red - Turn Right
   "Intent" (aka usability) is Stop on Red - Look Good for on coming traffic that has the right of way - Yield - when clear, turn right.
But, at least we are not talking about "left on red" 8^)
re: (2)
Just an observation. A defective product that claims to be "whole" can get entities (individuals/businesses) into a sticky wicket.
Putting a high volume of defective products on one's selves only increases the probability that one gets 'busted'.
Quantity replacing Quality just is not a success precursor.
Case in point - Target and the national class action legal action that was taken against it with regards to "accessibility" of online information/services.
Resolved now - see NFB's web site.
re: (3)
Ah, but what would Judge Judy or Judge Marily say?
Efficiency does not preclude providing a "whole" product.
I doubt that there will ever be a seamless "one-click" between products of any of the dominant software houses.
They are intense competitors. That this is the case does not abrogate others from providing a "whole" product, no?
So, if the organization wants the "we do accessible PDF" label then it pays the freight - Adobe Pro, training, appropriate work flows, etc
that permit delivery of PDFs that meet the standards for what a well formed tagged output PDF is (accessible is a sub-set of this).
For PDF there is no other way.
If this cannot be done then there is always HTML as an acceptable method (to some it is the preferred and only "true" way).
However, HTML, done "right" for accessiblilty is just as demanding in its own way.
With each AT version / dot version release, JAWS - Windows Eyes - NVDA & others hone in closer on utilizing PDF ISO Standard 32000.
That means if you deploy "accessible" PDF you need to provide PDF that live to the ISO standard.
Keep in mind that S508's paragraphs began when, effectively, HTML was "it". In software terms that was geologic eons ago.
For contemporary AT to effectively parse PDF, the PDF must be a well formed Tagged PDF having a format/layout that reflects a logical hierarchy.
Creation of all this must start in the authoring environment with the content author.
The post-process PDF output then assures that the PDF elements (tags) are the correct type, have the requisite attributes, etc.
Without this, AT will not be able to provide the end-user effect utilization of the PDF.
So, for AT to properly 'work' the PDF, <TH> elements *must* have the Scope attribute's value defined, Row and Column Span values defined, etc.
Scope, Row Span, Column Span, Table IDs and Headings must be added as part of the post-processing of a PDF using Acrobat Professional.
An alternative is the Netcentric CommonLook plug-in for Acrobat Professional. What it does, Acrobat Pro can do; however, the CommonLook
provides a robust user interface. Downside: at some $1k per seat it is not 'cheap' and it has a *steep* learning curve (Sitka Pass?).
Two table related resources are at this AUC thread (in post 3 and 4). They may be of some usefulness.
http://www.acrobatusers.com/forums/aucbb/viewtopic.php?id=23178
When the "smelly stuff" gets feed into the maw of the fan it's prudent to not be directly down stream, eh.
Consider Target and the situation they put themselves in.
Consider submittal of accessible PDF to fedgov or stategov agencies.
They won't be in front of the fan if usability of the PDFs becomes an issue.
Rather, it will be those submitting. After all the agency did say "accessible".
Better to slow down and do it right or ramp up resource loading to support "schedule" than to stake oneself out as someones "feed" tomorrow, no?
In the final analysis, for PDF, HTML, or any 'format', Accessibility is the Usability + Compliance.
Does it take improvements in professional development/training, adequate hardware/software, *time*?
Yes. But, it all comes down to "where the rubber hits the road" - what tires are you on?
It can be done. I do it one small step at a time every day. Often, that's what it takes.
Deliverables are provided; but, with no mis-labeling and the incremental progress is identified, celebrated and the whole thing continues until
the "road" is completed properly.
Don't want wash outs, bridge collapse or what not tomorrow <g>.
(But then I'm a fan of "Holmes on Homes" which may go a long way towards understanding my point of view when it comes to accessible PDF.)
re: function(){Return ....
Good question.
My guess - either from the cut & paste I initially performed from the application I'd been using to assemble write up and screenshots or something associated with the Adobe Forum application.
It can't be that I'm 'special'; if that was the case one of my occassional lotto quick picks would have been a big $ winner long ago <G>.
fwiw -
You'll find a number of "Accessible PDF" related resources in the threads at the AUC Accessibility Forum.
http://www.acrobatusers.com/forums/aucbb/viewforum.php?id=18
Two Accessible PDF related on demand eSeminars are also available.
Look for Duff Johnson's and Charlie Pike's (on page 2) eSeminars.
http://www.acrobatusers.com/learning_center/eseminars_on_demand
Be well...

Adobe does not recognize footers in Microsoft Word 2007 to PDF

I have copied and pasted the details, below, from a previous message I have sent out to an assistive technology listserv.
I am encountering this problem with various builds and versions of Adobe Acrobat:
Acrobat X on a Windows Vista 64-bit build (note that this is the best Acrobat I can install on Windows Vista, Adobe Reader XI is not even supported)
Acrobat X on a Windows XP build, sorry, do not know the bit count (it is my work computer so I can't upgrade anything)
Acrobat 9 on a Windows 7 64-bit build.
I have also encountered and checked into whether or not the PDF reads (and does what I want it to) in JAWS 14, latest update (Feb 2013). We encounter the same problem with JAWS and this morning found out that there is a conversion error between Word and Adobe. (See this post, where the ---- are).
Summary, I have spoken with JAWS, put out a support ticket with NVDA via e-mail, spoken with Microsoft, and tried to communicate with Adobe about this issue for help and Adobe is refusing to help. The other places tried everything they knew but they could not get it to work. I even tried to strip all the page numbers from Word and number using Adobe's page numbering feature, but that was not successful either because I cannot use Roman numerals.
I would appreciate any feedback the Adobe Forums can give me; please note that I cannot post a sample document at this time as the only document I have is a private work document (cannot share those by policy, so I will have to make up a fake document if I get the time and energy).
Thank you very much for your time and expertise. The pertient info is above and below in "Original Message" and "Activities section" - the other information is there if you'd like to look. And to provide feedback to Adobe about things I think they could improve, since they will not let me email them directly.
----Original Message----
My question concerns the reading of Footers / Headers in Microsoft Word 2007 and Adobe Acrobat (headers/footers designed in Microsoft Word 2007 and then converted to PDF with "Bookmark" checked in Adobe Acrobat conversion settings).
The document is a word document containing 50+ pages. There are 12 pages of "front matter" that are marked with Roman numerals. Subsequently, the body text of the document has an Arabic number (1, 2, 3, 4, etc.) in the bottom right corner. Footers are used properly in the document. All Table of Contents links, which do link to both headings in the "front matter" and to headings in the body text, are picked up properly. Literately, the only thing not reading on the document are page numbers (the Word Status bar is reading its page numbers, but the page numbers in the footer are not reading).
I then need to convert the document to Adobe Acrobat PDF. Granted, I have a full copy of Adobe Acrobat X available to me, and my various assistive technologies have always functioned better when opened directly in Acrobat (rather than Adobe Reader). So, I set the accessibility options (from Word) properly, asking it to bookmark Headers and Footers as appropriate, thinking that this will pick up the page numbers and make them read as the bottom right corner of my PDF.
All links work in Adobe to navigate by section/heading. All figures are alt tagged. Everything is perfect - but the one thing that NVDA won't read are the page numbers. Visually, the page numbers are there on the document, but NVDA won't pick them up. Additionally, I also changed the appropriate page numbers in Adobe (Page Thumbnail Pane, on the Navigation Pane I believe it is called) - to reflect the section where it is Roman numerals and Arabic numerals. This did not help, and for what it is worth, I cannot get NVDA to voice when I am in this pane, so I don't seem to have a chance of getting the page number info from there.
NVDA reads the document just fine except for the above-mentioned snare. However, when it reads, it will go to the next page, and say, "Page 2 of 54, (page text), Page 3 of 54 (page text)," etc. when I will need it to say Page ii of 54 (page text), Page iii of 54 (page text)," and so on, changing to "Page 1" when the Arabic numbers are used.
I know that the Page Label issue is part of Adobe's issue, with them not releasing the PageLabel aspect. (I have looked through some NVDA tickets). I do not know how to put a "changeset" into my copy of NVDA though, or even if it would help (I have no computer scripting skill). The easy answer would be to upgrade to Adobe Reader XI and see if that helps, but I don't have the ability to put it on every computer I use, and *I need this file to read consistently across multiple versions of Adobe* (including Adobe Reader/Acrobat 9, X, and XI). (This file is also going out to people who may not have the latest version of Adobe, but are also running some copy of NVDA, either a portable or a full install).
Is there any way to pick up the Footers with page numbers voicing in NVDA, and/or have it read the user-editable page number box that is on Adobe's Toolbar (next to the 1 of 54 parentheses). This user-editable box, to jump to page numbers, reflects the Roman numerals I have loaded into the pages of Adobe. When I press Ctrl+Shift+N in Adobe, I can also go to the appropriate page (if I type in iii, it will take me to iii, if I type in 34, it will take me to the Arabic number 34 -- NOT the 34 of 54, which would land me on a different page. And I want to land on the page that has the Arabic 34, so that's functioning fine.
I just need the page numbers in the footer to voice, "Page iii," or "Page iv," or "Page 29," etc. If I could get NVDA to do that, I could say to viewers of this document, "If you are using NVDA, remember to Ctrl+Shift+N to get the GoTo Box, then type in the page number you want if you cannot follow a link or a bookmark." This document is *very* accessible in my opinion with lots of ways to navigate...the only aspect of navigation that isn't being picked up are those footer page numbers!
I do have my Document Formatting settings on the NVDA menu set to "Report Headers," but that does not seem to help in either Microsoft Word 2007 or Adobe Acrobat. I have even switched the page numbers from the footer to the header to see if that would help and it didn't.
----Activities I have done today----
I spent over an hour on the phone today with Freedom Scientific (makers of JAWS) trying to troubleshoot this. We discovered that Footers will not read very well in JAWS and Microsoft Word 2007 (only solution is to stop reading document text and read Virtual Viewer text briefly, then go back out to document text, then back into Virtual Viewer which is NOT an acceptable or accessible solution whatsoever -- too much work for someone trying to read the document) -- and then we also discovered that:
Upon conversion from Word 2007 to .txt file (.docx to .txt), there are no alt tags for the figures in the document, or page numbers.
Upon conversion from Word 2007 to Adobe Acrobat X then to .txt file, every insert of a page number and footer is replaced with the same alt numberpad numerical code: the one that generates female. ♀No wonder JAWS and NVDA are skipping this, neither understand how to communicate it.
On the advice of JAWS Technical Support I contacted Microsoft Accessibility Technical Support and spent an hour on the phone with them. They say that unless Adobe can find a solution, it appears that it is impossible for Microsoft products to read the footer if JAWS was unsuccessful doing what I wanted it to do. The document/footer in question includes about 12 pages of front matter (numbered in Roman numerals) and 44 pages of body text (numbered in Arabic numerals).
I kindly explained to the Microsoft Support Agent that I found this issue hard to believe, although I understood. Sighted folks have the ability to make their documents look quite professional and that is the caliber and quality of documents anticipated from everyone, especially college students graduating from school, or job applicants. That a coding issue prevents the footer from being read properly, except in Edit view, is disappointing. The representative was with me 100% of the way. She completely understood where I came from. And yes, when I am designing the document myself, I know what I put there (or I pretty much do, anyway). But if I recieve a document, it is much harder to tell what is really there or not, or how the page numbers really lay. And this is confusing as heck, believe me.
I then called Adobe Technical Support, after having a brief online chat with them. Granted, I had to leave the chat in the middle because I got interuptted by something that was high-priority, but the woman chatting from Adobe says that chat is only for installation issues, and I will have to pay to open a support ticket. Excuse me? I have paid a hefty sum of money for Adobe Acrobat 9 and Adobe Acrobat X (work paid for the other Acrobat X copy). I deserve this problem to be troubleshooted for free. There was even a statement on the Adobe Acrobat X website that said Acrobat X users didn't have to pay for support, but Reader users did.
----Slight bit of rant and constructive criticism----
In speaking with Adobe Technical Support, I had to wait on hold for 30 minutes before my call was answered, and then I had to consent to being on hold countless times and had to answer, "Yes, I am converting from Word 2007 to PDF using Adobe Acrobat X" at least 6 times. The representative would put me on hold, then ask me the question, then put me on hold again, repeated 6 times over 45 minutes. At the end of 45 minutes (1 hour and 20 minutes of wasted time by now, that I must justify to my employer) - I told the representative I wanted to speak with his supervisor immediately, I did not care if he was trying to fill out a support ticket (and putting me on hold at least 4 more times in 10 minutes while he claimed he was filling out the support ticket) - and finally he put me on hold again and gave me to a very helpful supervisor. Within 6 minutes of speaking with the supervisor the supervisor had my support ticket filled out and I should recieve a call from Adobe within the next 30 minutes if his estimation was right (he estimated two hours, but it's been an hour and a half).
I have yet to know what can be done about my document. Freedom Scientific Technical Support is closed now for the day and I need to work tomorrow and Friday away from the phone. As I stated to Microsoft Accessibility Support, I truly feel that Adobe should read the page footers, every document says that Adobe should be able to read the page footers, and I feel slighted that as a person who uses assistive technology, there is some glitch that isn't making this happen. I am not blaming a specific place per se, except I am a little frustrated with Adobe especially since they have not gotten back to me, and I am frustrated with their customer service. JAWS customer service and Microsoft customer service were both exemparly, and I cannot say enough good things about them. My wasted time with Adobe however, that was disrespect in my opinion. And I certainly will not pay to open a support ticket, and my workplace has a site license. They've paid enough already.
If you've read this far, thank you. I look forward to replies, or at least understanding. And if anyone has ideas, I'd appreciate it very much (yes, I have tried taking the page numbers off and using Adobe's page number feature, but that would not allow Roman numerals. Only Arabic.).

Greetings NoNameGiven,
If I understand the problem correctly (I’m not sure I do) you would prefer ‘iii’ to be read as “eye eye eye” rather than “three”? The alt text property is the only way that I know of to make this happen. Hope this helps.
a ‘C’ student

Error message: Missing PDF maker files in Word 2007

OK, I am beyond frustrated. I have had nothing but trouble with Windows Vista and Adobe Acrobat. Please help!!!
What happens: first, the pdf addin for Word 2007 suddenly becomes disabled, for no apparent reason. Forget about trying to re-enable it through the Add-Ins menu, because Word tells me that the "connected state of Office Add-Ins registered in the HKEY_LOCAL_MACHINE cannot be changed". This is a problem for me, because I use a special font (Vietnamese) that sometimes gets corrupted when running pdf maker. The only consistent way I have found to avoid this problem is to run the pdf maker as "Quick PDF" and as far as I can see that option is only available through the pdf addin in Word, I have never been able to find it when I open the Acrobat program and create a pdf from there.
Second problem: shortly after the pdf addin becomes disabled, my Acrobat program loses the ability to create pdfs altogether. I get the error message "Missing PDF maker files". Yes, I have tried repairing the installation and re-starting my computer per the instructions given. It doesn't fix the problem. I also tried looking in the Knowledge Database on this website, but it appears that the instructions they have to fix the problem there are for earlier versions of Word, not 2007, because my version of word does not look like the version of Word in their little videos.
This is the second time this has happened. The first time I resolved the problem by a) re-installing Acrobat, which is a pain because it involves calling Adobe and wading through their customer service to get a new installation number, and b) paying a computer repair service to dig deep into the guts of my computer and convince it to change the Office Add-ins to allow the pdf addin again. It worked for about 6 months, and now I have the same problem again. For some reason Vista is spontaneously disabling Acrobat.
I simply cannot deal with this every few months. We all know that Vista is a crappy program, but I run a business and I need a program that works with whatever crappy program Microsoft puts out. Please, can anyone give me suggestions about how to re-enable these functions when Vista disables them?
Thanks in advance!
Alycia

for Office 2007, see if this Microsoft product will work for you
http://www.microsoft.com/downloads/details.aspx?FamilyId=4D951911-3E7E-4AE6-B059-A2E79ED87 041&displaylang=en

Error this object is corrupt or is no longer available while trying to open a embedded files in word 2007 or 2013

Hi All
Word 2007 and 2013 always show this error
This object is corrupt or is no longer available while clicking a embedded files( like pdf, doc and xls). I tried reinstall office 2007, and office 2013. But still have same problems.
I surf internet, find out solution like turnning off the add-on, but not working for me, and I do not install Norton AntiVirus.
Does anyone know what the solution of this issue is, I do not have any idea right now.
Thanks in advance!!!!!

I notice there is a cross post on Answer Forum:
http://answers.microsoft.com/en-us/office/forum/office_2013_release-word/error-the-object-is-corrupt-or-is-no-longer/fde2160e-fc19-4f90-81db-4f569fac7b95
Is Dinel's suggestion helpful?
Tony Chen
TechNet Community Support

HOW TO OPEN AND SAVE FILES TO/FOR MS-WORD 2007 .docx format

MS-Office 2007 will open .docx files as well as .doc files. Apple's Pages '08 can OPEN MS Word 2007 documents with the new file format ".docx". Pages '08 can not save as ".docx" files, just ".doc" files, but since MS Office 2007 can open these ".doc" without a problem, you should be covered.
Here is how.
To open: Just double click the file and Apple's Pages '08 will import the file and open it for you to use and modify.
To save and use at your work or school's Windows MS Word 2007: When you are done and ready to save the file, go to FILE in the menu bar in Pages '08 and select EXPORT. Then pick the icon DOC WORD and click NEXT. Then in the SAVE AS box, give it a name and tell where you want to save your file to. Click EXPORT. Export is like Save, as it will now save the file where you told it to save it to. Remember you can use the same name, or give it a new name. Thats it. EASY.
It will save the file in a Windows Word format of ".doc" that MS Word 2007 can open and use.
Hope this helps people.
-Apple //GS

Why yes. How did you know that I saw the way, the truth and the light?
I just had so many people ask me how to do this, that I thought I might share it with as many people as I could and help the masses To bad that Apple just did not have it as a simple "Save As:" Maybe in the next update.
-Apple //GS

How Can I Print 2 Pages per Sheet with Bookmarks in Word 2007?

Is there any workaround to print 2 pages per sheet (in MS Word) with bookmarks?
I always get the following message:
Acrobat PDFMaker has detected that 'Multiple Pages option in Page Setup' has been selected. It will not be able to create tags, links, bookmarks with this option selected...
--Roborabbit

The Word 2007 pdf export (the one MS has here: http://www.microsoft.com/downloads/details.aspx?FamilyID=f1fc413c-6d89-4f15-991b-63b07ba5f 2e5&displaylang=en) supports bookmarks right?

Corrupted .docx file. Word 2007. Can't open the document. Tags mismatch. Help?

The Office Open XML file *.docx cannot be opened because there are problems with the contents.
Details: The name at the end tag of the element must match the element type in the start tag.
Location: Part: /word/document.xml, Line: 2, Column: 3487212
Hmm, I guess I should give some background info and what I've tried so far, right?
The document is in word 2007, Windows 7. Last night, I was in a hurry, and got a lot of things open. I was opening the document to do a few quick spontaneous revisions, but it was so laggy and I was late for an appointment, so I was feeling panicky
and frustrated. In hindsight, it probably wasn't the best option to just force shut the PC down cause word stopped responding in the middle of opening the document. Still, while I'm no Sherlock, I knew stopping it while it's in the middle of saving the document
would bebad, I didn't think stopping it while opening the document (and not really modifying the document at all, at least that was what I thought before), could have drastic consequences! The document's quite
large, a few hundred words, and about 500 or so pages. It's this really big project I was doing at work, for months now really, and because it's somewhat business confidential in nature, I can't exactly share it freely, or I would've uploaded a copy, sorry.
Anyway, I woke up this morning and opened it, and the error came up. By the way, the document was saved in a 2TB external hard with a few disk errors in the past, if that helps, even if I'm pretty much sure its not a problem with the hard. The error
came up... and yeah. I first made a copy, which I've been trying everything on, in case I do end up making things worse. I have no previous versions of it, just a relatively very old backup. Anything less than 80% recovery would set me back weeks with a wage
cut. The good news is that I was able to open the document in WordPad, managing to recover the first 287 pages (131,543 words), with no errors or data loss, and saved it in a separate file. Apparently, according to information I obtained later, MSWord tends
to not open at all when it encounters an error, but Wordpad tends to stop reading the rest of the code once it encounters an error. So, naturally, I assumed (so correct me if I'm wrong), that behind a few sentences I might lose due to the error, the rest could
also be salvageable. I then looked up the problem all over the internet. Read a microsoft article on troubleshooting/recovering corrupted documents (Open & Repair, Draft Mode, Creating Link, Recover text from any file converter, etc). No dice.
I first saw a similar question on answers.microsoft, and tried to use Tony Jollan's Rebuilder, macros enabled and all. Sadly, no luck.
I managed to make my first breakthrough when I found out that .docx was just a .zip file, and could be renamed as such, with the document.xml extracted and manually fixed using an XML editor (not that I knew how to do that, but I was desperate and
willing to learn). So, made another copy, changed extensions, and tried to specifically extract the document.xml. I believe that it is the main body text, right? That is the only thing really necessary for me, since everything I've done so far is entirely
spartan, with no fancy fonts, formatting, header/footer/notes, media objects, formulas, tables, bullet points, numbered lists, etc. All pure sans-serif text, with some Japanese Kanji thrown in. 500 pages of pure text.
I then hit a snag, when WinRAR encountered an error on extracting document.xml, stating that "CRC failed in word\document.xml. The file is corrupt". So I tried to fix this using several ZIP repair programs and stuff. Nothing worked. At
least not so far. Managed to extract an incomplete version of document.xml using WinRAR's 'Keep Broken Files' option when extracting. The extracted
document.xml came up to 3.31 MB while the original in archive is 7.53 MB. Viewed it in the Windows XML Editor which opened up the text in Internet Explorer, a jumble of text with no line breaks or paragraphs. Still, it actually extracted a few pages less than
the open-using-Wordpad method tried earlier. So trying to fix the archive again...
So I decided to give up the manual route for the meantime and focus on readymade solutions. I came across yet another microsoft article, but this one was at least more relevant than the last. It had this auto FixMe thing. I ran it, didn't
work. Apparently, as I found out later, "This fix will work for one specific tag error where there are equations and graphics in the same paragraph AND Office 2010 SP1 has not been applied."
Tried several (read: dozens) corrupt Word recovery software, from freeware to pro trials, to varying degrees of effect, although unsuccessful
in goal. Some failed to read it, saying it was too corrupted for them to handle, the best managed to recover about three-pages-worth less data compared to the Wordpad method. So yeah, anybody with a similar problem, always open it with wordpad first and recover
what you can. That doesn't mean I'm giving up though.
So here I am, tearing my hair out in frustration. Whew, I feel like I told you guys my life story. I guess worst case scenario, I report this to my boss, so I personally or from the company, I/we'll hire a team of professionals to deal with it.
But that's not an ideal scenario. It's gonna be out of my salary either way (the company has a firm policy of 'You reap what you sow'), along with a wage cut for making such an amateurish mistake even with continuous reminders to back it up every two sentences,
so I'd rather avoid that.
I'm currently looking to see whether there's a way to recover a previous version of an overwritten document somehow using a third-party software or something. (I didn't have Windows Backup enabled, so no previous version on Windows). So far, no
autosaved documents on MSWord AutoRecover, even though I have it enabled set to every 3 mins (or maybe I'm just not seeing it since I'm trying to look for it manually?). Or are the temporary files wiped on shutdown? I don't have 'Always save backup copy' option
enabled on word either.
So yeah, an auto fix, or a lengthy answer detailing what exactly I should do (from the very very basics), or a link to a site with such info, would be much appreciated. Seriously :D
Please. Thanks for at least making an effort :)

When a Word document file is corrupted, then you can try several methods to recover it:
1. First of all, you can try the recovery function integrated with Microsoft Word, as follows:
1) On the File menu, click Open.
2) In the Look in list, click the drive, folder, or Internet location that contains the file that you want to open.
3) In the folder list, locate and open the folder that contains the file.
4) Select the file that you want to recover.
5) Click the arrow next to the Open button, and then click Open and Repair.
You may find more information about this at:
http://office.microsoft.com/en-us/word-help/recover-the-text-from-a-damaged-document-HP005189610.aspx (for Word 2003)
http://support.microsoft.com/kb/893672/en-us (for Word 2007/2010/2013)
2. If you have multiple corrupt Word documents, then you can use the VBA macro provided in article
http://support.microsoft.com/kb/893672/en-us so that all the files will be opened in "Open and Repair" option automatically.
3. There are also free tools from third-parties that can open and read Microsoft Word documents, for example,
3.1 OpenOffice at http://www.openoffice.org. This is a very famous open source project that is designed to support Office file formats, including Word documents. The software can run under Windows.
3.2 LibreOffice at http://www.LibreOffice.org. Another free office suite.
3.3 AbiWord at http://www.abisource.com. This is a cross-platform tool that works under Unix and Windows.
3.4 Google Drive at https://drive.google.com/ also support to load Word document files.
Sometimes when Word fails to open your document, these tools may be able to open it successfully. If that is the case, then after the document is opened, you can just save it as a new document which will be error-free.
4. For docx files, they are actually a group of files compressed in Zip file format. Therefore, sometimes, if the corruption is only caused by the Zip file, then you can use Zip repair tools such as WinRAR at
http://www.rarlab.com to repair the file, as follows:
4.1 Assuming the corrupt document is a.docx, then you need to rename it to a.zip
4.2 Start WinRAR, go to "Tools > Repair Archive" to repair a.zip and generated a fixed file a_fixed.zip.
4.3 Rename a_fixed.zip back to a_fixed.doc
4.4 Using Word to open a_fixed.doc.
There may still be some warnings when opening the fixed file in Word, just let ignore it and Word will try to open and repair the fixed file. If the file can be opened successfully, then you can just save the contents into another error-free file.
5. If all above methods does not work, then you may try third-party tools such as DataNumen Word Repair at
http://www.datanumen.com/word-repair/
I have used it to repair some word documents successfully. It provides a free demo version so that you can try to see if the data you want can be recovered or not.
Good luck!

Error while previewing in Word 2007

I am using word 2007 and have xml publisher template builder for word version 5.6 build 45 in stalled on my system. I have installed MS .NET 2.0 patch also.
When i select for preview after loading the data, every time i hit the same error. the error does not chnage with the type of preview type chosen.
the error is
Windows cannot find 'C:\PROGRA~1\Oracle\XML'.Make sure you typed the name correctly, and then try again. To search for a file, click the start button and then click Search
Can anybody please help.

Now i have upgraded to Oracle BI Publisher Template Builder for Word 10.1.3.3.2 build 115
but still when i preview i am hitting error
Windows cannot find 'C:\DOCUME~1\user123\Local'. Make sure you typed the name correctly, and then try again. To search for a file, click the Start button, and then click Search.

Word 2007 - Save as Pdf gives error - This file is in use by another application or user

I have MS Office 2007 Small Business.
For months I have been using the "Save as PDF/XPS" option to save my word documents as PDF files.
All of a sudden, when I click on the publish button within the "save as PDF dialog", I get the error:
"This file is in use by another application or user."
- I have tried creating a new word document and I still get this error when I try to save-as pdf.
- I have tried opening a document that previously was able to be saved-as-a-pdf, and it no longer works either.
- I have tried saving from other office applications (excel, powerpoint) that also get errors now.
I have not personally installed any new software that I recall between when this worked and stopped working for me.
As far as I can tell there have been no updates explicitly for save-as-pdf in office.
Is anyone else seeing this problem all-of-a-sudden?
Thanks.
jlk

I just encountered this problem while trying to save a pdf from Excel 2007. I had recently updated to Adobe Reader 9.1.
I received the same error message you're reporting here when I went to Word 2007 and tried to save a pdf file from it as well.
I uninstalled Adobe Reader 9.1.
Reinstalled the Office 2007 pdf plug-in
Successfully created pdf files from word and from Excel (which is what I needed to do in the first place).
I then reinstalled Adobe Reader 9.1 so I could read the PDF files I had just created in Excel and word.
I then tried to create pdf files from word and excel. Error messages are back and I'm unable to create pdf's from word or excel.
So.. why does Office 2007 pdf plugin not work when Adobe Reader 9.1 is installed?
Frankly I'm getting tired of uninstalling Adobe Reader 9.1 every time I need to create a pdf file in Word or Excel.
Bry

HP Laserjet 1018, Word 2007 on Windows XP - Duplex printing alignment

HP Laserjet 1018, Word 2007 on Windows XP
Want to Print a book on both sides of A4 paper. I am printing one page per
page (not the book mode).
If I print single sided, the top of the page (e.g. header text) on odd and
even pages are aligned. When I print duplex mode, odd pages print fine but
the even pages are shifted down. Thus the header text are not aligned.
I think this is more a problem with the way the printer is managing duplex
printing.While printing in duplex mode, the printer first prints in reverse (with bottom of
the page as ref) to enable placement of the output sheets back into the input
tray without rotation. Is this messing up the alignment?
- Jayawanth

Hi there,
Try downloading and running the print and scan doctor located here:
http://h10025.www1.hp.com/ewfrf/wc/document?docname=c03275041&cc=us&dlc=en&lc=en
It can fix a lot on its own and if not give a better idea of what is going on.
Best of Luck!
You can say thanks by clicking the Kudos Star in my post. If my post resolves your problem, please mark it as Accepted Solution so others can benefit too.

Duplex Printing Problem - Word 2007, Vista and HP Officejet Pro L7780

I'm having trouble with duplex printing on my new HP Officejet Pro L7780, from Word 2007, running on a brand new Vista system. I've also had this same problem (repeatable) with two other computers, running XP Professional/Word 2003, XP Home/Word 2003. All of the service packs have been installed for the operating system, word, and printer.
If you print a landscape document, using the auto duplex setting for the HP printer, the margins will print out offset by .25 inches, on the left and rigt margins. So if your margin is 1 inches on right and left, the margins will print to .75 on one side and 1.25 on the other. This would be annoying, except that I'm trying to print brochures and books, which requires that the pages print out exactly as set up... "close enough" isn't working for me
The way I have replicated this problem is as follows: set up a document in landscape format, using the default margins. Insert an image on page one, size it so it takes the full margin area. On the second page, fill it up with text. Print the document, selecting the printer properties and setting Print on Both Sides=Automatic. The easiest way see the problem is by holding the document up to the light. The front and back margins should match and they don't.
Any help you can provide would be very much appreciated.
Diana

Diana,
This problem is perhaps much larger than you might have imagined. We have tried to work with Hewlett Packard for over two years on the duplex printing problems. In the process, we have expended over 100 hours of effort in troubleshooting the problem which has included updating software, reinstalling software, developing test documents, escalating issues, submitting technical findings, and in purchasing replacements. Unfortunately, our efforts to interact with Hewlett Packard excalated support have resulted in an aire of apathy, disinterest, incompetence, frustration, redundancy, occasional discourtesy, and an outright lack of professional decorum - something inconceivable of a large, reputable company.
We have identified several problems with duplex printing. The duplex printing problems include irregular margin increases (.25 to .50 inch), margin shifts, cut-off text, compressed text, and compressed graphics. Please note that most of these problems are only evident when printing documents from computer applications to the printer. If the user simply uses the front printer panel to copy in duplex mode, these problems are not always evident. This suggests that the printer mechanics are capable of properly duplexing and that the problem lies in the drivers.
The problem is evident on the HP OfficeJet Pro L7780, Photosmart L7180, Photosmart C6150, Photosmart 3310, and likely on many, many other HP models. The problem is evident on many computers (HP, IBM, Toshiba, and Dell), is evident in multiple applicatons (Word, Wordperfect, Excel, Peachtree, Notepad, and many more), and is evident on multiple operating systems (Windows XP Home, Windows XP Professional, Windows XP Media Center Edition, and Microsoft Vista).
We consider ourselves to be extremely polite, patient individuals, but have nearly been driven to outrage by the indignant disregard offered us by HP's escalation support department; a department which should represent the cream-of-the-crop in both service and technical expertise. Given the ease with which the problem can be duplicated, we expected an extremely quick resolution by HP who, to our knowledge, has never even made the effort to duplicate the problem in-house on our behalf.
Ironically, HP highly advertises their J.D. Powers rated technical support, yet it appears that they actually have extremely poor published consumer rankings in some of today's mainstream computer magazines. HP technical support makes no apologies for the fact the user cannot use a major feature of their printers, offers no indication that the problem is even being addressed, and off-loads the responsibility by suggesting that we contact Microsoft (who is to blame for this issue).
Thank you, Diane, for your message. We had a hard time imagining that we were the only one experiencing this problem, especially when HP promotes such a representation. Which also begs the question why HP plays like the problem does not even exist? I also fail to understand why HP technical support shows so little interest in a problem that is easily duplicated and adversely affects a major feature of the printer which is commonly used by individuals purchasing equipment for its duplex capabilities.
This is sad because we have been a loyal customer of HP for over twenty-five years. There was a time when we would have happily endorsed HP's steller products and steller support (provided you could get a problem escalated). Now, however, they all-too-often appear to offer equipment that fails to support advertised features which is backed up by sub-standard support and extremely expensive ink. This is an especially sad commentary for users who are buying HP's upper-end printers and computers.
We desire to know if there are others out there experiencing similar problems? If you have experienced these problems or would like samples of the problems we have duplicated, please respond. I think the more information we gather, the better our chance of a successful resolution to a serious problem.
Thanks Everyone!

Word 2007 (docx) integration in SAP CRM 7.0 EhP1

Hi,
When creating word templates with the template designer (CRM_OI_TEMPLDSG) for office integration, is it possible to use Mircosoft Word 2007 docx-files?
Furthermore you get the message, that "The file contains custom XML elements which are no longer supported by Word. If you save this file, these custom XML elements will be removed permanently." ([KB2445062|http://support.microsoft.com/kb/2445062]) when you create a template in fileformat .doc with Word 2007. When you open this template again all xml elements are no longer available (as mentioned in the message) and you have to create the template again.
How do you handle this situation? Or do you not even have this problem?
Thanks in advance,
Sebastian

May be this thread Document Template designer - ActiveX on IE 7 problem and the [Note 1566793 'Procedure to create word template in EHP1 & higher versions'|https://service.sap.com/sap/support/notes/1566793] will give you some inputs.

Inability to use eps graphics in Word 2007 and make a pdf

Hi there …
I work at a small "intellectual capital" company where virtually all of our documents (our products!) depend on embedding eps "pictures" into Word and pdf'ing the result. While this process works great in Word 2003, it fails miserably in Word 2007 - the "mechanics" work fine and a pdf is produced, but the rendering of the eps images are terrible. I spent some effort looking into this issue trying to find a solution and came up with the following (thanks in part to this post) ... if anyone has any more details, corrections, or solutions feel free to post!
It appears that, over the years, there have been three flavors of eps import filters for Word ... (for the curious the filter is found in Program Files\Common Files\Microsoft Shared\Grphflt\EPSIMP32.FLT )
The simplest (and oldest) filter basically embeds the eps code unmodified into the Word doc and will display a raster preview of the image if one is included in the eps file. if the file is printed on a postscript printer or to Acrobat, the eps code is passed through (so it produces perfect pdfs, and the screen image in Word looks as good as the preview image embedded in the eps file). if the file is printed to a generic printer, no image appears (so it doesn't work for joe user).
The Word 2003-era filter pastes the eps code unmodified into the Word doc, then renders a (very poor) preview image (using an OEM'd eps converter). if a preview image is in the eps file it is ignored (which is bad). if the file is printed on a postscript printer or to Acrobat, the unmodified eps code is passed through (so it produces perfect pdfs, though the screen image in Word looks yucky). if the file is printed to a generic printer, the poorly rendered preview image is printed (so it works poorly but better than nothing for joe user - and probably gives joe user a bad impression of eps).
In what might be an attempt to improve things for joe user, the Word 2007 filter immediately interprets the eps code (using a slightly updated eps converter from the same OEM) and pastes the resulting rendered image into Word. It NO LONGER embeds the unmodified eps code in the Word doc. While the rendered image looks better than filter #2, it still leaves A LOT to be desired - in my brief testing, colors are VERY wrong and curves become choppy. if the file is printed on a postscript printer or to Acrobat, the poorly rendered image is used since the original eps code is gone (unacceptable for my purposes). if the file is printed to a generic printer, the poorly rendered image is printed (so it works better than Word 2003 for joe user).
So where does this leave anyone that wants to upgrade to Word 2007, use eps images, and make quality pdfs ??
Filters #1 & #2 were interchangeable in Word 2003. The true eps experts like #1 the best, and it is by far the simplest technically (76k of code vs 400+k), so they merrily swapped and used it with Word 2003. (Very) unfortunately filters #1 and #2 do not work with Word 2007 - if they did the problem would be nicely solved.
Find another graphics file format to work with? This is undesirable because the "beauty" of #1 & #2 above is the unmodified eps code gets fed to the pdf maker (which itself is native eps) - Word is just a transport (no "transcoding" loss in compression-speak). if there were an efficient way to convert eps to say wmf (microsoft's proprietary vector graphic format), and the images were able to survive two transcodes (from eps to wmf back to eps for pdf), it might be livable. But of course Adobe Illustrator cannot save as wmv (nor should it IMHO). Of note - there is another industry standard vector format - svg - which AI can save as but Word does not support.
Stay in Word 2003 doc format while using Word 2007 (don't use docx). Doesn't work. My testing shows a Word 2003 doc file with embedded eps created in Word 2003 (and pdf's correctly in Word 2003) does not pdf correctly in Word 2007.
Use a work-around. As suggested here, "Open the EPS in Illustrator. Select all, and Edit > Copy. In Word, Edit > Paste Special > Enhanced Metafile." This seems to work for small images such as logos, but not for larger graphical stuff (probably because of the internal transcoding to WMF).
Stay with Word 2003. This appears to be the only workable option for now IF you want to use Word and render eps pictures in pdf's with acceptable quality.
IMHO the best solution would be to have the very simple 76k filter #1 ported to Word 2007 (those who need the capability can swap the filter files) or (not as optimal but does not require swapping filter files) add the option in filter #3 to still embed the eps code. Microsoft is the right place to do it, or (politics aside), Adobe could and should do it (given some support from MSFT).
I am surprised this issue has not caused more rumblings from users - perhaps it has, the symptoms are just worded differently. Or maybe everyone is just staying with Word 2003 (which is what I have done until now). The problem is most companies are being forced to upgrade now, so I think this will become a bigger issue for Adobe / Microsoft going forward.
Thanks for listening. I look forward to your comments.
Andy

Microsoft has released a hot fix that supposedly addresses this issue, it is at
http://support.microsoft.com/kb/977468
I downloaded the fix and tried it; it actually made the problem worse! Apparently they
are trying to fix their filter rather than bypassing it. What I am doing is
1. Making maps in AutoCaD Map and printing (plotting in autocad) them to a pdf file
2. Opening the pdf file in Acrobat and resaving it as eps
3. Importing the eps file into a Word 2007 document
4. Use Acrobat to convert the Word document to pdf
Before the hot fix when I did the process the resolution of the map in the final
pdf file was not as good as in the original made from AutoCad. Also the colors were
not correct. After installing the hotfix there are still these same problems but also now
any non horizontal text is not displaying correctly.
Be careful about trying this hotfix.
As others have noted, back in Word 2003 the above steps 1 - 4 worked very well and resulted
in a high quality pdf file with the map as good as in the original pdf.

Slow word 2007

Similar Messages

Maybe you are looking for