Postscript Error Undefined Offending Command Stack
Contents |
The error can be caused by numerous things such as missing dictionaries, imported graphics, data corruption, communication problems or missing PostScript header error undefined offending command stack xerox information. General solutions Some offending commands indicate a possible problem with error rangecheck offending command image the driver settings or printer support files. Updating drivers or switching to an alternative driver might solve error: syntax error offending command: stack the problem. You can also try to copy and paste all elements to a new file. If the document was converted from a previous version of an application, error undefined offending command new try printing again from that version. A strange word as an offending command: Sometimes a RIP generates an ‘undefined' PostScript error, with an offending command ‘bspt' or another randomly chosen kind of technical term like ‘fob' of ‘xtrfx'. Such errors indicate that the RIP tries to execute a command that has not been defined in the
Offending Command Nostringval
PostScript file. In a lot of cases, PostScript error "undefined" issues are caused by incorrect drivers: PostScript drivers that are corrupted or that are vendor-specific (eg you try printing to a Tectronix printer using an HP driver) PPDs that are too old or too new. PPDs that should be used for another device. Some applications that put themselves in-between your application and the RIP can also cause this kind of a problem: try printing without passing through a spooler or OPI-system. Use another imposition software or try to avoid using your trapping software. Sometimes the name of the offending command indicates which application is causing the problem. I remember a customer who by accident had deleted a number of PostScript files from his Preps folder. Subsequently Preps kept generating ‘undefined' errors because its printfiles lacked the necessary code. We found this rather quick because the offending command started with ‘SS' or so, something that we linked to ScenicSoft, the makers of Preps. Specific errors PostScript
of these temporary values on top of each other, a bit like the pile of paperwork you might have on your desk. When an error occurs, it is
Error Undefined Offending Command Get
useful to know what is on that stack since it might give offending command g2ubegin a programmer or support engineer an indication of what the interpreter was working on. That is why a PostScript error undefined offending command eexec error also contains a dump of the stack, as shown below: ERROR: undefinedresult OFFENDING COMMAND: itransform STACK: 2380.1 3366.1 In the above case the stack contains two numbers but it could just https://www.prepressure.com/postscript/troubleshooting/errors/undefined as well be PostScript commands. A PostScript error with offending command stack does not really exist. For some reason the offending command is simply not listed. Troubleshooting an error without knowing which command caused it, can be difficult. The error may be caused by a communication issue. There are fortunately specific cases for which a fix is available: Issues with the HP 4550 https://www.prepressure.com/postscript/troubleshooting/errors/stack and blank pages Every time a Windows machine prints to our HP 4550dn, it also prints two additional pages, one is blank, the second has the following PS error: "ERROR: undefined OFFENDING COMMAND: STACK:" It never lists the offending command or stack. This happens when you print binary jobs. The same issue is discussed in this thread. Either change the printer driver postscript settings to ASCII or, if you want binary for smaller print jobs when printing over the TCP/IP network to the Jetdirect's LPR BINPS queue, do then the following: When you print into a file (hint: change Port to File: ), you will see at the end of the print job something like %%EOF [emailprotected] EOJ %-12345X The cause is HP's adding to the PPD an for BINPS LPR an unnecessary TBCP switch. Here's the fragment in the PPD: *% ================================= *% Emulations and Protocols *% ================================= *Protocols: PJL TBCP *JCLBegin: "" *JCLToPSInterpreter: "@PJL ENTER LANGUAGE = POSTSCRIPT <0A>" *JCLEnd: "<1B>[emailprotected] EOJ <0A><1B>%-12345X" I changed the line above into *JCLEnd: "" and now I can create and print binary postscript in Windows 7 x64. Jus
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn http://graphicdesign.stackexchange.com/questions/15733/adobe-pdf-error-when-printing-whats-stack more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Graphic Design Questions Tags Users Badges Unanswered Ask Question _ Graphic Design Stack Exchange is a question and answer site for Graphic Design professionals, students, and enthusiasts. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers offending command are voted up and rise to the top Adobe PDF error when printing. What's STACK? up vote 3 down vote favorite I'm receiving a mysterious error when printing a .PDF. The exact message it prints out (wrong linebreaks) is: ERROR: undefinedresult OFFENDING COMMAND: itransform STACK: 2380.1 3366.1 I've already accepted the error and offending command specifications are too general to be of any help. What I'm wondering about error undefined offending is the STACK details. What is it? Could it give any help whatsoever? pdf printing share|improve this question asked Feb 6 '13 at 11:59 JackWilson 13816 The numbers under STACK are probably the location on the stack and an error code that was thrown when something wrong was caught. –OghmaOsiris Feb 6 '13 at 18:28 add a comment| 1 Answer 1 active oldest votes up vote 4 down vote accepted "STACK" is a programming term used to describe functions currently in use to accomplish a particular task. Postscript, the technology behind PDFs, is a programming language in its own right. But unless you are a programmer who understands Postscript, that will do little to help troubleshoot the error. I would say that something happened when the PDF was being created, some odd transformation that the Postscript driver had a hard time understanding, either because the complexity of the effect or there could have been a bug in the driver that created the PDF, that is in turn causing the printer driver to have a hard time. One workaround that sometimes works is, in Acrobat, go to the Advanced settings in the Print window and select "Print as image." Either way, you