Error Rangecheck Offending Command Put
Contents |
(a link is in the column in the left hand column). Solutions PostScript errors caused by the PostScript command put are sometimes caused by custom fills. Check all drawings in your lay-out whether they contain custom files and either replace or recreate these. "Put" errors may also be printer error offending command put related to a damaged font. Reinstall all fonts used in your document from the original disks, both
Error Invalidaccess Offending Command Put
on your Mac or PC and your RIP. This is a known problem with Linotype PostScript level 1 RIPs when printing from FreeHand 7. A error rangecheck offending command image PostScript error invalidaccess error, offending command put can be caused by the use of an incorrect driver. I once got around this error by switching from an Agfa PPD to a generic Scenicsoft PPD while creating PostScript code for Scenicsoft Preps. Using error undefined offending command stack a PPD driver of a recent device for outputting on an older RIP can cause similar problems. I once spend half a day troubleshooting a file from a customer that kept generating rangecheck errors, offending command put. It turned out that some of the about 20 spot colors in the file had round brackets in them (one colour was named ‘bordeaux (tarif 1)') and this was unacceptable for the in-rip separation algorithm of the RIP. Changing the names of the spot colors solved the
Error: Syntaxerror Offending Command: --nostringval--
issue. The customer never experienced the problem himself because he always output preseparated files. A rangecheck error, offending command put can occur while trying to print complex Xpress 3.3 files containing lots of nested EPS files (Illustrator files which contained other Illustrator EPS files which themselves contained EPS files of scanned images). Here are three solutions for this problem: Make a back-up copy of XPress and open this copy with ResEdit. Open the PSHD resource and look for line 1007. Use the search command to find the following piece of text: /A 128 array def. Change the 128 to a higher value (like 250 or even 500). Save the altered application and use it to print the file. Although this solution works, it may still generate the "rangecheck" error if you print lots of pages in one go. You can also send the file as a composite file and have the RIP do the separation. On Agfa RIPs, this workflow is called "Inrip separaration" or ‘Composite printing'. Download the following piece of PostScript code to the Postscript level II RIP and then print your file. I cannot guarantee that this code works with non-Agfa RIPs. true 0 startjob userdict begin /F18 /array load def /array { dup 128 eq { pop 50000 } if F18 } bind def end This piece of code will remain active until the RIP is rebooted or reset. You can add it to user/boot but then the first line should not be included. 23 Decem
the RIP tries to process a value that is too small or large. This can, for instance, happen when you accidentally ask for an output size that is larger than what the output device supports. These are some of the reasons offending command nostringval why a rangecheck error pops up: Page or flat is too large / wrong papertray xerox error undefined offending command stack - This error can be caused by the operator trying to print a page that is too large for the imagesetter or
Error Unregistered Offending Command Show
CtP device. Some laster printers don't allow explicit papertray selection and generate a rangecheck error if a wrong cassette is selected. Sometimes the ‘offending command' points to the problem, as in the error message error: rangecheck,offending https://www.prepressure.com/postscript/troubleshooting/errors/put command: lettertray. A path is too long - Mark VanBuren from The Shelby Star was kind enough to report that long path names of embedded images can also lead to rangecheck errors. Try sticking to short names for folders and don't bury folders too deep in other folders. PageMaker 6.5 can cause this error - PageMaker 6.5 can also cause rangecheck errors when printing with the ‘Manage Composites on Printer' option selected in https://www.prepressure.com/postscript/troubleshooting/errors/rangecheck the CMS Preferences dialog box, or exporting to PDF with the CIE output color model selected. PageMaker 6.52 no longer generates the error under these conditions. Other commands There are several commands that can cause rangecheck PostScript errors. Click on a specific offending command to get a more detailed error description: colorimage, filter, get, getinterval, image, imagemask, makeblendedfont, put, show. 9 August 2013 1 Comment » One response to "PostScript error: rangecheck" Coscript Consulting says: June 25, 2013 at 7:02 pm /rangecheck error indicates a wide range of problems, when a numeric parameter goes out of the correct range. Little else can be determined without a sample file. Please contact Coscript Consulting for professional resolution of PostScript and PDF issies: [emailprotected] or +1 (610) 529 3475. Navigation Home Design Basics Troublefree Output Troubleshoot InDesign Prepress Workflow Systems Prepress History Printing Printed Products Printing Industry Printing Processes History of Printing Printing Museums Finishing Folding Perfect Binding Printing Dictionary A – ‘A2′ to ‘azure’ B – ‘back lining’ to ‘byline’ C – ‘C1S’ to ‘cyan’ D – ‘Dagger’ to ‘Dye’ E – ‘E-13B’ to ‘extension’ F – ‘face’ to ‘fuzzy font’ G – ‘GAA’ to ‘gutter’ H – ‘hairline’ to ‘hyphen’ I – ‘IBC’ to ‘ivory board’ J – ‘jacket’ to ‘justify’ K – ‘kanji’ to ‘KS/KSSM’ L – ‘L
CommunityCategoryBoardUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for http://forum.support.xerox.com/t5/Printing/ERROR-limitcheck-OFFENDING-COMMAND/td-p/7530 Do you mean Reply Topic Options Subscribe to RSS Feed Mark Topic as http://www.tek-tips.com/faqs.cfm?fid=3622 New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page « Message Listing « Previous Topic Next Topic » beinformedsd New Member Posts: 2 Registered: 08-05-2011 ERROR: limitcheck OFFENDING COMMAND: Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a offending command Friend Report Inappropriate Content 08-05-2011 02:16 AM Hi,I'm using a Xerox WorkCentre 7545 with the Postscript driver. Serveral users report that they get the message "ERROR: limitcheck OFFENDING COMMAND:" when printig a Word document. The document has 50 pages and after page 10 the printer stops with the error message. I have tried to break up the document in pieces, but after 10 pages the offending command put printer stops. It doesn't matter if you print page 1-10 or 11-20 etc.The print spooler is on a Windowws 2003 server. The client is Windows 7 with Office 2007.Any ideas? Solved! Go to Solution. Message 1 of 7 (53,606 Views) Reply 0 Kudos Fabio Frequent Advisor Posts: 1,540 Registered: 10-11-2010 Re: ERROR: limitcheck OFFENDING COMMAND: Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content 08-05-2011 02:34 AM have you tried disabling : "advanced printing features" , you can find it if you open the printer properties, then the tab advanced, that at the bottom you can unchech that option Message 2 of 7 (53,605 Views) Reply 0 Kudos beinformedsd New Member Posts: 2 Registered: 08-05-2011 Re: ERROR: limitcheck OFFENDING COMMAND: Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content 08-08-2011 04:49 AM Hi Fabio,this solves the problem. Do you have any idea why I can print the document when this option is disabled?Thanks in advance! Message 3 of 7 (53,586 Views) Reply 0 Kudos Fabio Frequent Advisor Posts: 1,540 Registered: 10-11-2010
Join INTELLIGENT WORK FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Xerox/Tektronix Printers Forum at Tek-Tips Home > Forums > Server Rack > Printers > Xerox/Tektronix Printers > FAQs Xerox/Tektronix Printers FAQ Forum Search FAQs Links MVPs Post Script Errors Getting an Offending Command? by neo3 faq723-3622 Posted: 22May03 --------------------------------------------------------------------------------Note: The key to troubleshooting PostScript errors is determining the frequency of the error. If the error only occurs when printing one file or from one application, it is probably not an issue with the printer or driver. In this case, it is recommended to contact the application vendor for assistance in resolving the PostScript error. --------------------------------------------------------------------------------General InformationWhile the PostScript error message you receive from the error handler probably gives good information on the source of the problem, there may be additional troubleshooting that needs to be done. Typically, PostScript errors occur on one of many different levels. The source of the error can be in: the system itself a particular application a particular file a single element in a file Before troubleshooting the error in any great detail, it is often worth trying to print again, to see if the problem is repeatable. Also, verify that you are not trying to print an EPS (Encapsulated PostScript) file. EPS files are meant only for importing i