I just joined, and I haven't found a DocuSP specific subforum, so forgive me if I have posted this in the wrong spot.

I was wondering if any of you who use BW and Color DocuSP's have encountered any jobs that fail to rip on one DocuSP, but if you send the job to another, or if you restart the first, it rips without issue.

Specifically, I have seen this occur when a cluster of several unrelated PDF jobs emit any of the following error messages over a short period of time:

PDF exception is: Wrong operand type.
PDF exception is: Expected a dict object.
PDFToPSGetErrorString returns unsubstituted string.
D0 not found, using Courier.

Have any of you have experienced this phenomena?

-Thanks
-Lou

Yes, we have had these error and this problem a few times. Usually a restart of the DocUsp will clear the problem but eventually comes back.. We run the "fsck" routine and we are good for a long time. Seems to be when faulted jobs or problem files have went through and ecumulate over time. This is not anything that we have considered a big problem but rather an occasional annoyance. Run the "fsck" routine and see if you go longer in between problems.

Dale Zahnke

Dale,

Thanks for the response!

We have been chasing this D0 issue for a while now, and have submitted it to Xerox support, but they are unable to reproduce this error and so are unable to resolve it.

The other 3 errors are not so much an issue, because when they occur, the job faults and produces no hardcopy whatsoever.

However, "D0", since it is detected as a font issue, and since our font management preferance is set to substitute fonts, it prints the entire job, and goes to completed.

This is unfortunate, since there really isn't much you can do after having printed 90 copies of a 300 page book to the stackers.

Xerox claims we are the only ones that have this issue.
Perhaps you could look into reporting your Phantom Errors to Xerox, {Especially the D0} to make them aware it happens to others also?

Hopefully some others here that experience this will also reply.


-Lou

This is scary workflow... We never substitute...

On the other issue I will see if I can do a little diggin for you..

Dale

Thanks!

And I agree, it is scary...