To help streamline the identification and resolution of issues, it’s important to take some additional time to submit details. This page offers some tips on the type of information the developers will find useful.
- A general description of the problem including the exact text of any error messages that have appeared. Screen-shots can often help explain a problem.
- The operating system(s) used on both the server and workstation.
- The version of PaperCut. This information is located under the “About” section in the PaperCut Admin interface or Administration Console. Please submit the full number (i.e. PaperCut NG 12.2 (Build 17368)).
- Information about related components such as model and make of printer or other software you think is involved.
- If the problem relates to a current or past reported issue, please report your previous issue number (usually listed in the subject of the support email).
Print Tracking Related Problems
- Review the options presented in this KB article first.
- Please report the full model and make of printer. This will help the developers correlate problems with other reported issues for that make of printer.
- Any information on the printer driver such as type (i.e. the Postscript driver, PCL 6 driver, etc.). This information is often listed under:
- Right-click on the printer and select Properties…
- Click the Advanced Tab.
- If the problem relates to a page count or attribute detection issue (general print tracking), the developers may find a print-to-file useful.
Internet Charging/Quota Related Problems
- Please report the type and version of the proxy server.
- A sample log file or a section of the log file may also be useful.
Enabling Debug and Inspecting Logs
If you’re having issues with page counts not being correct, or jobs not coming out of the printer, then you should enable debug in the Print Provider, which is in charge of most printing functions. To do that, follow these steps.
For any other problems you’re seeing, ranging from authentication to options not working as intended, then you should enable debug in the Application Server by following these steps.
If you’re not sure which debug logs are required, it’s best to enable and collect both logs so we have as much information to help as possible.