I'm seeing instances of Error Code 29062 "timeout processing the PDF document" with certain PDF files (usually PDF files).
Typically, user has obtained or generated a PDF file, then uploaded the PDF file to Mobile Print. When releasing the document the Uniprint fails to print with no error message, however a few moments (or a few minutes) later the document shows in the queued jobs flagged as "Free Print". In Pharos Administrator Alerts the error is logged stating "timeout processing the PDF document". Despite the job now being shown as "Free Print", Uniprint is never able to print the document.
Trying to "tweak" the file (using Acrobat or other tools) doesn't help. Re-printing the file to a different PDF creator (like "Microsoft Print to PDF") successfully creates a new PDF file that will print through Mobile Print.
Who else is seeing this? Any suggestions?
I've already reviewed the driver settings for Mobile Print and even created new render print objects in the hope it might help (it didn't).
Thanks,
- Paul L.
Hi Paul,
Looks like you have a PDF that is not quite as simple as some can be,. PDF documents can be generated by many different applications and no two do the same thing out of the box, meaning some "flatten" those complex files when they are created and some don't unless specifically configured to do so.
The other part to the "Render" equation is the print driver used. I have seen some process those pesky PDF documents better/faster than others and some not so much, different drivers can produce different results. Often it is not a setting in the driver that you can tweak to make it work better, often it is switching from a PCL driver to a PS driver (or the other way around) for the Rendering of the file through a PDL that creates a print ready file for the device to chew on.
I have also seen small-ish (25MB files) with 200 or 300+ pages from a scanner device, meaning someone scanned a book to PDF and when the PDL gets it it takes minutes and days for it to chew on that file thus creating a large spool file in the Gigabytes. Most often those files take fuhever when printing through normal Windows methods, meaning direct TCP/IP ports to device. The Print Spooler processing it can be seen to take up to 15-20 minutes to simply complete the process so the file becomes something the device will print. It is those "scanned pages" that creates image files per page that causes the PDL (Print driver) to hunker down and get to work processing the image data, takes a while for some drivers and other not as much.
When you print to the print queue first, the file gets rendered at that time so when it gets "through the server" to the Secure Release Port Monitor it is already ready to go to the printer. No additional processing is needed other than the device has to chew on the file to put ink to paper. When doing it this way, the user is often going to have a few minutes as they finish something, go to device, login, see job and release it.
-Jeff