Offending command: string

A PostScript error Limitcheck; offending command: String may point to memory related problems. A simple reboot of your RIP may help. If there is a way to provide it with more memory, that might also do the trick.

An application may also write bad PostScript code and exceed the  maximum allowable string length. Check if updates are available that address this issue.

Matt send me an e-mail: “I got this error in Distiller 4.0 when distilling a Quark postscript file. I had a duotone that a ‘yellow’ color in it, which I didn’t need so I changed it to a monotone EPS and then the thing distilled. Not proper troubleshooting, but I must move on. Love the site!”

27 November 2015

2 responses to “Offending command: string”

  1. Mike says:

    Hi,
    I am receiving this error message when trying to print from .DWF to .PDF, can you help me solve this problem?

    Thanks,
    Mike

    %%[ ProductName: Distiller ]%%
    %%[ Error: limitcheck; OffendingCommand: string ]%%

    Stack:
    122400
    /mystring
    24
    2031
    40800

    %%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
    %%[ Warning: PostScript error. No PDF file produced. ] %%

    • Laurens says:

      Tough one as this is a very generic error message. The best work-around is probably to switch to another way of generating a PDF file, e.g. by using the ‘export to PDF’ option that many apps offer.

Leave a Reply

Your email address will not be published. Required fields are marked *


Advertising