PaperCut Job Ticketing is a print room management solution that allows operators to manage, track, and process print jobs through a workflow-based interface. Job Ticketing runs as a standalone service and uses an embedded Apache Derby database to store job and order data locally.
If a technical issue arise debug logs are the primary tool for diagnosing the root cause. By default, Job Ticketing logs are already set to debug mode, meaning detailed diagnostic information is captured automatically without any additional configuration required.
The location of the Job Ticketing debug log is:
[app-path]\PaperCut MF\job-ticketing\log
(e.g. C:\Program Files\PaperCut MF\job-ticketing\log).
There will be a single log file named pc-job-ticketing.log. Upload a copy of this file to the PaperCut Support Team when requested.
When diagnosing Job Ticketing issues, it is highly recommended to enable PaperCut MF debug logging concurrently. Analyzing the PaperCut MF server logs alongside the Job Ticketing debug log allows us to trace API requests, verify authentication handshakes, and confirm whether an issue stems from the Job Ticketing service or the core PaperCut MF architecture. See our MF debug instructions here.
Your log files and other information you send to us will be treated in accordance with our privacy policy.
Comments