PaperCut has special debug options which cause PaperCut to produce a more detailed text log of activity. The log allows our Developers to inspect the internal workings of the PaperCut application and pinpoint the cause of problems. Enabling debug logging is only usually required of requested by the PaperCut Support Team.
The Web Print Server is the component in PaperCut that accepts user uploaded documents and prints them on behalf of the user.
To enable debug in the PaperCut Web Print Server:
1. Open the file in a text editor (for example, Notepad on Windows):
4. Restart Web Print according to your Operating System:
If running on Windows in Simple Mode:
Restart the PaperCut Web Print service in the Services.msc located in Control Panel → Administrative Tools → Services
If running on Windows in Sandbox Mode:
Restart the PaperCut Web Print GUI application (or restart the server).
If running on macOS in Simple Mode:
Restart the system running the PaperCut Application Server.
If running on Linux in Simple Mode:
Using Init scripts: Restart the PaperCut Web Print service via /etc/init.d/pc-web-print restart.
Using systemd: Restart the PaperCut Web Print service via sudo systemctl status pc-web-print.service.
5. Print a few test documents via the end-user Web Print interface to duplicate/demonstrate the issue you’re having.
6. Record the approximate time and date of the problem and the name of any printed documents (or the time you performed the test action). This will help the Support Team and Developers match up log entries with your test activity. Additional information such as what was observed or what was expected is always useful.
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.