ColorSpan Legacy Print Server - Troubleshooting PostScript Errors

4
Error: stackoverflow
Explanation: A PostScript object stack contains too many objects. It’s difficult to find the cause of this.
Knowing the offending command probably won’t help. Isolate the offending elements in your file and
remove them. It could also be a memory problem, data corruption, or a communication error.
Error: stackunderflow Explanation: An expected PostScript operator isn’t on
the stack. It’s difficult to find the cause of this error. As with stackoverflow errors, knowing the offending
command probably won’t help. Isolate offending elements in your file and remove them. It also possibly
could be a memory problem, data corruption, or a communication error.
Error: syntaxerror Explanation: The program didn’t generate the
PostScript code correctly, or illegal characters were used in the code. Someone familiar with PostScript
coding could check for illegal characters in fi le names, as well as in any custom PostScript effects.
Other common causes are mismatched brackets in the code or data corruption.
Error: Timeout - input stops before job finished This error message appears when the RIP’s
time limit for receiving data is exceeded, which is usually the result of an error-prone network or faulty
network connectors. Explanation: Check your network connectors. If this is a frequent error for you,
you need to have a qualified person check your network and make necessary adjustments. Large TIFF,
PICT, and EPS graphics can cause this error. Complex fill patterns or complex type effects can also
cause this error. Also, try ungrouping large or nested groups.
Error: typecheck Explanation: Somewhere in the PostScript code, an
operator is of the wrong type. Isolate offending elements in your file and remove. Possible memory
problem, data corruption, or communication error. “Typecheck” does not necessarily mean “type” as in
“text” or “font.”
Error: undefined Explanation: The PostScript code is trying to use a
procedure that it can’t find. This error is usually the result of a corrupted EPS file that contains a
PostScript command that is not defined. Delete or replace the corrupt graphic, or try to place the
graphic into the file again. A printer prep file may be missing or not found. Possible corruption or
communication error.
Error: vmerror Explanation: The memory within your PostScript RIP
or other output device has been exhausted. This is often the result of using too many fonts within the
same document. Or, it could be caused by an EPS file that takes up too much memory. The offending
command tells you where processing stopped and memory ran out.
a. Restrict the number of fonts in your document. For example, if you are using seven fonts,
reduce the number to 3 or 4 if possible. Also, remember that when you specify a font attribute,
such as italic or bold or bold italic, you are sending another font.
b. If you routinely get this error, increase the virtual memory on the print server to 7 or 8 megs.
Rarely would you need to increase this setting above 8 megs, though it can be increased to as
high as 20 megs. Keep in mind that a higher VM setting can increase RIP times. The default is
5 megs.
Offending Commands and Possible Solutions
Offending Command: ashow Check: Kerned text, custom letter and word
spacing, baseline shifted text and superscript/subscript text. May also indicate a bad or corrupt font
Offending Command: awidthshow Check: Text justification, baseline shifted text,
and superscript/subscript text. It could also be a damaged font.
Offending Command: clip, eoclip
Check: Graduated or radial fills, clipping paths (masks), text effects, complex autotraced paths and any
text that has been converted to paths
Offending Command: curveto
Check: Complexity of curves
Offending Command: def
Check: This may be difficult to isolate. Check printer fonts, RIP memory, and imported EPS files