The customer reports: One of our clients sent in his postscript files, which he has been unable to convert with our product, using GhostScript. There are two files: Postscript.ps => This is the file that is failing to convert. IBM2090D.ps => This is the file that is run via Postscript command IN the postscript.ps file. If you look at the postscript.ps file, near the bottom of the document, you’ll notice the line: (D:/Autoweb/Reports/IBM2090D.ps) run You’ll need to modify this to match the full path of the IBM2090D.ps file, otherwise an invalidfileaccess error is thrown. However, when the path is set properly, and the postscript.ps file is run through ghostscript, the following error is written to the stdout log (attached): Unrecoverable error: invalidaccess in exitserver Looking at IBM2090D.ps, it appears to be a series of postscript commands, as opposed to printer output. We’re looking for more information as to what exactly GhostScript is erroring on during the conversion of postscript.ps.
Ghostscript follows the spec. exitserver operator calls startjob operator and throws an error if startjob fails. According to PLRM, startjob requires that the current level of save nesting is no deeper than it was at the time the current job started. postscript.ps creates new save levels. So startjob fails and exitserver throws an error. IBM2090D.ps also contains incorrect PS code /FontMatrix╒0.001 0 0 0.001 0 0σreadonly def
Not sure why Alex didn't close this as invalid, but I am closing this based on Alex's analysis.