When you try to print, InDesign returns the following error:
"Printing Error: The Adobe Print Engine has failed to output your data due to an unknown problem."
- Rename the InDesign SavedData file and the InDesign Defaults file (for example, to InDesign SavedData.old, InDesign Defaults.old) in the following location:
- Windows XP: C:/Documents and Settings/[user name]/Application Data/Adobe/InDesign/[Version]
- Windows 7/Vista: C:/Users/[user name]/AppData/Roaming/Adobe/InDesign/[Version]
- Mac OS: /Users/[user name]/Library/Preferences/Adobe InDesign/[Version]
If you print an EPS file exported from an InDesign document with a gradient, make sure that spot colors in the gradient are from the same color space, and then re-export the EPS. (For example, make sure that the gradient doesn't contain one RGB spot color and one LAB spot color.)
Change the settings in the Print dialog box as follows:
- If you print a section that contains only one odd page, deselect Even Pages Only.
- If you print a section that contains only one even page, deselect Odd Pages Only.
If you print an InDesign document that contains imported tagged text, check to see if the tagged text file contains an out-of-range color. Out-of-range colors appear in the Swatches palette with an appended value, such as "+5," that indicates the nearest in-range value.
To replace an out-of-range color with an in-range color, do the following:
- Define a new color swatch in InDesign and then use the Find/Change feature to replace the color in the tagged text file with the new color.
- Redefine the color value in the tagged text file and then reimport the file into InDesign. The color values are defined with a color table tag (<Color Table>). For more information about Tagged Text color definitions and tags, see the Tagged Text PDF file on the InDesign CD-ROM.
Export the file to PDF and then print the PDF file from Adobe Acrobat 5 or later or Adobe Acrobat Reader 5.0 or later.
Remove OPI 2.0 comments from the PDF file, place the PDF file into InDesign, and then print the document.
To remove OPI 2.0 comments, do one of the following tasks:
- In Adobe Acrobat, manually remove the OPI 2.0 comments and then re-create the PDF file.
- In Acrobat, use Enfocus Pitstop to remove the OPI 2.0 comments.
- Use OPI 1.3 comments.
- In Acrobat Distiller, choose Settings > Edit Adobe PDF Settings, click the Advanced tab, deselect Preserve OPI Comments, and then distill the PDF file.
- Use a proxy OPI workflow and embed proxies in the PDF (no Omit).
- In InDesign, select the PDF and apply a transparency option. See "Specifying transparency" in InDesign Help for instructions.
Use an image-editing application such as Adobe Photoshop to save the PDF file as an EPS image. Then place the EPS image into the InDesign document.
To verify the number of spot colors you are using, open your Swatches palette. Swatch names followed by a square with a gray circle in it are spot colors.
To convert all colors to process colors via Ink Manager, do the following:
If you select the Output page in the Print dialog, you see that only Cyan, Magenta, Yellow, and Black inks are listed in the Inks section.
Note: This problem only occurs when you print to a PostScript printer. If you have access to a non-PostScript printer, you can use it to print composites of your file.
Open the source file in the application that created it and save it to a format other than PDF. For more information, see the documentation included with the application.
Solution 10: Export the document to InDesign Interchange (.inx)format, and then check the font information.
Place the PDF file in a new InDesign document. Export the PDF file as a JPEG file, and then place the JPEG file in the original InDesign document.
To create a PostScript file in the source application, see the documentation included with the application.
To convert a PostScript file to a PDF file, do the following:
To determine if the problem is related to a damaged font, try switching all fonts used in the document to a standard font. (For example, change Arial or Times New Roman.)
If the problem recurs after you switch fonts, then it is not font-related. If the problem doesn't recur, then the original font could be damaged or out-dated (that is, created before 1992). Try reinstalling the font or obtaining an updated version from the font manufacturer.
- On Windows XP and Windows Vista, type "Adobefnt*.lst" (including the quotation marks) in the All Or Part Of The File Name box, and then click Search.
- On Windows 2000, type "Adobefnt*.lst" (including the quotation marks) in the Named box, and then click Find Now.
- On Mac OS X v10.4.x, click the Computer button, type Adobefnt in the text field beside File Name Is, and then click Enter.
- On Mac OS X v10.2.x-v10.3.x, choose Local Disks from the Search In menu, type Adobefnt in the box beside File Name Is, and then click Search.
Note: For Mac OS 10.5x, if no adobefnt.lst file is found, then add system files in the search criteria in the File > Find dialog box.
This error has several potential causes. Re-creating the preference files corrects the most common causes, which include the following:
- Printing to a non-PostScript printer immediately after printing to a PostScript printer with Scale To Fit selected.
- Canceling a print job during the printing or spooling process.
- Printing with damaged preference files.
Other potential causes include the following:
- Printing a PDF file that contains OPI 2.0 comments.
- Printing a gradient that contains spot colors from different color spaces.
- Printing a tagged text file that uses out-of-range colors.
- Printing without having selected a printer in the Chooser.
- Printing with the Chooser open after making a printer selection.
In some cases, printing a PDF version of the file is a workaround. The error doesn't always occur with InDesign 1.5 or later because those versions include many printing enhancements.
InDesign returns an error when you try to print OPI 2.0 comments. The error can occur when you place PDF files that were created in QuarkXPress 5.x into an InDesign document. The issue doesn't occur with OPI 1.3 comments. Most proxies don't contain OPI 2.0 comments.