A PostScript error: typecheck is one of the most common PostScript errors. It signals that the RIP encounters an operand of a wrong type – i.e. an operator expected one type of data and got something else.
Most common causes
- Typecheck errors are usually caused by corrupted data.
- This may indicate a problem with the printer driver. Try reinstalling it if the error occurs printing from various applications. Check the network and/or server if the error persists.
- Try copying and pasting your data to a new document.
- Try opening and resaving all images and drawings.
Offending command “dF3(!2xT” (or other random characters)
If the offending command contains random characters, it may indicate a problem with the communications link or driver. This problem may also occur when PostScript files are transferred from one computer platform to another. Try using an ‘ASCII’ or ‘Text only’ format instead of a binary format when saving.
Lots of PostScript operators can cause a typecheck error. Make sure you know the offending command that caused the error and click on it in this list: aload, CCRun, div, get, image, imagemask, pdfmark, setcolor, setflat, sethalftone, setoverprint, settransfer, sh(PDF), S(PDF), stack, status.