Troubleshoot Acrobat PDFMaker issues in Microsoft Office on Windows

Adobe Acrobat PDFMaker (the Convert To Adobe PDF button in the PDFMaker toolbar/tab) is an add-in that creates PDF files from Microsoft Office applications. This feature installs with Acrobat Professional and Standard.

• In MS Office 2003 and earlier, PDFMaker uses Adobe PDF Printer to a create a PostScript file. Then, Adobe PDF printer interfaces with the Adobe Acrobat Distiller application to create a PDF file.
• In MS Office 2007, 2010, 2016, and 365, PDFMaker uses the AdobePDF Library to convert a Microsoft Office document to PDF.
• Acrobat Distiller or Adobe PDF Printer can also be used independently to create PDF files.

This document can help you troubleshoot problems that occur when you try to create PDF files from Office applications using Acrobat PDFMaker. Although this document is specific to Microsoft Word, most of the troubleshooting procedures also apply to Microsoft PowerPoint and Microsoft Excel.

Try the following steps to fix the problem:  

Acrobat PDFMaker is crashing with Office 2016 and Office 365 on Windows after Office 2016's February update.

Adobe is investigating the problem and working with Microsoft to get it resolved as soon as possible. Meanwhile, to create PDFs, see the workaround here.

Before you begin troubleshooting, be sure that the version of Acrobat you are running is compatible with the version of Office you are running. For details, see Compatible web browsers and PDFMaker applications | Acrobat, Reader.

Acrobat PDFMaker (for MS Office 2003 and earlier) uses the Adobe PDF printer, which in turn uses the Acrobat Distiller application, to convert Word documents. Therefore, the first step in troubleshooting is to determine if Acrobat Distiller is working correctly:

• If you can create a PDF file with the Adobe PDF printer, but not with Acrobat PDFMaker, the problem could be with Acrobat PDFMaker. Proceed to Troubleshoot Acrobat PDFMaker.
• If you can't create a PDF file with the Adobe PDF printer, proceed to Try to create a PDF with the Acrobat Distiller application.

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

If you can create a PDF file with the Adobe PDF printer or Acrobat Distiller, but not with Acrobat PDFMaker, the problem could be with an Acrobat PDFMaker feature. To determine if any of these features is the cause of your problem, disable them. Then, try to create a PDF file:

• If you can't create a PDF file, proceed to 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 Word document that contains only a few words. 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 Troubleshoot document-specific issues.
• If you can't create a PDF file from the new document, then the feature most recently enabled continues to cause problems. Reinstall Acrobat PDFMaker. If the problem persists, contact Acrobat Support. 

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

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.

Do 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 the text in the document, change its font, and then save the document with a new name. Word rewrites the document, which can eliminate elements that conflict 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 one you use to create the PDF file, make a small change to the document. Then save it with a new name. This procedure forces Word to rewrite the document, possibly eliminating any elements that conflict with 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. Delete .tmp files (often located in the Windows/Temp folder).

Remove both Acrobat and Office or the specific Office application (Word, PowerPoint, or Excel). 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.

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

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 (refer applicable link below). Then try again to convert a document to a PDF using PDFMaker. If the problem does not recur, contact the manufacturer of that macro.

• MS Office 2007 
• MS Office 2010

The steps below are based on the Microsoft knowledgebase articles:

• How to use startup command line switches to start Word 2010, Word 2007, Word 2003, Word 2002, and Word 2000
• How to troubleshoot problems that occur when you start or use Word 2010, Word 2007, Word 2003, or Word 2002

For more detailed information on troubleshooting Microsoft Word, visit the Microsoft website and search for a relevant article.

The /a switch starts Word and prevents add-ins and global templates (including the Normal template) from being loaded automatically. The /a switch also locks the setting files; that is, the setting files cannot be read or modified if you use this switch.

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

To start Word by using the /a switch:

To load PDFMaker manually (Acrobat 6.x only):

To load PDFMaker manually (MS Word 2003 or earlier):

Load PDFMaker manually (MS Word 2007 and 2010):

Create a test Word document and start PDFMaker: 

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)
• 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
• Word Auto Macros

Note: Refer the following Microsoft Product Support Services for additional Word startup troubleshooting:

• Microsoft knowledgebase
• How to reset user options and registry settings in Word
• How to troubleshoot problems that occur when you start or use Word

For instructions on how to rename the global template file, see the section "Global Template (Normal.dotm or Normal.dot)" in the Microsoft Support article, How to reset user options and registry settings in Word. Scroll down the page to get to the article.

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

If you resolve the issue when you rename the global template, then the issue is a damaged Normal.dot template. It's sometimes necessary to change several settings to restore your options. If the Normal.dot file you renamed contains customizations, such as styles, macros, or AutoText entries that cannot be easily re-created, try using 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:

If you do not resolve the issue, consider using 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, contact Acrobat Support.