Error Rangecheck Offendingcommand Setpagedevice

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,

Developer Network (CDN) ForumsCitrix Insight ServicesCitrix ReadyCitrix Success KitsCloud Provider PackCloudBridgeCloudPlatform (powered by Apache CloudStack)CloudPortalDemo CenterDesktopPlayerEdgeSightEducationForum PrototypeHDX MonitorHDX RealTime Optimization PackHotfix Rollup PackJapanese ForumsKnowledge Center FeedbackLicensingLTSRNetScalerNetScaler E-Business CommunityNetScaler Gateway (Formerly Access Gateway)Profile ManagementProof of Concept KitsProvisioning ServerQuick Demo ToolkitReceiver, Plug-ins, and Merchan...Secure GatewayShareFileSingle Sign-On (Password Manager)SmartAuditorStoreFrontTechnology PreviewsTrial SoftwareUniversal Print ServerUser Group CommunityVDI-in-a-BoxWeb InterfaceXenAppXenClientXenDesktopXenMobileXenServer Discussions Support Forums Products Receiver, Plug-ins, and Merchandising Server Receiver for Macintosh Javascript Disabled Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. Printing in Receiver 11.5 Started by Phillip Williams , 21 June 2012 - 04:30 AM https://www.prepressure.com/postscript/troubleshooting/errors/limitcheck Login to Reply 4 replies to this topic Phillip Williams Members #1 Phillip Williams 3 posts Posted 21 June 2012 - 04:30 AM We are running XenApp 6.5 on Win2008 64bit. Clients are running Citrix Receiver 11.5 on OS X 10.7.2/10.7.4. When clients connect to the server their local printers are auto created on the server with a driver of 'HP Color LaserJet 2800 Series http://discussions.citrix.com/topic/309139-printing-in-receiver-115/ PS'. When users print to these printers, a page prints out with the following error printed on it:ERROR: range checkOFFENDING COMMAND: setpagedeviceSTACK:-dictionary-This is printing to a Fuji Xerox ApeosPort 2200. I installed its driver onto the server, then created a policy to map that driver to the clients when they connect. Then when printing to the printer, Citrix Receiver just crashes.Can anyone assist?As a sidenote, Does Citrix Universal Printing work on Macs and Receiver 11.5? I would be happy to just have one printer visible to the end users with a universal driver if possible. 1252-309139-1653222 Back to top Phillip Williams Members #2 Phillip Williams 3 posts Posted 02 July 2012 - 08:14 AM I was able to resolve this error by installing PostScript drivers for the Fuji Xerox 2200 and using Citrix Policy to apply that driver to all unknown printers. The only problem I am still having is that these client printers are network printers, and in the Windows Event Log they dont list the driver name they are attempting to use, it just lists UNKNOWNORBADDRIVER. If anyone knows of a way to fix that, I'm all ears. 1252-309139-

OFFENDING COMMAND: filter) - Adobe Acrobat Windows We are attempting to print off some rather large image files on a Xerox 340 and http://www.justskins.com/forums/postscript-print-error-error-100990.html an HP Laserjet 4MV printer via Adobe Acrobat 6. Smaller similar https://helpx.adobe.com/x-productkb/global/troubleshoot-postscript-errors.html files print fine, but when we try to print some of the larger files we get a sheet with the following printed instead of the image: ------------------------------------------------ ERROR: rangecheck OFFENDING COMMAND: filter STACK: /CCITTFaxDecode -dictionary- -filestream- -filestream- -mark- /_Filters [1.0 0.0 ] /Decode 1 error rangecheck /BitsPerComponent [25386.0 0.0 0.0 -6552.0 0.0 6552.0 ] /ImageMatrix 6552 /Height 25386 /Width 1 /ImageType -mark- -savelevel- ---------------------------------------------------- From searching the Adobe site, it sounds like the "ERROR: rangecheck" ... Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode May 12th,09:05 error rangecheck offendingcommand PM #1 Postscript Print error (ERROR: rangecheck; OFFENDING COMMAND: filter) We are attempting to print off some rather large image files on a Xerox 340 and an HP Laserjet 4MV printer via Adobe Acrobat 6. Smaller similar files print fine, but when we try to print some of the larger files we get a sheet with the following printed instead of the image: ------------------------------------------------ ERROR: rangecheck OFFENDING COMMAND: filter STACK: /CCITTFaxDecode -dictionary- -filestream- -filestream- -mark- /_Filters [1.0 0.0 ] /Decode 1 /BitsPerComponent [25386.0 0.0 0.0 -6552.0 0.0 6552.0 ] /ImageMatrix 6552 /Height 25386 /Width 1 /ImageType -mark- -savelevel- ---------------------------------------------------- From searching the Adobe site, it sounds like the "ERROR: rangecheck" indicates there is a problem with "unintelligible PostScript code", however I cannot find any reference to what "OFFENDING COMMAND: filter" means or how to fix this problem. If anyone has any information or suggestions, I would love to hear from you. Thanks Darrell_J_Brown@adobeforums.com Guest May 13th,11:24 AM #2 Re: Postscript Print error (ERROR: rangeche

a PostScript error Applies to : Illustrator InDesign PageMaker Photoshop PostScript printer drivers 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:%%[Error: ; OffendingCommand: ]%%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. Choose one of the following: Start > Settings > Printers (Windows 2000)Start > Printers And Faxes (Windows XP)Start > Control Panel > Printers (Windows Vista, Windows 7) Right-click the printer you are using, and then choose Printer Properties. Select the General tab, select Printing Preferences, and then click Advanced. Expand Document Options, and then expand PostScript Options