Error limitcheck offending command image

As you may already have guessed, an ‘image’ error points to a problem with one of the bitmap images in your file.

Possible solutions

Often a corrupted image leads to this type of error. You can easily trace which image causes the problem from applications like QuarkXPress that allow you to print jobs without the images. If the PostScript error doesn’t occur then, you can start trying to locate the bad image. Set half of your images to non-printing and try printing again. Again halve the number of images and print again and keep doing this until you located the bad one.

Updating your application and/or printer driver to the latest release could also solve issues with an offending command ‘Image’ error.

If you run into this problem when printing from Adobe Reader,  try the ‘Print as Image’ option which can be found selecting the Advanced button on the Print panel.

If the info below doesn’t point to a more specific workaround, try the basic troubleshooting tips.

PostScript error Limitcheck

If you get a PostScript error ‘limitcheck’ offending command ‘image’, an image in your document is too large, its resolution is too high or it cannot be rotated. Reduce the size or resolution, rotate the image at a different angle or rotate it in an application like Photoshop.

Some older level 2 versions of PostScript RIPs as well as Acrobat Distiller 4.0 (and 4.05 and probably 3.x) cannot handle copydot files in which the number of pixels exceeds 32000 in either direction. Using such big copydot files (eg larger than about 33 centimeters for a 2400 dpi copydot) can lead to a PostScript error ‘limitcheck’ offending command ‘image’.

If you get a PostScript error ‘limitcheck’ offending command “image” when printing from InDesign 1.0, the document probably contains a multitone EPS (duotone, tritone,.. ) that uses a spot color. To get around the error, you can either perform the color separation in InDesign itself (deselect ‘In-RIP’ in the separations tab) or you should upgrade your RIP to Adobe PostScript version 3011 or later.

PostScript error IOerror

An ‘ioerror’, offending command ‘image’ or ‘colorimage’ points to an incorrect amount of data in an image or it indicates that the printer’s PS interpreter reads beyond the end of the job while rendering an image. Two possible solutions:

• Make sure that the channel used to connect the printer to your system is truly binary or try to change you printer driver’s settings from binary to ASCII. In general, parallel (Centronics) interfaces do not support binary data transfer, serial and network interfaces do.
• Scan, edit, or import the image again.

PostScript error Typecheck or Rangecheck

A PostScript error ‘typecheck’ or ‘rangecheck’ orrurs when you try printing a PostScript level 2 file to a PostScript level 1 device. Check the driver settings.

Troubleshoot PostScript errors

You can receive a PostScript error when sending a file to a PostScript interpreter (for example, a printer, Acrobat Distiller). A PostScript error occurs when the PostScript interpreter can’t read the file’s PostScript code. An error can also occur if the file’s PostScript code exceeds one or more of the limits in the PostScript page description language. If your PostScript interpreter appears to process data but then stops, a PostScript error could have occurred.

A PostScript error message includes a PostScript error type, which defines the type of error it is. It also includes an offending command, which usually indicates the specific part of the PostScript code that the interpreter couldn’t read. The offending command usually indicates the command that caused the problem. Some PostScript errors point you right to the cause of the problem, and some get you looking in the right direction.

Example of a PostScript error:

For example, the PostScript error %%[Error: dictfull; OffendingCommand: def ]%% contains the PostScript error type «dictfull» and the offending command «def.» The error type indicates that the dictionary contains the maximum number of entries. The offending command is the last command the PostScript interpreter tried to process, «def,» which defines a new word in the dictionary.

View or print a PostScript error message

If you think a PostScript error has occurred, but it doesn’t appear onscreen or in your printout, you can sometimes view or print the error message. Do one or more of the following:

• Use an error handler utility. For example, Adobe PageMaker has the Include PostScript Error Handler option in the Print Options dialog box.
• In Windows, configure the printer to print the error message:

Note: In Windows NT, you cannot configure a printer to print an error message.

Note: If PostScript Options isn’t visible, double-click Document Options

• In Mac OS, configure the Apple LaserWriter 8 or Adobe PS printer driver to print the error message by doing one of the following:
  • Choose either Job logging or Error Handling from the pop-up menu in the Print dialog box, and click Options. Select either Summarize On Screen or Print Detailed Report, and then click Print.
  • Choose Background Printing from the pop-up menu in the Print dialog box, select Foreground, and then click Print.

Use the PostScript error message to start troubleshooting

After you identify a specific PostScript error message, you can begin troubleshooting the cause. To begin troubleshooting, locate the error type and offending command in the «PostScript Error Types» and the «PostScript Offending Commands» parts of this document. You can then try to repair the problem.

For example, you could receive the PostScript error, «%%[Error: limitcheck; OffendingCommand: image ]%%.» Your first step is to locate «limitcheck» in the «PostScript Error Types» section. The «PostScript Error Types» section lists «limitcheck» under the heading «Exceeds printer’s memory or PostScript language limit.» The «PostScript Offending Command» lists «image» under the heading that indicates a problem with bitmap data. So, you have bitmap data that exceeds the printer’s memory or PostScript language limit. The likeliest source of bitmap data is a graphic in your file. You can then check graphics in your file to see if one or more is causing the problem. If you find a likely culprit, you can delete the graphic, reimport it, save it in different format, or simplify it (for example, reduce its dpi). You can also try printing the file to a printer with more memory.

