Postscript Error Error Configuration Error Offending Command Setpagedevice
Contents |
a more detailed error message which might help in pinpointing the cause of the error. In general, setpagedevice errors are caused by incorrect driver settings or insufficient memory available on the RIP. postscript setpagedevice example Driver problems The use of incorrect settings or an incorrect driver typically cause
Error Undefined Offending Command Stack
a PostScript error: configurationerror, offending command: setpagedevice. If there is more information available (e.g. an extra line marked offending command image ‘errorinfo' or ‘additional information'), this may point to the most likely cause of the problem. For example: additional information: [/PageSize [0 792]] clearly points to a problem with the selected output error syntaxerror offending command size. If you use an incorrect PPD driver to access features like in-rip separation or in-rip trapping, this can cause setpagedevice errors. Make sure you use the latest PPD/driver for your specific device. Trying to output pages that are physically too large for a specific output device can also cause setpagedevice errors. Make sure that rounding errors don't spoil your fun if you
Offending Command Nostringval
try to output the largest possible page. Another popular cause for such errors is the use of an inappropriate resolution, like asking for output at 1270 dpi while the output device only supports 1200 dpi. I once encountered setpagedevice errors when printing jobs from Preps to a particular RIP. It took me half a day to find out that the PostScript files that were imported in Preps had been created using the driver for that particular RIP. This had never caused any problem but in this particular case, you had to use a PPD from Preps itself. Memory related problems When a RIP runs out of memory while processing a job, this can also cause setpagedevice errors. Some of the things you can try: Try to output the job page by page or even colour by colour. Lower the resolution of the output device. Use a lower screen ruling. Simplify the document. Reboot the RIP to solve any problems with memory leaks. Allocate more memory to the RIP or add RAM if possible. 9 August 2013 4 Comments » 4 responses to "Offending command: Setpagede
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 error unregistered offending command show cases, redesigning the document to make it less complex can get around "limitcheck" errors. Breaking up the xerox error undefined offending command stack 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
Error Unregistered Offending Command Xshow
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 https://www.prepressure.com/postscript/troubleshooting/errors/setpagedevice 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 https://www.prepressure.com/postscript/troubleshooting/errors/limitcheck 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 qu
BMO. For more details see Persona Deprecated. Last Comment Bug283437 - [Postscript] If the page size is not set correctly, there will be a https://bugzilla.mozilla.org/show_bug.cgi?id=283437 PostScript error "configurationerror" Summary: [Postscript] If the page size is not set correctly, https://bz.apache.org/ooo/show_bug.cgi?id=6989 there will be a PostScrip... Status: RESOLVED INVALID Whiteboard: Keywords: Product: Core Classification: Components Component: Printing: Output (show other bugs) Version: Trunk Platform: x86 Linux Importance: -- normal (vote) TargetMilestone: --- Assigned To: Leon Sha QA Contact: TriageOwner: Jet Villegas (:jet) Mentors: URL: Depends on: Blocks: Show dependency tree /graph Reported: offending command 2005-02-24 02:26 PST by Leon Sha Modified: 2006-04-29 01:30 PDT (History) CC List: 3 users (show) jsmeix kherron+mozilla roc See Also: Crash Signature: (edit) QA Whiteboard: Iteration: --- Points: --- Has Regression Range: --- Has STR: --- Tracking Flags: Attachments Patch (1.29 KB, patch) 2005-02-24 02:32 PST, Leon Sha kherron+mozilla: review+ roc: superreview+ Details | Diff | Splinter Review Patch with kherron+mozilla's comments. (1.25 KB, patch) error offending command 2005-02-27 22:15 PST, Leon Sha roc: superreview+ Details | Diff | Splinter Review Use (<<) cvx exec to replace << (1.20 KB, patch) 2005-03-08 02:38 PST, Leon Sha no flags Details | Diff | Splinter Review Patch with kherron+mozilla's comments. (1.34 KB, patch) 2005-03-09 00:26 PST, Leon Sha kherron+mozilla: review+ roc: superreview+ Details | Diff | Splinter Review Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.) Description Leon Sha 2005-02-24 02:26:20 PST If the page size is not set correctly, there will be a PostScript error "configurationerror" ERROR: configurationerror OFFENDING COMMAND: setpagedevice. STACK: -dictionary- Comment 1 Leon Sha 2005-02-24 02:32:58 PST Created attachment 175413 [details] [diff] [review] Patch I use "<<" here. This is a postscript level 2 operator. But If the postscript interpreters only support level 1, it will not have "setpagedevice". This part of postscript code will not be used by postscript level 1 interpreters. Comment 2 Kenneth Herron 2005-02-27 16:29:06 PST Comment on attachment 175413 [details] [diff] [review] Patch > // Tell the printer what size paper it should use > fprintf(f, > "/setpagedevice where\n" // Test for the feature >- "{ pop 1 dict\n" // Set up a dictionary
Login: [x] First Last Prev Next This issue is not in your last search results. Issue6989 - setpagedevice error in generated PostScript Summary: setpagedevice error in generated PostScript Status: CLOSED IRREPRODUCIBLE Product: gsl Classification: Code Component: www Version: current Hardware: PC Linux, all Importance: P3 Trivial (vote) TargetMilestone: --- Assigned To: issues@gsl QA Contact: issues@gsl URL: Keywords: Depends on: Blocks: Show dependency tree /graph Reported: 2002-08-14 16:29 UTC by Unknown Modified: 2003-03-13 10:14 UTC (History) CC List: 1 user (show) issues See Also: Issue Type: DEFECT Latest Confirmation in: --- Developer Difficulty: --- Attachments Add an attachment (proposed patch, testcase, etc.) Note You need to log in before you can comment on or make changes to this issue. Description Unknown 2002-08-14 16:29:54 UTC This applies to OpenOffice.org1.0, soffice. In certain documents converted from Microsoft Word format, and then printed, the print job fails (on the 3 printers I've tried) with the error ERROR:configurationerror OFFENDING COMMAND: setpagedevice When I investigated, I found that the problem was caused by these lines in the PostScript: %%BeginSetup % %%BeginFeature: *PageSize Letter <> setpagedevice %%EndFeature %%EndSetup and the job printed fine if I edited the PostScript by hand and replaced them with %%BeginSetup %%IncludeFeature: *PageSize Letter %%EndSetup Comment 1 psfales 2002-09-24 23:35:22 UTC We saw this error also. It went away when we changed the default paper size in printer setup from "A4" to "US letter" Comment 2 philipp.lohmann 2002-11-12 13:52:05 UTC That actually is the right behaviour for a printer; on most printers you can configure that they adapt Letter to A4. That being said the PostScript produced will of course contain the page size of the document, which in this case seems to be Letter. Comment 3 philipp.lohmann 2002-11-12 15:51:01 UTC printing -> gsl Comment 4 philipp.lohmann 2002-11-12 15:51:25 UTC reassign Comment 5 philipp.lohmann 2002-11-12 15:52:15 UTC transition from printing to gsl Comment 6 michael.bemmer 2003-03-13 09:38:46 UTC As mentioned on the qa dev list on March 5th I will close all resolved