Word XP to PDF 6

J

Jane

I am trying to convert a Microsoft Word file to PDF using
the "Convert to PDF button".

I get an error message that says:

"The following error occurred while Printing: File not
found: pdfmword.dll". I have that file in the Adobe
folder. How can I make Word recognize the file?

I ran Help > Detect and Repair in Acrobat 6 Professional.

I have Acrobat 6.0.1 Professional, Windows, with a
PostScript printer (Xerox Phaser 4400).

Thanks,
Jane
 
S

Subramanian S [MSFT]

Hi Jane,
Can you try this? Copy the following files into the msoffice folder
office10/startup pdfmaker.dot pdfmakerA.dot pdfmword.dll
all from acrobat folder 'C:\prog files\adobe\acrobat5\pdfmaker and
pdfmaker\office2000'

Please let me know if this solves your problem.

Regards,
Subbu.

Subramanian .S
This posting is provided "AS
IS" with no warranties, and confers no rights.
 
J

Jane

I tried your suggestion and got the same message.

Then I tried restarting my computer and Word crashes each
and everytime I try to launch it.

So now things are worse--much worse.
 
S

Subramanian S [MSFT]

Hey Jane,

If Word crashes as soon as it opens ...
a) It is most likely to be due to template corruption. To verify whether
this is the case, start Word without templates and add-ins loaded, to see
whether it still crashes: to do this, click the Start button in the bottom
left of your screen, select Run, and type winword.exe /a. (You may need to
specify the full path although you probably won't.)

Note the space before the forward slash! If you miss out that space, you'll
get an error message such as: 'Cannot find the file ‘winword.exe/a’ or one
of its components'.

The /a switch is intended as a troubleshooting tool only, and you shouldn't
continue to use it to start Word. Any customisations you make while in this
mode will be discarded.

If that fixes it, either your Normal.dot template or one of the files in
Word's Startup path are probably corrupt, so the next steps to try are:

i) Try renaming your Normal.dot file (with Word closed and if Outlook is
your email editor, close Outlook as well, and if you have opened a Word
document within Internet Explorer, close IE too).

For instance, try renaming Normal.dot to Normal.old and make sure you only
have one Normal.dot file.

ii) If that doesn't fix it, try either moving any files that are in Word's
Startup2 path to another folder, or renaming any files in Word's Startup2
path from [filename].dot to [filename].old.

If in doubt, move the files instead of renaming them.


Let me know the result.

Regards,
Subbu.

Subramanian .S

This posting is provided "AS IS" with no warranties, and confers no rights.
 
J

Jane

Word began crashing immediately after I copied the 3 files
that you mentioned (pdfmaker.dot pdfmakerA.dot
pdfmword.dll) into the Startup folder. It crashed
everytime, without fail, once I made that change.

I just noticed that you specified copying them from the
Acrobat 5 folder. I have Acrobat 6.

I deleted those 3 files from Word's Startup folder,
renamed my normal.dot, and deleted the "data" key from my
registry. Word is now functioning and I will have to redo
my customization.

Now I'm left with my original problem. I can't use the PDF
Maker button to create a PDF in Word XP.

Jane
 
S

Subramanian S [MSFT]

Hi,

Please try the following:

(http://www.adobe.com/support/techdocs/31e8e.htm)

Troubleshooting Acrobat PDFMaker

If you can create a PDF file with the Adobe PDF printer or Acrobat
Distiller, but not with Acrobat PDFMaker, the problem may be with an
Acrobat PDFMaker feature. To determine if any of these features causes the
problem, disable them, and then try to create a PDF file:

1. In Word, choose Adobe PDF > Change Conversion Settings.
2. Choose Smallest File Size from the Conversion Settings pop-up menu.
3. Click the Word tab, and then deselect all options.
4. Click the Bookmarks tab, and then deselect all Bookmark options.
5. Click the Security tab, and then deselect all Security options.
6. Click OK.
7. Try to create a PDF file:
-- If you can't create a PDF file, proceed to the next section,
"Troubleshooting document-specific issues."
-- If you can create a PDF file, determine which features cause the
problem: Enable one feature, and try to create a PDF file. Repeat this
process until the problem recurs. Then, create a new Word document that
contains only a few words, and try to create a PDF file from that document
using the same Acrobat PDFMaker settings:
- If you can create a PDF file from the new document, the problem is
document-specific. Proceed to the next section, "Troubleshooting
document-specific issues."
- If you can't create a PDF file from the new document, then the feature
most recently enabled will continue to cause problems. Reinstall Acrobat
PDFMaker. If the problem persists, contact Acrobat Technical Support.


Troubleshooting document-specific issues

If you determine that the problem is document-specific, troubleshoot as
follows:

-- Enable only the Acrobat PDFMaker features the document uses. For
example, if the document contains only the heading styles Heading 1 and
Heading 2, disable the other heading styles in the Acrobat PDFMaker dialog
box.
-- Switch to the Normal document view in Word, and then create the PDF file
using Acrobat PDFMaker.
-- Re-create the Word document to eliminate any damage in it by doing one
or more of the following:
- Copy and paste the content of the Word document into a new document, then
create the PDF file.
- Select all of the text in the document, change its font, and then save
the document with a new name. Word rewrites the document, which may
eliminate whatever element is conflicting with Acrobat PDFMaker. After you
save the document, you can reformat it in the desired font.
- If the document was created in a version of Word other than the version
you use to create the PDF file, make a small change to the document, and
then save it with a new name. This procedure forces Word to rewrite the
document, possibly eliminating any element that conflict with Acrobat
PDFMaker.
-- Re-create any custom heading styles in the document, and then create the
PDF file.
-- Identify conflicting elements in the document:
1. Create a new Word document.
2. Copy half of the original Word document into the new Word document.
3. Convert the new Word document to PDF using Acrobat PDFMaker:
- If the problem recurs, a conflicting element exists in the new Word
document. To further isolate the conflicting element, repeat steps 1-3, and
copy half of the second Word document into another new Word document.
- If the problem does not occur, a conflicting element exists in the
original Word document. To further isolate the problem, repeat steps 1-3,
and copy the other half of the original Word document into another new Word
document. If both halves of the document convert correctly, close other
programs that are running, including the Office application, and delete
*.tmp files (usually located in the Windows/Temp folder).
-- Remove both Acrobat and Office or the specific Office application (Word,
PowerPoint, or Excel), then reinstall Office or the specific Office
application, and then reinstall Acrobat. To remove Acrobat, use the
Add/Remove Programs Control Panel. For instructions to remove Office, see
the Office documentation or contact Microsoft.
-- If the Word document is protected, remove the protection. For
instructions to remove the protection, see the Word documentation or
contact Microsoft.


Troubleshooting conflicts with other macros in Microsoft Word

PDFMaker can conflict with other macros, such as virus checkers or fax
software. If other troubleshooting tasks fail, or if PDFMaker has problems
after installing a third-party macro, troubleshoot conflicts with other
macros. Macros known to cause incompatibilities include Duden Korrektor
Plus 2.0, ViaVoice 10 and earlier, Personal Translator 2002 Office Plus,
OfficeReady Stuffit, Leuchter Informatic AG WordPlus, and GoldMine Link to
Word.


To determine if PDFMaker is conflicting with another macro, delete or
deactivate other macros one at a time, and then try again to convert a
document to a PDF file using PDFMaker. If the problem does not recur,
contact the manufacturer of that macro.


Regards,
Subbu.

Subramanian .S

This posting is provided "AS IS" with no warranties, and confers no rights.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top