Some PostScript errors don’t help you determine a likely cause. For example, you could receive the PostScript error «%%[Error: undefined; OffendingCommand: ]%%.» The «PostScript Error Types» section lists «undefined» under the «Errors that indicate unintelligible PostScript code» heading. The «PostScript Offending Command» section lists «» under the heading that indicates a problem with any element or file. In this case, your file contains PostScript code the PostScript interpreter can’t recognize. See the «Troubleshooting Possible Causes for the PostScript Error» section to continue troubleshooting.

PostScript error types

Following are common error types, grouped by general cause.

The following error types indicate that something exceeds the PostScript interpreter’s memory or a PostScript language limit:

• dictfull
• fatal system error at [various]
• limitcheck
• VMerror
• The following error types indicate communication problems:
• interrupt
• ioerror (a disk problem on the printer’s hard disk, such as a bad sector can also cause this error)
• timeout

The following error types indicate the file contains unintelligible PostScript code:

• configurationerror
• dictstackoverflow
• dictstackunderflow
• execstackoverflow
• handleerror
• invalidaccess
• invalidexit
• invalidfileaccess
• invalidfont
• invalidrestore
• nocurrentpoint
• rangecheck
• stackoverflow
• stackunderflow
• syntaxerror
• typecheck
• undefined
• undefinedfilename
• undefinedresource
• undefinedresult
• unmatchedmark
• unregistered

PostScript offending commands

Following are common offending commands, grouped by general cause.

The following offending commands indicate a problem with specific text or a font element:

• addglyph
• ashow
• awidthshow
• charpath
• definefont
• findfont
• imagemask
• kshow
• makefont
• removeglyphs
• selectfont
• show
• startdata
• stringwidth
• usefont
• widthshow

Note: For font-related errors, try changing the font-related settings in the device driver. For example, in the printer’s properties (Windows), click Advanced, then, in the Graphics section, change the TrueType Font option to Download as Softfont.

The following offending commands indicate a problem with specific masks (for example, clipping paths):

The following offending commands indicate a problem with fills and lines, often in imported object-oriented, or vector, graphics (for example, EPS, PICT):

• arc
• arcto
• currentpoint
• curveto
• eofill
• fill
• lineto
• moveto
• rcurveto
• rlineto
• setdash
• setlinecap
• setlinejoin
• shfill
• stroke

The following offending commands indicate a problem with bitmap data:

• colorimage
• image
• imagemask (associated with 1-bit image bitmap graphics and bitmap fonts)

The following offending commands indicate a problem with any element or graphic:

• array
• currentsmoothness
• currenttrapparams
• def
• dict
• exch
• get
• index
• itransform
• nostringval
• packedarray
• put
• restore
• save
• setcolor
• setgray
• setpageparams
• setsmoothness
• settrapparams
• settrapzone
• setscreen
• [random characters]

Troubleshoot possible causes of a PostScript error

Many PostScript error messages readily indicate the source of a problem. Troubleshoot a problem further if you receive a non-specific PostScript error message, or if a PostScript error occurred without a message. To troubleshoot a PostScript error, isolate when the problem occurs to determine if it is a system-level, application-specific, file-specific, or element-specific problem. After you isolate when the problem occurs, you can eliminate likely causes until you solve the problem.

Isolate system-level printing problems

Do you receive the error from more than one application? If the same problem occurs from more than one application, the cause is most likely a problem at the system level. Damaged fonts, damaged system files, damaged printer drivers, insufficient hard disk space, network problems, or hardware problems commonly cause system-level problems. If the problem occurs only from one application, see the «Isolating Application-Specific Problems» section.

Make sure that you use an up-to-date PostScript device driver (for example, printer driver). Or, use the version of the driver required by the application. You also need plenty of free hard disk space when sending a file to a PostScript interpreter, especially when you print a large file. Make sure that free hard disk space is defragmented.

If you print to an external PostScript device, secure loose connectors (for example, cables, switch boxes) by unplugging and replugging them. You can easily tell if a connection to an external device is severed altogether: The device doesn’t receive any data, so nothing happens. But if a connection is loose, the symptoms of a problem can be unclear. The device receives small jobs only, or its driver appears only intermittently in the Chooser in Mac OS.

If you print to an older PostScript printer or one that uses a PostScript emulator (for example, a LaserMaster or LexMark printer), it possible it doesn’t recognize newer PostScript code. Try printing the file to a printer or RIP that contains a more current version of Adobe-licensed PostScript.

Isolate application-specific problems

Do you receive the error only from a single application, and in every file from that application? To determine if the application or a specific file causes the error, create a file with only a simple element, such as a rectangle. If the error doesn’t occur with this test file, the application itself isn’t causing the error, so you can move to the «Isolating File-Specific Problems» section. If this test file does cause the error, the application software could be damaged. Delete the application’s preferences file, and then reinstall the application from the original installation disks.

