Problems Converting Word docs to PDF

Can you try printing to Adobe PDF printer directly and see if that works.

Check Acrobat compatibility with Microsoft Office

Before you begin troubleshooting, be sure that the version of Acrobat you are running is compatible with the version of Office you are running. Acrobat 7.0 Professional and Standard are compatible with Office 2003, 2002, and 2000. Acrobat 8.0 Professional and Standard are compatible with Office 2003, 2002, and 2000.

Troubleshoot Acrobat Distiller and the Adobe PDF printer

Because Acrobat PDFMaker uses the Adobe PDF printer, which in turn uses the Acrobat Distiller application to convert Word documents, the first step in troubleshooting is to determine if Acrobat Distiller is working correctly:

1. Try to create a PDF file from Word with the Adobe PDF printer: Open a document in Word, choose File > Print, choose Adobe PDF from the Printer Name menu, and then click OK.-- If you can create a PDF file with the Adobe PDF printer, but not with Acrobat PDFMaker, the problem may be with a feature of Acrobat PDFMaker. Proceed to the next section, "Troubleshoot Acrobat PDFMaker."

-- If you can't create a PDF file with the Adobe PDF printer, proceed to step 2.

2. Try to create a PDF file with the Acrobat Distiller application:

Note : This method doesn't support advanced PDFMaker features, such as maintaining links and document structure.

a. Open a Word document, and then choose File > Print.b. In the Print dialog box, select a PostScript printer (for example, the Adobe PDF printer), select Print to File, and then click OK. A PostScript (.ps or .prn) file is created.

Note: If you don't have a PostScript printer, you can download a PostScript printer driver from the Adobe website at www.adobe.com/support/downloads. After you install the driver, complete steps 2a-2b. If you select the Adobe PDF printer, deselect "Do Not Send Fonts To 'Adobe PDF'" to create a PostScript file.

c. Choose Advanced > Print Production > Acrobat Distiller (Acrobat 8) or Advanced > Acrobat Distiller (Acrobat 7).d. Choose a setting from the Default Settings list (or leave at the default).

e. Choose File > Open, choose All Files in the Files Of Type menu, select the PS or PRN file you created, and then click Open.f. Specify a name and location for the PDF file, and then click Save.

-- If Acrobat Distiller creates a PDF file, proceed to the next section, "Troubleshoot Acrobat PDFMaker."

-- If Acrobat Distiller doesn't create a PDF file, proceed to step 3.

3. Open the messages.log file in the following folder:

-- Windows NT: WINNT/Profiles/ [user profile] /Application Data/Adobe/Acrobat/Distiller [version number]

-- Windows 2000 and XP: Documents and Settings/ [user profile] /Application Data/Adobe/Acrobat/Distiller [version number]

4. Check the messages.log file for troubleshooting information:

-- If the file indicates why Acrobat Distiller couldn't create the PDF file, search the Support Knowledgebase at www.adobe.com/support/products/acrobat.php for related documents. For example, if the file lists a PostScript error, troubleshoot the error according to the recommendations in document 328515, "Troubleshoot PostScript Errors."

-- If the file doesn't indicate why Acrobat Distiller couldn't create the PDF file, create a new Word document that contains only a few words, and then try to create a PDF file from that document using the Adobe PDF printer and the Acrobat Distiller application:

- If you can create a PDF file from the new document, the problem may be related to PDFMaker. Proceed to the next section, "Troubleshoot Acrobat PDFMaker."

- If you can't create a PDF file from the new document, use a file from another application, and try to create a PDF file with Acrobat Distiller. If the problem happens with the file from another application, reinstall Acrobat Distiller. If the problem doesn't happen with the file from another application, troubleshoot the specific behavior using the documents listed in Related Documents, below, or search the Support Knowledgebase at www.adobe.com/support/products/acrobat.php. If you need further assistance, contact Acrobat Technical Support.

Troubleshoot 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 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, "Troubleshoot 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, "Troubleshoot 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.

Troubleshoot 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, and 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 elements 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 on how to remove Office, see the Office documentation or contact Microsoft.

If the Word document is protected, remove the protection. For instructions on how to remove the protection, see the Word documentation or contact Microsoft.

