ppr-list-digest volume 3, number 12, message 2

Note: please don't spam any of the e-mail addresses which you see here. Follow this link if you want some addresses to misuse.


From: David Chappell <David.Chappell@mail.trincoll.edu>
Date: Wed, 31 Jan 2001 09:55:17 -0500
Subject: Re: PPR: We got some issues...

Martin Whinnery wrote:

> We have a number of issues, the most pressing of which is that on a
> number of our non-postscript printers, large jobs are dying part way
> through. The first few pages print, then the job arrests.
> 
> I'm at a loss.
> 
> PS Our network clients are Win95 machines, and we use Adobe's PS driver.

This most common reason for a job to be arrested is a PostScript error.  
In such a case, PPR doesn't stop the job from printing, it simply 
reports that it has failed.  However, if you are using Ghostscript, 
there are a few additional possible causes.  For example, it is possible 
that a communications error is being reported by Ghostscript as a 
PostScript error.

If there was a PostScript error, it should show up in the job's log 
file.  If not, look in the printer's alerts file.  Here are sample commands:

$ ppop log bigprn-1004

$ ppop alerts bigprn