![]() Use the method in the previous section to confirm that the job is getting tracked correctly - and that it’s showing up as the correct username.Ī useful trick here is to disable the Account Selection (see next section) temporarily while you’re confirming that job tracking is working correctly.Īnother trick is to check the Application Log, under Logs → Application Log. If you’re finding that one particular user is not getting an account popup, confirm that the user is printing as the username that you’re expecting. Head over to our article Print jobs not getting tracked for further troubleshooting.ĭoes the owner of the print job match the user signed into the client? If you don’t see the job recorded on either of those pages… then PaperCut doesn’t know about the print job. If you see the job on that page… good, skip to the next section. If the client isn’t connecting to the server a “tooltip” message will be displayed showing “Connecting…”. If the balance window isn’t displayed, then hover your mouse over the PaperCut client task-tray icon (Windows) or the PaperCut client menu bar icon (Mac). If the client is running and displaying the current balance of the logged in user then this is a good indication that the client is working correctly. If user client notifications are not being delivered there could be a number of reasons why, and this article discussed how to diagnose/resolve these problems. the workstation where the job was printed). PaperCut delivers these notifications by determining where the user printed the job from (i.e. Authenticate users through PaperCut (see the ‘Authentication’ section on this page).Display print job popups as directed by printer scripts (Advanced Scripting). ![]() Display print job popups for account selection or print confirmation.Deliver notifications/messages for denied print jobs, jobs held in the release station, etc.We imagine this could cause pains in slow networks or when clients running the Direct Print Monitor are unable to connect to the share.įor simplicity, if you require Print Archiving we recommend setting up a PaperCut Secondary Server. Each workstation would need to have the Print Provider running as a service account with permissions to write to the server share which hosts the Central Archive. Why is this the case? The Print Archiving feature relies on write files to a file share, which is not practical in large environments. The manual states here: “The following options are not available on a direct print queue: Google Cloud Print, Email to Print, Web Print (users may upload documents to print), Print Archiving”. ![]() When Direct Printing mode is enabled, the Print Provider ignores the Print Archiving settings and will not archive jobs. In the example below a Canon UFR driver results in the message “Unable to convert this page to an image due to a conversion error”.Īre these jobs being printed from a workstation with the Direct Print Monitor?īoth the PaperCut Secondary Server and the Direct Print Monitor utilize a service called the “Print Provider” to track jobs, but one big difference is that the Direct Print Monitor does not support Print Archiving. You can check for yourself what PDL is being used by a particular driver in PaperCut by looking at attributes column of the job log. This is due to UFR being a proprietary PDL and therefore cannot be interpreted by GhostTrap in order to generate the required image preview for recorded UFR spool files. 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.įor example, Canon UFR/UFR II is not a supported PDL for Print Archiving. If the PDL or Datatype is unknown or unsupported, the print job will pass through but will not be archived. PaperCut Print archiving supports the most common Page Description Languages (PDL) for printing spool files, including EMF, PCL5, PCL6, PDF, PostScript, and XPS, as documented on our Supported Printers page.
0 Comments
Leave a Reply. |