The config file is located here: [app-path]\providers\print\[platform]\print-provider.conf
Tip: If you’re running on Windows, and the changes you make to the config file are not being saved, you may need to run Notepad with Administrator privileges - Find ‘notepad’ in your Start menu, then right-click and select ‘Run as Administrator’. When notepad opens, use the ‘File → Open’ menus from that instance of notepad to open and edit the .conf file above, then save the file and re-open to confirm the connection information has saved correctly.
5. Restart the ‘PaperCut Print Provider’ service (Windows), or restart the secondary server to pick up any changes made above.
6. If you’re running the secondary server on Mac OS, confirm that the printer has been enabled for PaperCut monitoring by performing the steps to Add a new printer on a Mac
7. Check the Print Provider logs in [app-path]\providers\print\[platform]\print-provider.log to see if there are any errors listed, and to confirm that it is monitoring the local print queues.
Check the Admin Console:
8. Check that the Printer on the secondary server is appearing in the ‘Printers’ tab in the PaperCut administration console - otherwise, re-check the steps above, and then enable debug in the Print Provider and send the log files through to PaperCut Support, along with a full description of the issue, and any supporting information like screenshots / IP address of primary server / printer name of the printer not appearing and any other useful information.
9. Check that jobs sent to the print queues on the secondary server are appearing under Printers → [select secondary server print queue] → Job Log. If they are not, try pausing the print queue on the secondary server at the Operating System level, and send another job to the print queue. Confirm that the job shows up as paused in the print queue on the server. If not, check through the troubleshooting steps to determine why Jobs are not being tracked.
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.