Limitcheck errors are caused by the complexity of the document, such as there being too many path elements in a line. This error is more common on old PostScript level 1 RIPs than on Level 2 or PostScript 3 devices.
Sometimes it is not the document that is too complex, but the RIP or printer has certain limitations.
General solutions
Reduce the complexity of the file:
- In a lot of cases, redesigning the document to make it less complex can get around “limitcheck” errors.
- Breaking up the print job in smaller entities can also do the trick. Print only one page or even one color at the time. Send your page without including the images to see whether images are causing the problem.
- Ungrouping objects can be very effective. Often groups and especially groups in groups or rotated groups of objects really make it tough to render PostScript.
- Nesting files (e.g. placing an EPS in an EPS or placing a PDF file on a page) also adds to the complexity of a document and can lead to limitcheck errors (especially with the offending commands ‘save’ and ‘restore’).
- If you have a printer with a limited amount of memory you could try to reduce the number of fonts used in the document.
- Use the option ‘split long paths’ in drawing applications to split up complex path in easier to process chunks.
- If you are printing from Illustrator: if the document contains gradients, select Compatible Gradient Printing (Illustrator 7.x or earlier) or Compatible Gradient and Gradient Mesh Printing (Illustrator 8.0) in the Document Setup dialog box.
- Johan sent me an e-mail: He got a couple of limitcheck errors in PostScript 3 RIPs because of a very big ‘history’ entry in Photoshop EPS metadata. The problem is solved by deleting the metadata, but finding the offending image can be tricky in a big project. Photoshop itself has no problem with such EPS files and they can be placed in QuarkXPress documents without a problem. Using TIFF or JPEG or making it a standard procedure to remove history info from metadata (or all meta data) are valid workarounds.
Give your workflow, printer or RIP more room to work
- Lowering the resolution of your imagesetter or printer makes it easier for the RIP to calculate the job. This may seem odd but sometimes selecting a higher screen ruling is not such a bad idea as well.
- Reboot the RIP (or printer) to clear its memory.
- Some laser printers allow you to add more memory. That often does the trick and with the current RAM prices, it doesn’t even cost that much.
- If you are still using an old PostScript level 1 RIP, perform a font cache delete if you have the tools for this.
Avoid extra layers of software
- Get rid of all extra software that adds to the complexity of the job: do not use OPI, do not print using a printer queue, disable any extension or plug-in that adds stuff to the PostScript data, don’t download an error handler,….
Random characters as offending command
In QuarkXPress you can select ASCII or Binary data transfer to the RIP. If all our CMYK images are binary encoded, you should also select ‘Binary’ in the Page Set-up menu of XPress. If one of the images is ASCII encoded and you select binary transfer, you can get a ‘limitcheck’ PostScript error, offending command ‘(ÁEGD-**£12ze8’ (or other meaningless characters). Reopen all imagefiles in Photoshop, save them as binary files and print again in XPress. The problem will be solved. You could also keep the original images and redo the layout in XPress 3.11 or later as these versions of XPress are less scruffy about ASCII encoded files.
Limitcheck errors due to corrupted fonts
Another source of limitcheck errors are corrupted printer fonts on either the Mac, the server or the RIP itself. Try to find out if the limitcheck errors only occur with documents that share certain fonts. If this is the case, you should replace all those fonts with a fresh copy from the original disks.
Limitcheck errors due to insufficient memory
On laser printers, the limitcheck error can also mean that there is not enough memory to do the page size and resolution requested. A letter/a4 size page needs about 1 MB at 300 ppi, 4 MB at 600 ppi and 7 MB at 800 ppi. Double these requirements for A3/11×17 paper. Double again for duplex (double sided printing). Quadruple for color printers. This is just to hold the page; more will be needed (at least 1 MB) for fonts, paths, and other things.
Niknak causes limitcheck error
PDF files created by Niknak version 1.1 Patch Level 2 can cause limitcheck errors when printed from Exchange to an Adobe RIP. This was fixed in patchlevel 3 of Niknak.
More detailed information
There are several commands that can cause limitcheck PostScript errors. Check the specific offending command to get a more detailed error description: addglyph, clip, fill, findfont, image, restore, save, sethalftone, setscreen, show, stroke.
I use an old salvaged office printer (Kyocera Ecosys FS-1118MFP) which might not be able to handle some fancy things with recent PDFs – or, who knows, the PDF was a very crappy one?
When trying to print the PDF in questions, I got an empty page and another one with the following error message:
ERROR: limitcheck OFFENDING COMMAND: filter STACK: --nostringval-- --nostringval-- --nostringval-- --nostringval-- /DataSource --nostringval-- --nostringval-- false -mark- -mark- -mark-
A limitcheck error happens when a request “Exceeds printer’s memory or PostScript language limit.” The “offending command here” is “filter”, which probably has to do with decompressing an image.
On the second attempt at printing, the printer was stuck with the “receiving” led blinking for ages.
What helped me to print that PDF: I opened it with LibreOffice Draw (currently using version 6.1.5.2), which now does a great job at handling PDFs. I then exported it as a new PDF, which interestingly changed the size from 626.4 kB to 125.5 kB. I was then able to print the PDF without any error, and without having the printer think about it for an hour.
There will be other ways to fix that. You can try different way to reduce the complexity of the document (including converting it to an image before sending it to the printer). People often have success with reinstalling their printer for some reason.
Some links that might be of interest if you have that kind of error:
- This is the best article I have found about limitcheck errors, with lots of tips to try and resolve the issue: https://www.prepressure.com/postscript/troubleshooting/errors/limitcheck
- My particular error had the “filter” offending command. If you want to understand other offending commands: https://www.prepressure.com/postscript/troubleshooting/errors
- Adobe’s help to troubleshoot Postscript errors: https://helpx.adobe.com/x-productkb/global/troubleshoot-postscript-errors.html
- Xerox printers: https://forum.support.xerox.com/t5/Printing/ERROR-limitcheck-OFFENDING-COMMAND/td-p/7530
- HP printers: https://h30434.www3.hp.com/t5/LaserJet-Printing/ERROR-limitcheck/td-p/6501290
That was tested on an Ubuntu 18.04-derivative, with LibreOffice Draw version 6.1.5.2, Gnome Document Viewer 3.28.4 and CUPS 2.2.7.
Ошибка «Limitcheck; OffendingCommand.
Ошибка «Limitcheck; OffendingCommand: pdf mark» при дистилляции PS-файла FrameMaker 5.x
При дистилляции .PS-файла, созданного в FrameMaker 5.x, в окне Message программы Adobe Acrobat Distiller 2.1 выводится сообщение об ошибке «%%[Error: limitcheck; OffendingCommand: pdfmark]%%».
Перед генерированием PostScript-файла в FrameMaker 5.x отключите в диалоговом окне Print параметр Generate Acrobat Data. А затем создайте PDF-ссылки в Acrobat Exchange вручную.
ИЛИ: Разбейте документ FrameMaker на несколько разделов и дистиллируйте каждый из них отдельно.
Максимальное число допустимых в Acrobat Exchange или Reader именованных пунктов назначения, или гипертекстовых ссылок, составляет 4000. Если .PS-файл в FrameMaker создавать при включенном параметре Generate Acrobat Data в диалоговом окне Print, FrameMaker включает в выходной файл сотни или тысячи гипертекстовых ссылок. Многие из них не используются ни программой Exchange, ни Reader, и их число может превысить лимит в 4000.
Обрабатывая .PS-файл, Distiller 2.1 фиксирует число обнаруженных ссылок и, когда оно достигает 4000, прекращает обработку и выдает сообщение об ошибке «%% [Error: limitcheck; OffendingCommand: pdfmark]%%». Distiller 2.0 не ведет подсчета ссылок и .PS-файл обрабатывается даже если их там больше 4000. Правда, созданные с помощью Distiller 2.0 PDF-документы в программах Exchange и Reader все равно подчиняются правилу ограничения в 4000 ссылок и могут отображаться некорректно. Windows
Что значит сообщение «%%[Error: undefined; OffendingCommand: @PJL]%%», выдаваемое Acrobat Distiller при обработке PostScript-файла?
Когда ошибка PostScript описана как «undefind», значит, Distiller наткнулся в PostScript-файле на непонятную команду, а то, что следует за «OffendingCommand» (в данном случае @PJL), — это команда, вызвавшая проблему.
К счастью, причина этой проблемы проста, и решается она тоже просто. Команда @PJL входит в специальный драйвер для принтеров Hewlett-Packard, поддерживающих автоматическое переключение с режима PCL (Printer Control Language) на PostScript. Драйвер вставляет в PostScript-файлы строки (начинающиеся с @PJL), которые дают принтеру указание переключиться на режим PostScript. А поскольку Adobe Acrobat не понимает этих команд, то возвращает сообщение об ошибке.
Самый простой способ справиться с проблемой — это создать PostScript-файл заново с помощью другого PostScript-драйвера, например стандартного Windows PostScript-драйвера или драйвера Adobe PostScript, которые не вставляют команд @PJL. И тогда Distiller обработает такой файл.
Если Вы не можете создать PostScript-файл заново (например у Вас нет документа или программы, на основе и с помощью которых тот был генерирован), существует еще один способ решения проблемы — открыть файл в текстовом редакторе и удалить не-PostScript команды. Если у Вас нет навыков редактирования PostScript-кода, прибегать к этому способу не рекомендуется. А делается это так:
1. Прежде всего создайте резервную копию PostScript-файла.
2. Откройте файл в программе, сохраняющей текст в формате Text Only (Windows Write, WordPad).
3. Найдите не-PostScript код и удалите его. Искать нужно в двух местах — в верхней части файла и в нижней. Пример того, что нужно удалить в верхней части файла, см. на прилагаемом компакт-диске (у Вас могут быть другие команды, но, скорее всего, удалить надо будет все, что предваряет комментарии «% IPS-Adobe. »).
В следующем разделе на прилагаемом компакт-диске приводится пример того, что следует удалить в нижней части файла. У Вас могут быть другие команды, но выбрасывать надо будет все, что идет после комментария PostScript «%%EOF» (это означает конец PostScript-файла).
4. Закончив, сохраните файл в формате Text Only и попробуйте дистиллировать его снова. Если проблема возникает опять, обратите внимание на сообщение: если в файле все еще остается какой-нибудь ne-PostScript-код, скорее всего, ошибка будет снова идентифицирована как «undefined». В этом случае посмотрите, что следует за «Offending-Command», снова откройте PostScript-файл, найдите и удалите эту команду, сохраните файл как Text Only и попробуйте дистиллировать еще раз.
Fore kc .ru
Рефераты, дипломы, курсовые, выпускные и квалификационные работы, диссертации, учебники, учебные пособия, лекции, методические пособия и рекомендации, программы и курсы обучения, публикации из профильных изданий
Источник
Проблемы с печатью больших файлов
Все новые темы
| Автор | ||||
|---|---|---|---|---|
| DeniTornado Старожил форума Зарегистрирован: 22.10.2007 |
|
|||
| Вернуться к началу |
|
|||
 |
||||
| Зарегистрируйтесь и реклама исчезнет!
|
||||
|
||||
| DeniTornado Старожил форума Зарегистрирован: 22.10.2007 |
|
|||
| Вернуться к началу |
|
|||
|
||||
| Paranoya Почетный житель
Зарегистрирован: 14.12.2006
|
|
|||
| Вернуться к началу |
|
|||
|
||||
| DeniTornado Старожил форума Зарегистрирован: 22.10.2007 |
|
|||
| Вернуться к началу |
|
|||
|
||||
| Paranoya Почетный житель
Зарегистрирован: 14.12.2006
|
|
|||
| Вернуться к началу |
|
|||
|
||||
| mrhron Участник форума Зарегистрирован: 09.11.2010
|
|
|||
| Вернуться к началу |
|
|||
|
||||
| DeniTornado Старожил форума Зарегистрирован: 22.10.2007 |
|
|||
| Вернуться к началу |
|
|||
|
||||
| sergeykp Участник форума Зарегистрирован: 13.03.2006 |
|
|||
| Вернуться к началу |
|
|||
|
||||
| DeniTornado Старожил форума Зарегистрирован: 22.10.2007 |
|
|||
| Вернуться к началу |
|
|||
|
||||
| Paranoya Почетный житель
Зарегистрирован: 14.12.2006 Источник Adblock |
When you print, there are times when you have too many images to get printed along with texts.
HP printers, of course, allow you to get the best quality image printouts but then at times, they may lead to some issues while printing the images. There are various PostScript limitcheck errors that are reported while using HP printers. This limitcheck alerts you to check the limit that your system allows when it comes to taking image printouts. HP printer error limitcheck OFFENDING COMMAND IMAGE is one such error that is widely recorded.
Causes Limitcheck Offending Command Image Error Message HP Printer
Error Description
HP printer error limitcheck OFFENDING COMMAND IMAGE issue arises when a corrupt image is identified. The limitcheck error, however, signifies that the image in your document is too large. Either the resolution is too high or it’s unable to rotate. Limitcheck HP Printer Error Message are caused due to the complexity of the document maybe because there are too many path elements in a line.
Recommended Action
Before opting for the advanced error handling tricks, it is expected that you reduce the size or resolution of the image of the document to be printed. Rotate the image at a different angle and adjust it according to the allowed limit.
Troubleshooting Steps HP Printer Error Limitcheck Offending Command Image
Troubleshoot
Once the PostScript HP printer error limitcheck OFFENDING COMMAND issue arises, the next step is to identify the cause. Locate the error type and offending command to find out whether it is image type or font type or others. For example, if you get %%[Error: limitcheck; OffendingCommand: image]%%, this means that there is a problem with the bitmap data of the image.
Therefore, it helps you know that the error has arisen because the bitmap data exceeds the printer’s memory or PostScript language limit. There is a possibility that the problem is with the graphic in your file.
General Solutions
1. You can reduce the size of the image or minimize the resolution of it
2. If the problem is with the bitmap data, remove the graphic. Reimport it and save it in a different format
3. Reduce the document with the image by redesigning it to make it less complex to avoid limitcheck errors
4. Break up the print job into smaller parts. For example, print one page at a time or use one color at a time
5. Ungroup objects to put lesser presser on the device
6. Reduce the resolution of the imagesetter or printer for a better image printing job
HP Technical Support – Scope of Service
We provide efficient Printer Support services to customers and hence if you want to know more about the error and other instructions to follow to get rid of the HP printer error limitcheck OFFENDING COMMAND IMAGE issue. Our HP technical support team for resolutions is:
- Available to you 24*7
- Accessible to you via email, chat, and multiple telephone lines
- There to assist and guide you with conceptual and technical issues
- Always ready to help you as and when you require
- Serious about retaining the faith and trust of customers with its loyal support services
Feel free to call us at 
.
June 5, 2018November 24, 2019
That looks like either a PCL.XL error message or a PostScript message.
When it comes to printing PDFs there is one quick work around:
1. Open the PDF
2. Navigate to File > Print
3. Click on Advanced
4. Check the Print as Image checkbox (the default DPI is usually fine)
Using the Print as Image feature will alter how your printer recieves teh PDF print data as if it were a single image instead of a document with fonts and formatting that could be causing the error message.
Otherwise you will need to experiment with updating or swapping your print driver lanugage.
Experts are not HP Employees. Experts are advanced users, administrators, technicians, engineers or business partners who volunteer their time to answer community questions.
Please mark anything that is helpful with a Kudo.
When you are done troubleshooting, please mark one of the responses as the Solution.
This feedback enhances the community by helping future readers choose between multiple similar responses.
Upon updating OS 10.13.3 word and reopening HP laser jet M553 I can no longer print, but get the info on otherwise blank page: Offending command xshow.
Re-installing the newest version of the printer driver did not help, nor did any restart. No updates available.
How do I remedy this disrupting situation?
iMac,
macOS High Sierra (10.13.3),
HP laser jet M553
Posted on Jan 27, 2018 8:41 AM
«error: limitcheck — offending command: xshow» I have the same problem with a Ricoh Aficio MP C2050. I tried everything but nothing … I re-installed the ricoh driver. and deleted all the printers but nothing.
Can someone help me?
Posted on Feb 7, 2018 9:46 AM