Postscript Error Handler Offending Command
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
Error Undefined Offending Command Stack
PostScript error occurs when the PostScript interpreter can't read the file's PostScript code. An error rangecheck offending command image error can also occur if the file's PostScript code exceeds one or more of the limits in the PostScript page
Offending Command Nostringval
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 error syntax error offending command stack 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 error undefined offending command stack xerox ]%% 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. Set Send PostScript Error Handler to Yes. If you do not see this option, your printer does not
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 this seems to be the most logical
Error Unregistered Offending Command Xshow
approach to me): 1. Try printing one more time Take a deep breath, look offending command g2ubegin through the window during a couple of seconds, check all the parameters in the Print windows and print again. Sometimes
Error Limitcheck Offending Command Save
a simple mistake like setting the orientation wrong causes errors. Have a colleague print the job. He or she may instantly see what you did wrong. Everybody makes a stupid mistake once in https://helpx.adobe.com/x-productkb/global/troubleshoot-postscript-errors.html 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 pieces Don't print large jobs with many pages or big images in one go. Print a couple of pages at the time or https://www.prepressure.com/postscript/troubleshooting/tips 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 error is somehow related to your document or the way it is created or printed. The reverse is not true: if a document prints on one device but not on another, this does not mean that that device is unreliable or faulty. The inconsistency may be
the links to other people's web pages are now broken. Why can't they stay still! Quick contents Introduction - what is an error? What is the error? Use an error http://boffin.quite.com/ps/errors.htm handler Still no error details? Things to try first Checking for corrupt graphics About us PostScript error details (alphabetical by error name) HP Laserjet Error codes (30 PS ERROR nn) Introduction - what is an error? This is intended for people who have to try and deal with PostScript errors. You don't need to know anything about PostScript, except that it is a language that gets sent to a printer. By 'errors' I mean specific errors detected by a offending command PostScript printer, that make it stop printing. This won't help you if the results are complete, but not what you expect. Good information on errors is hard to come by. The information here may help. It is long and detailed, and best used as a reference. Still, be prepared for a long struggle. Sometimes a file simply cannot be printed on a particular printer, particularly if it is old or has limited memory. (The amount of memory supplied offending command stack by default with many printers is not adequate for complex graphics or using many fonts). Some people will be dealing with PostScript files sent to them, that they must try to print; others will be generating the PostScript themselves. Not all of the advice in this document can be followed by both groups. Although I refer to 'printers' throughout, you might be using a printer, a printing or previewing package on a PC or workstation, or a high-end typesetter. This file is definitely not intended to help people writing their own PostScript. The discussion is confined to errors likely to be found when a program writes the PostScript on your behalf. If writing PostScript you will need a good manual, and lots of patience! A particularly unpleasant source of problems is bugs, either in the programs that write the PostScript, or in a few cases in the PostScript interpreter itself. As bugs can cause anything to happen, this document may not be much use either, but I have included information on some bugs that have been discovered in common software. Good luck! You may need it. What is the error? PostScript errors are reported in various ways. Before you can get anywhere with a problem you need to know the error name and offending command. For instance Error: limitcheck; Offendingcommand: clip Many people skim this information and say that they have received "an o