Isolate file-specific problems

Do you receive the error only with a specific file or files? If the error occurs only with a specific file, the file could have the wrong print settings selected for your PostScript interpreter. Or, it could be damaged or contain a problem element (for example, a damaged graphic). You can begin troubleshooting the file by using the same print settings as the settings of a file that doesn’t cause an error.

To determine if the file itself is damaged, copy the file’s contents into a new file. Save the new file using the Save As command, and then see if the error occurs with the new file. If the error doesn’t occur, the original file is damaged. If the error does occur, run any built-in diagnostic routines your application offers.

Isolate element-specific problems

Do you receive the error only with a specific page or elements on a page? After you rule out a damaged file as the cause, a damaged or incorrectly written element or font is likely causing the error. An element or combination of elements that requires more memory than is available could be causing the error. If the error occurs with a range of pages, look for common elements on those pages. If you can print all elements individually or in small groups, the combination of elements you print requires more memory than is available.

To isolate the element or elements that cause the problem, make a copy of the file. Then send groups of pages to the PostScript interpreter. If a group causes an error, print one page at a time from that group. Continue sending pages until you narrow down the problem page. You can then isolate the elements causing the problem by removing elements from each page. If you remove a page and the error doesn’t recur, the elements you just removed cause the problem.

If an element that causes the problem is text or an element you created in the application, re-create the element. For text elements, you can also try using a different font (for example, reformat the text using a different type of font). If the error doesn’t recur with a different font, the previous font is damaged. Reinstall it from the original media.

If the element causing the problem is an imported graphic, first try reimporting the graphic. If the error still occurs, open the graphic in the application in which it was created, resave it with a different name. Make sure that it prints from that application, and then reimport the graphic. If the imported graphic still causes the error, try resaving it in a different format. Or, export it from a different application, or simplify it so that it requires less memory. An imported graphic can cause a PostScript error if it contains damaged or incorrectly written information. It can also cause an error if it is too complex for the PostScript interpreter (for example, it requires more memory than is available).

If the file causes a PostScript error because it is too complex, simplify it and see if it prints. To begin simplifying a complex file, do the following:

• reduce the number of imported graphics
• reduce the number of fonts that are downloaded
• reduce the number of text effects (for example, skewing, rotation)
• delete elements you don’t need, create paths using fewer points
• reimport bitmap images with ones that have been resampled at a lower resolution

Graphic formats such as EPS are updated periodically, so older applications can use an older graphic standard that newer PostScript interpreters can’t understand.

Источник

Offending command: image

As you may already have guessed, an ‘image’ error points to a problem with one of the bitmap images in your file.

Possible solutions

Often a corrupted image leads to this type of error. You can easily trace which image causes the problem from applications like QuarkXPress that allow you to print jobs without the images. If the PostScript error doesn’t occur then, you can start trying to locate the bad image. Set half of your images to non-printing and try printing again. Again halve the number of images and print again and keep doing this until you located the bad one.

Updating your application and/or printer driver to the latest release could also solve issues with an offending command ‘Image’ error.

If you run into this problem when printing from Adobe Reader, try the ‘Print as Image’ option which can be found selecting the Advanced button on the Print panel.

If the info below doesn’t point to a more specific workaround, try the basic troubleshooting tips.

PostScript error Limitcheck

If you get a PostScript error ‘limitcheck’ offending command ‘image’, an image in your document is too large, its resolution is too high or it cannot be rotated. Reduce the size or resolution, rotate the image at a different angle or rotate it in an application like Photoshop.

Some older level 2 versions of PostScript RIPs as well as Acrobat Distiller 4.0 (and 4.05 and probably 3.x) cannot handle copydot files in which the number of pixels exceeds 32000 in either direction. Using such big copydot files (eg larger than about 33 centimeters for a 2400 dpi copydot) can lead to a PostScript error ‘limitcheck’ offending command ‘image’.

If you get a PostScript error ‘limitcheck’ offending command “image” when printing from InDesign 1.0, the document probably contains a multitone EPS (duotone, tritone. ) that uses a spot color. To get around the error, you can either perform the color separation in InDesign itself (deselect ‘In-RIP’ in the separations tab) or you should upgrade your RIP to Adobe PostScript version 3011 or later.

PostScript error IOerror

An ‘ioerror’, offending command ‘image’ or ‘colorimage’ points to an incorrect amount of data in an image or it indicates that the printer’s PS interpreter reads beyond the end of the job while rendering an image. Two possible solutions:

• Make sure that the channel used to connect the printer to your system is truly binary or try to change you printer driver’s settings from binary to ASCII. In general, parallel (Centronics) interfaces do not support binary data transfer, serial and network interfaces do.
• Scan, edit, or import the image again.

PostScript error Typecheck or Rangecheck

A PostScript error ‘typecheck’ or ‘rangecheck’ orrurs when you try printing a PostScript level 2 file to a PostScript level 1 device. Check the driver settings.

Источник

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. 

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.

Looks like no one’s replied in a while. To start the conversation again, simply

ask a new question.

ERROR: limitcheck OFFENDING COMMAND: imagemask