Troubleshoot 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.

Troubleshoot problems in Microsoft Word


The steps below are based on the Microsoft Knowledge Base article 825840, "How to Troubleshoot Problems When You Start or Work in Microsoft Office Word 2003." For more detailed information on troubleshooting Microsoft Word, visit the Microsoft website at www.microsoft.com and search for this article.

Important: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, see the following article in the Microsoft Knowledge Base: 256986 "Description of the Microsoft Windows Registry."

1. Start Word using the /a switch and add PDFMaker manually.


When you start Microsoft Word by using the /a switch, Word temporarily uses the default built-in settings for all options and prevents the loading of add-ins, preferences, customizations, and macros. This is referred to as Office Safe Mode. All Microsoft Office 2003 programs have a Safe Mode startup option.

For additional information about Office Safe Mode, visit the Microsoft Knowledge Base and search for article 291013: "WD2002: About Office Safe Mode in Word."

Note: If you make changes to preferences, customizations, or macros during an /a switch session of Word, the changes you make are lost when you quit Word.

Exit all programs before you proceed with these steps.

To start Word by using the /a switch:

1. Choose Start > Run.2. In the Run dialog box, type: winword.exe /a .

3. Click OK. The Run dialog box closes, and Word starts.

To load PDFMaker manually:

1. Select Tools > Customize, and click the Commands tab.2. Click Tools in the Categories panel.

3. Drag COM Add-ins from the Commands panel to the Tools menu while holding down the mouse button. When the Tools menu displays the menu commands, drag COM Add-ins just below the Customize option, and then release the mouse button.

4. Click Close.

5. Click COM Add-ins on the Tools menu.

6. Click Add, locate the add-in (the PDFMaker Add-in is located at [Acrobat Installation Path] \PDFMaker\Office\PDFMOfficeAddIn.dll), and click OK.

7. Press Alt+F11 to start the Visual Basic Editor.

8. Press Ctrl+G to start the Immediate Window of Visual Basic Editor.

9. To start PDFMaker in Word, type Application.COMAddIns("PDFMaker.OfficeAddin").Connect = True .Close the Visual Basic Editor.

10. Verify that the Adobe PDF and Acrobat Comments menus now appear to the right of Help on the Microsoft Word menu bar.

To create a test Word document and start PDFMaker:

1. Type some text in the Word document.

2. Choose File > Save, and save the test document to the desktop.3. Click Convert To Adobe PDF.

If you resolve the issue when you use the /a switch to start Word, remove each of the components that load during Word startup. Remove these components one at a time in the order that they appear in Word. The following components load during Word startup: Word auto macros, global template (Normal.dot), Add-ins (WLLs) and Templates in the Word Startup folder and the Office Startup Folders, COM add-ins, Word Data key in the Windows registry, Word Options key in the Windows registry, and Word Auto Macros.

Note: Microsoft Product Support Services has a Troubleshoot Utility (included in the Support.dot file) that automates the removal and restoration of the components that Word Startup loads.

For additional information about Support.dot, visit the Microsoft Knowledge Base and search for article 289506 "HOW TO: Install and Use the Support.dot Template in Microsoft Word 2002."

2. Rename Normal.dot template file.


To prevent the formatting, autotext, and macros that are stored in the global template (Normal.dot) from affecting the behavior of Microsoft Word and documents that you open, rename your global template (Normal.dot). When you do so, you can quickly determine whether the global template is causing the issue.

Important: When you rename the Normal.dot template, you reset several options to the default settings, including custom styles, custom toolbars, macros, and AutoText entries. Therefore, Microsoft strongly recommends that you do not delete your Normal.dot file.

Certain configurations may create more than one Normal.dot file. For example, this issue may occur if a computer runs more than one version of Word or if several workstation installations exist on the same computer.

To rename the Normal.dot file:

Note: Do not use the /a switch to restart Word after you complete these steps.

On Microsoft Windows 2000:

1. Quit all instances of Word, including Outlook if Word is your e-mail editor.

2. Select Start > Search > For Files Or Folders.3. In the Search For Files Or Folders Named box, type: Normal.dot .

4. In the Look In box, select your local hard disk.

