PaperCut integrates with some MFP devices remotely using web services (e.g. like SOAP). In this case the PaperCut application server logs provide most of the information required to diagnose problems.
In some circumstances, it is necessary to also capture the contents of the communications between the device and PaperCut. This requires an additional configuration to the PaperCut logging and is described below.
NOTE: In the 11.6 release and higher, extra logging will be automatically enabled when the regular server debug log mode is enabled.
To obtain debug logs (PaperCut 11.6 or higher):
Follow the regular debug logging process:
To obtain the log files (PaperCut 11.5 or earlier):
First, enable the detailed logging of network communications, this is done as follows:
First enable “regular” debug logging mode in PaperCut
On the PaperCut
server, open or create the following file in a text editor:
Add the following on a single line:
Now reproduce the problem you are having. Also make note of important information (e.g. date/times, behaviour seen, usernames, etc). This helps us analyze the logs files later.
Zip up and send us all the logs as described here
: Check that your zip file contains the “server.log*” and the “service.log*” files. Then send these to us at support.
8. Once the additional logging is no longer required, disable debug logging by disabling the option in step #1 and removing the line added to the
Categories: Debugging, Troubleshooting
Keywords: soap, device, sharp, km, konica, debug logging, debug mode