Diagnosing issues with Novell iPrint
Last modified on 15 August 2020 08:48 PM
PaperCut monitors printing on the Novell iPrint server by being configured as the accounting autoload command within iPrint Manager. This allows PaperCut to monitor and track all printing activity on the iPrint server.
If problems occur after enabling PaperCut on the Novell iPrint server (e.g. problems starting iPrint) some diagnosis will be required.
Verify that the autoload command is set to exactly
A common cause of problems are caused by iPrint not having permission to access important PaperCut files.
Verify that iprint has permissions as follows:
If there are problems starting the PaperCut autoload command, this will be reported in the ispmd.log located in:
Check this log for any obvious error messages relating to the
If the above does not help resolve the problem, report the issue to PaperCut support.
It’s generally advisable to first enable debug logging (see here), reproduce the problem and then send the following information to PaperCut support:
Important: The iPrint Manager needs to be restarted!
Zip and send the following log files:
Also send the following information:
If we need to further escalate this problem to Novell, then more information will be needed.
Please get the output of the iPrint Information gathering script from your iPrint Server. The script is available from: http://www.novell.com/communities/node/5705/iprint-information-gathering-tool
Turn on debug logging from the health monitor in the Printer Manager. Follow the menus:
Enable all of the options other than “errPause” and get the debug.log