5. Click Search Now to search for the file.

6. For each occurrence of the Normal.dot file that appears in the Search Results dialog box, do the following:

-- Right-click the file, and select Rename.

-- Give the file a new name (for example, OldNormal.dot or Normal-1.dot), and then press Enter.

7. On the File menu, click Close to quit the Search, and then restart Word.

On Microsoft Windows XP:

1. Quit all instances of Word, including Outlook if Word is your e-mail editor.

2. Select Start > Search.3. Under What Do You Want To Search For, select All Files And Folders.

4. In the All Or Part Of The File Name box, type: Normal.dot .

5. In the Look In box, choose your local hard disk (or an alternative user template location if you are running Word from a network server).

6. Click Search.

7. For each occurrence of the Normal.dot file that appears in the Search Results dialog box, do the following:

-- Right-click the file, and select Rename.

-- Give the file a new name (for example, OldNormal.dot or Normal-1.dot), and then press Enter.

8. On the File menu, click Close, and then restart Word.

If you resolve the issue when you rename your global template, the issue is a damaged Normal.dot template. You may have to change several settings to restore your options. If the Normal.dot file that you renamed contains customizations, such as styles, macros, or AutoText entries that cannot be easily re-created, you may be able use the Organizer to copy those customizations from the old Normal.dot file to the new Normal.dot file.

For more information about how to use the Organizer, follow these steps:

1. Start Word.

2. Choose Help > Microsoft Word Help.3. In the Office Assistant or the Answer Wizard, type Organizer.

4. Click Search to view the topics returned.

If you do not resolve the issue, then you may want to use your old global template (Normal.dot) instead of the new global template. To use your old Normal.dot template, rename the new Normal.dot template back to Normal.dot. If you continue to experience issues with PDFMaker after working with this document, then contact Adobe Technical Support.


Additional Information
328515 : Troubleshoot PostScript Errors

330984 : PDFMaker is unavailable in a Microsoft Office application (Acrobat 7.0 on Windows)

328399 : Remove and reinstall PDFMaker 6.0 in Office 2000 or XP

317147 : Troubleshoot problems with Acrobat PDFMaker (6.0-7.0 on Windows)

333504 : Acrobat PDF-capable web browsers and PDFMaker-compatible applications (Acrobat 8.x on Windows and Mac OS)


Sources
Copy these steps into your case notes and note the result of each.

Please indicate if you assisted the customer with each step, or if they performed the step by themselves (for example: "Helped CU" or "CU off phone").

Where appropriate, list your results; yes/no answers might not provide enough data.

Check Acrobat compatibility with Microsoft Office
1. Is Acrobat compatible with Office?

Troubleshoot Acrobat Distiller and the Adobe PDF printer
2. Can you print to Adobe PDF?
3. Can you create a PS file from Adobe PDF?
4. Can you create a PDF from the PS file?
5. Was a log file generated when attempting to convert to PDF?
6. Can you print to the Adobe PDF printer using a New Document?

Troubleshoot Acrobat PDFMaker
1. Turn off all features in PDFMaker and attempt to convert again.
2. Reinstall PDFMaker if you are still unable to convert.

Troubleshoot document-specific issues
1. Disable extra heading styles in PDFMaker.
2. Use Normal view to convert document.
3. Copy and paste the contents into a new Word document.
4. Change the font in the entire document.
6. Save the document with a new name.
7. Re-create customer style headings.
8. Identify conflicting elements in the document.
9. Remove Acorbat and Office and reinstall.
10. Unprotect document if protected.

Troubleshoot conflicts with other macros in Microsoft Word
1. Could you identify any conflicting macros in Word?
2. What other macro were loaded?

Troubleshoot problems in Microsoft Word
1. Start Word using the /a switch and add PDFMaker manually.
2. Rename Normal.dot template file.


Original VersionsAcrobat Professional 8.0

Original AuthorsAlister Black

CategoryTroubleshooting

TechNote DetailsLast Update: 09-28-2007
ID: 329852
OS: Windows

Permanent Link: http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=329852

Just restarted after the install (which i wasn't prompted to do!) and everything seems to be running fine now.

Thanks for taking the time guys :)