Troubleshooting
Solving or finding a work-around for PostScript errors can be a long and frustrating process. Usually the PostScript devil, who obviously is called Murphy, waits until late Friday afternoon before showing up. He has this annoying habit of using cryptic error messages to confuse your printer, your workflow and above all: yourself.
These pages provide background information about the essentials of PostScript errors next to a database of known issues and possible work-arounds.
- The basics of PostScript errors: What is PostScript for, how did it evolve and which alternatives are available on the market?
- PostScript errors: A long list of every type of PostScript error that I am aware of or found references to. The 10 most frequently occurring errors, listed in the order of importance with the most ‘popular one’ first, are:
- Offending command image
- PostScript error limitcheck
- Offending command setdistillerparams
- PostScript error undefined
- PostScript error rangecheck
- Offending command get
- Offending command findfont
- PostScript error typecheck
- Offending command pdfmark
- PostScript error invalidfont
- Basic Postscript troubleshooting: What to do when the above list doesn’t offer an immediate solution or work-around.
27 December 2011
%%[ Error: typecheck; OffendingCommand: setcolor ]%%
Stack:
0.867
0.871
0.871
-mark-
%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%
With any PostScript error, first look up the error and offending command in my overview at http://www.prepressure.com/postscript/troubleshooting/errors
If that doesn’t help, the general tips don’t help and a search across the web doesn’t bring up any useful clues, post a message at http://forums.b4print.com/ – there might be someone on the forum who can help you.
Postscript errors are a pain. SO on that note, open the pdf in Acrobat, go to file, print, select advanced, put a check mark in the “Print As Image” check box, hit ok and print away. This is only a work around not a fix.
Cheers
Here is the error I get when trying to distill a postscript file made with quark 7.5 file with Adobe Distiller professional 8.1.3
Anyone have idea what it means?
I liked the old version better it use to give you your errors in English not some kind of weird code.
%%[ Error: limitcheck; OffendingCommand: 6d1cfe1ec58bf0b995cce6f36574c7c0efb466398c1c62d79ba71e2455ea2364cb9026a9ca72bbeb9160f04f68dddad9f36bc9ba1eb822c3acb054c7c852a99 ]%%
Stack:
-dict-
-dict-
false
12
12
0.0
0.0
1.0
0.0
0.0
1.0
-14149.5
-11100.0
33.3333
0.0
0.0
33.3333
0.0
0.0
1.0
0.0
0.0
1.0
0.0
0.0
1.0
0.0
0.0
1.0
0.0
0.0
1.0
0.0
0.0
1.0
0.0
0.0
1.0
0.0
0.0
1.0
0
0
-null-
-null-
1
1
1
0
0.0
0
0
1.0
1
-1
false
0
-null-
-null-
-null-
-null-
1.0
0.0
0.0
0.0
0
false
false
false
424.485
333.0
/stringtype
5
100
99
98
97
0
false
/arraytype
5
/DeviceGray
/arraytype
1
1
false
false
/arraytype
1
/DeviceCMYK
false
1.0
0.0
0.0
0.0
%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%
Getting Offending command:flase message when trying to
print a barcode to a PS printer.
The command in the error message is indeed ‘flase’
If I remove the bar code then it prints.
1. Offending command image
Rotate the image 90 degrees.