PostScript error: typecheck

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 cause 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.

Also check

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.

9 August 2013

8 responses to “PostScript error: typecheck”

  1. Most od PostScript operators can fail with a /typecheck error. Little more can be determined without a sample file.

    Please contact Coscript Consulting for professional resolution of PostScript and PDF issies: [email protected] or +1 (610) 529 3475.

  2. Webhoncho says:

    I ran into this problem on a Outlook email in HTML format. When I saw the original comment about a “bad” character, I selected all text in the email and just set everything to a specific font, Calibri since I like that style. I didn’t change anything else – and bingo, it prints to PDF fine now.

    Thought I’d mention this is something to try. The “solution” is not very explicit in the above comments and it might work for you too.


    it happening on IR500



    {–pop– –pop– ct_str1 –exch– 0 –exch– –put– ct_str1 –show–
    {_ct_na _ct_i –get–} –stopped– {–pop– –pop–} {_ct_x _ct_y
    –moveto– 0 –rmoveto–} –ifelse– /_ct_i _ct_i 1 –add– –def–
    –currentpoint– /_ct_y –exch– –def– /_ct_x –exch– –def–}

  5. Jojakim says:

    In my case, I had a bad EPS which I opened and resaved in Illustrator. Also outline the fonts may be a solution.

  6. Blue says:

    I have a cshow error. The log says:
    %%[ Error: typecheck; OffendingCommand: cshow ]%%

    {–pop– –pop– ct_str1 –exch– 0 –exch– –put– ct_str1 –show–
    {_ct_na _ct_i –get–} –stopped– {–pop– –pop–} {_ct_x _ct_y
    –moveto– 0 –rmoveto–} –ifelse– /_ct_i _ct_i 1 –add– –def–
    –currentpoint– /_ct_y –exch– –def– /_ct_x –exch– –def–}

    %%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
    %%[ Warning: PostScript error. No PDF file produced. ] %%
    Distill Time: 00 Hour(s) : 00 Minute(s) : 00.921 Second(s)
    **** End of Job ****

  7. bob says:

    Not sure what this error is with xshow at the offending command, I did searching on the internet and couldn’t find anything. I know that I found the character to be at fault, because when I take it out the email prints fine from entourage 2004. The character is a comma set at 36 pt verdana. I am not sure how this can be as the rest of the title prints fine, which is also set to verdana. Any help is much appreciated.