Print Ps Error
Contents |
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 error limitcheck offending command image interpreter can't read the file's PostScript code. An error can also occur if the file's postscript errors PostScript code exceeds one or more of the limits in the PostScript page description language. If your PostScript interpreter appears to process data error undefined offending command stack 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 error undefined offending command stack xerox 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
Error Syntax Error Offending Command Stack
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. Set Send PostScript Error Handler to Yes. If you do not see this option, your printer does not have a PostScript Error Handler. Note: If PostScript Options isn't visible, double-click Document OptionsIn Mac OS, configure the Apple LaserWriter 8 or Adobe PS printer driver to print the error message by doing one of the following:
the Basics section to determine exactly what PostScript error and offending command you got hit with. Then do one of the following (not necessarily in that order but
Error Syntax Error Offending Command Nostringval
this seems to be the most logical approach to me): 1. error unregistered offending command xshow Try printing one more time Take a deep breath, look through the window during a couple of seconds, error limitcheck offending command save check all the parameters in the Print windows and print again. Sometimes a simple mistake like setting the orientation wrong causes errors. Have a colleague print the job. He or https://helpx.adobe.com/x-productkb/global/troubleshoot-postscript-errors.html she may instantly see what you did wrong. Everybody makes a stupid mistake once in a while (I once spent 2 hours troubleshooting a ‘broken' Mac, only to find out the keyboard wasn't plugged in properly). This is definitely the first thing to try if no other documents or applications cause similar problems. 2. Cut the print job into smaller https://www.prepressure.com/postscript/troubleshooting/tips pieces Don't print large jobs with many pages or big images in one go. Print a couple of pages at the time or even one single page at the time. This makes it easier for both your computer and the RIP to process the file. Always try this approach if you have an older printer or RIP. 3. Search for solutions for your specific error Look up both the error and offending command in my database of PS errors and offending commands. This may give you a clue as to what to do next. Check out other sites as well by searching the web for pages about the specific PostScript error or offending command. Another alternative is to post your question on the b4print prepress forum. 4. Switch to another computer, app, driver,… Print the job from another computer, from another version or copy of the application used to create the file and try switching drivers. Always print the file to another PostScript device as well. If the same error occurs, you are at least sure the
The error can be caused by numerous things such as missing dictionaries, imported graphics, data corruption, communication problems or missing PostScript header information. General solutions Some offending commands indicate a possible https://www.prepressure.com/postscript/troubleshooting/errors/undefined problem with the driver settings or printer support files. Updating drivers or switching to an alternative driver might solve 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, try printing again from that version. A strange word as an offending command: Sometimes a RIP generates an offending command ‘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 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 offending command stack 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 error undefined offending command D On Macs running Leopard the above error can pop up with a wide range of printers including the HP LaserJet 1200 and HP PSC 1610xi. Installing and using a Gutenprint driver seems to resolve the problem. An alternative solution is to deactivate error reporting, as documented in this procedure on