“Help! We’re not able to see the Print Archiving Thumbnails in PaperCut. What should we check?”
Is Print Archiving enabled?
This feature is not enabled by default and requires the open source software program “Ghost Trap” installed on the Print server. First make sure Print Archiving is enabled by following these steps in our manual.
Does the user have permissions to view the archived print jobs?
PaperCut Print Archiving is a powerful feature that allows an administrator to view all documents printed through PaperCut. By default only the internal admin account in PaperCut has permissions to view archived print job. This means that even users given administrator access within the PaperCut Administration Console will not automatically have permissions to view archived print jobs.
If another specific user requires access to view archived jobs, the built in PaperCut administrator can assign these permissions by logging into the PaperCut Administration Console, and going to Options → Admin Rights. From there, choose the user you would like to give access to view archived jobs, and enable the Access archived jobs option under the List of Admin Rights.
Is there enough disk space left on the server?
Print archiving will stop if the server starts to run low on disk space. Check “Size Management” under the Print Archiving settings in PaperCut to adjust the threshold and make sure that your server has adequate disk space.
Are the print jobs a supported datatype?
PaperCut Print archiving supports the most common datatypes for printing spool files, including EMF, PCL5, PCL6, PDF, PostScript, and XPS. The datatype is displayed in the attributes column of the job log. If the datatype is unknown or unsupported, the print job will pass through but will not be archived. Usually printer manufactures make a PostScript or PCL driver available, and this is what we recommend using to ensure the highest degree of compatibility with PaperCut.
Are these print jobs from a secondary PaperCut Server?
There are some additional steps that sometimes get overlooked when a PaperCut Secondary Server is involved. Double check the steps on this page to confirm that you have set up the Central Archive and that the Print Provider service is configured correctly.
Make sure the Print Provider on the secondary server is upgraded to the same version as the PaperCut server.
Make sure the Print Provider service is started on the Secondary Server and is running as a service account that has read/write privileges to the Central Archive.
If this spontaneously stopped working recently, make sure the service account password has not expired or been changed.
Confirm that print-provider.conf file has been updated with the correct path for the Central Archive.
Still not working?
Let us know! We love chatting about what’s going on under the hood. Feel free to leave a comment below or visit our Support Portal for further assistance.
This release contains an updated Java version which no longer supports 32-bit workstations. If you have any 32-bit users launching the User Client or Release Station from a network share, see this Knowledge Base article for more information.