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."
Do one or more of the following:
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 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:
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:
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.
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:
On Mac OS X:
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.
Print one page at a time.
Locate the corrupted page or link in the document.
Contact your printer manufacturer to obtain the latest version of the printer driver for your printer. If you are using the latest version of your printer's driver and the problem persists, remove the driver, then reinstall it from the original installation disks or CD-ROM.
Move pages using Move Pages command
Choose Layout > Pages > Move Pages, or choose Move Pages from the Pages panel menu.
Specify the page or pages you want to move.
For Destination, choose where you want to move the pages, and specify a page if necessary.
Click OK.
This error has several potential causes. Re-creating the preference files corrects the most common causes, which include the following:
Other potential causes include the following:
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.
Pierakstieties savā kontā