Known issues with recent releases of PaperCut NG and PaperCut MF

KB Home   |   Known issues with recent releases of PaperCut NG and PaperCut MF

Get notified about new announcements on this page by following the RSS feed

This page lists known issues or bugs with the most recent releases of “ ”PaperCut NG″ and “ ”PaperCut MF″. The aim is to arm administrators with information about problems in the current release, and where possible mention workarounds or methods to mitigate the issues.

Known PaperCut MF issues relating to embedded MFD software, hardware and device integration are listed in a separate article.


Issue ID

Description

Reported in

Status

Resolved in

11381

Web Print sandbox mode: After one or more Web Print servers go offline, a single print PDF job with multiple copies will be incorrectly processed as multiple individual print jobs.
More info…

MF 17.1.2 (Build 40576)
NG 17.1.2 (Build 40577)

Open

MF 17.1.2 (Build 40576)
NG 17.1.2 (Build 40577)

11058

Google Cloud Print and Email to Print on Mac and Linux, will stop printing if the number of concurrently processed jobs exceeds 5.
Impact from: 9th of August, 2016
More info…

MF 16.2 (Build 37593)
NG 16.2 (Build 37604)

Resolved

Hotfix build from support

6206

TouchNet Payment Gateway will stop working when TLS 1.0 is disabled by TouchNet.
Impact from: 1st May, 2017
More info…

MF 15.1 and older
NG 15.1 and older

Resolved

MF 15.2 (Build 33661)
NG 15.2 (Build 33665)

10603

Compatibility issue with release 16.4 and an older version of the Standard or custom XML-RPC Release Station when releasing all jobs to a Find Me queue - jobs could be sent to the wrong printer.
First reported: Fri, January 6th 2017 More info…

MF 16.4 (Build 38868)
NG 16.4 (Build 38875)

Resolved

MF 16.4 (Build 39037)
NG 16.4 (Build 39038)

10017

Upgrade of Apache OGNL Java package results in errors affecting certain pages of application web interface.
First reported: Thursday, September 15th 2016 More info…

MF 16.3 (Build 37857)
NG 16.3 (Build 37858)

Resolved

MF 16.3 (Build 38110)
NG 16.3 (Build 38090)

9941

Web Print jobs being errantly cancelled due to timeout under certain conditions.
First reported: Thursday, September 15th 2016 More info…

MF 16.2 (Build 37593)
NG 16.2 (Build 37604)

Resolved

MF 16.3 (Build 38241)
NG 16.3 (Build 38242)

9922

Enabling PaperCut on Xerox Printers on Mac and Linux may cause the configuration script to exit with an error.
First reported: Wednesday, September 2nd 2016 More info…

MF 16.2 (Build 37799)
NG 16.2(Build 37798)

Resolved

MF 16.3 (Build 38126)
NG 16.3 (Build 38127)

9808

Publishing printers via Google Cloud Print causes an error to occur.
First reported: Friday, August 12th 2016 More info…

All versions of PaperCut

Resolved

v16.2 (Build 37798)

8810

On the print Release Station, some print queues were missing in certain configurations More info…

v16.0 (Build 34963)
v16.0 (Build 34947)

Resolved

v16.0 (Build 35131)

8815

In certain configurations when virtual and physical queues set, you may see a direct printing error. More info…

v16.0 (Build 34963)
v16.0 (Build 34947)

Resolved

v16.0 (Build 35131)

7553

When using some Pay stations to add funds, coins deposited may not increase the balance of a user. More info…

15.3 (Build 34079)

Resolved

15.3 (Build 34230)

7138

Site server sync fails after deleting a group. More info…

15.0 (Build 31930)

Resolved

16.0 (Build 34949)

4563

Devices using iOS 9 might be unable to print. More info…

All versions of PaperCut

Resolved

15.3 (Build 34078)

4562

15.1 database upgrade back-up stops under some circumstances, causing the upgrade to halt, preventing the PaperCut services from starting. More info…

15.1 (Build 33284)

Resolved

15.1 (Build 33291)

4561

Username normalisation on Novell fails in some environments More info…

15.0 (Build 31930)

Resolved

15.0 (Build 32334)

000008

Authentication is denied when running a Windows Server 2003 Domain Controller. More info…

15.0 (Build 31930)

Open

Workaround available

4489

Refund approvals and rejections fail from the admin interface. More info…

15.0 (Build 31930)

Resolved

15.0 (Build 32334)

Known issues with older releases of PaperCut NG and PaperCut MF (version 14 and earlier) are covered here


11381: Web Print sandbox mode: After one or more Web Print servers go offline, a single print PDF job with multiple copies will be incorrectly processed as multiple individual print jobs.

Before 17.1, for any file type, uploaded to web print server with intention to print multiple copies was used to processed as multiple individual jobs. After 17.1 this behavior was corrected with some limitations. For now we are still switching to old behavior when one or more web-print servers are offline and user tries to print a multi copy PDF job.



11058: Google Cloud Print (GCP) and Email to Print on Mac and Linux, will stop printing if the number of concurrently processed jobs exceeds 5.

As part of a change to reorganise the background Mac and Linux processes (in 16.2), the handling of the printing jobs from GCP and Email to Print was broken. If the number of concurrently processed print jobs exceeds the configuration parameter of SpooledJobsManagerJobProcessLimit (which defaults to 5), then the processing of the print jobs will be stalled and not be processed.

A hotfix build for Mac and Linux based off 17.0.7 can be provided from PaperCut support with the fix scheduled for 17.1.



6206: TouchNet Payment Gateway will stop working when TLS 1.0 is disabled by TouchNet.

From Monday 1st May, 2017, TLS1.0 will no longer be supported by the TouchNet Payment Gateway system. As a result, customers running PaperCut version 15.1 or older will no longer be able to accept TouchNet payments through PaperCut.

Upgrading to PaperCut 15.2 or above will resolve the issue, however if there’s some reason where a customer cannot upgrade to a later version, please contact Support for a manual workaround.



10603: When upgrading the Application Server to Version 16.4, print jobs could be released to the wrong printer.

As part of version 16.4, we’ve enhanced the experience across Release Stations to block users from releasing print jobs to a printer in error, and to provide them with a meaningful message to help them resolve the issue.

Although the update has been designed to offer backwards compatibility with Release Stations that were not updated, there is one scenario where this is not the case.

  • When releasing all jobs using the Standard Release Station (pc-release.exe) or a custom XML-RPC, in a Find Me environment.


10017: Upgrade of Apache OGNL Java package results in errors affecting certain pages of application web interface.

The initial release of version 16.3 for both PaperCut MF and PaperCut NG each incorporated an upgrade of the bundled Apache OGNL Java package. An unexpected side effect of this upgrade were Apache Tapestry page rendering issues. Thus far, the following pages of the interface have been confirmed to encounter issues:

  • The issue prevents the successful completion of transactions made via a number of different payment gateways, including Authorize.Net, PayPal Website Payments Standard, Moneris eSELECT Plus, and Realex Realauth Redirect.
  • Attempting to select a shared account when submitting a Web Print document via the User Web Interface will result in an error.
  • Accessing the mobile device variant of the User Web Interface will result in an error.

Other pages of the interface may also be affected. This Known Issue entry will be updated if and when these pages are identified.

A fix has been implemented, and is now available via a Maintenance Release of PaperCut NG 16.3 (Build 38090), and an updated Early Access release of PaperCut MF 16.3 (Build 38110).



9941: Web Print jobs being errantly cancelled due to timeout under certain conditions.

Our Web Print solution underwent a large architectural revision in version 16.2 to accommodate new Web Print scaling capabilitites. As part of these changes, the responsibility for creation of Web Print job status files was shifted to be distributed amongst all deployed Web Print Servers. Instead of status files being created up-front, they would now be generated at the moment a given Web Print Server selected a job for rendering.

Under certain workloads, Web Print jobs may not have been chosen by a Web Print Server for some time, remaining in the pending queue without an associated status file being created. However, it was discovered that the Application Server could misinterpret the prolonged absence of a status file as evidence that the actual job rendering had failed in error. When these jobs were subsequently picked up by a Web Print Server, they would be rendered successfully and submitted for printing via our Print Provider, but the Application Server would improperly instruct the Print Provider to cancel them, as they had been previously earmarked as errored.

These jobs would be logged as timed out in the Application Log:

The Web Print server took too long rendering document, cancelling job

… and similarly displayed as timed out in the user Web Print interface:

Error: Timed out

A fix has been implemented, and will be made available via forthcoming Maintenance Releases of PaperCut MF 16.3 and PaperCut NG 16.3. In the interim, a hotfix build is available upon request from our support team.



9922: Enabling PaperCut on Xerox Printers on Mac and Linux may cause the configuration script to exit with an error.

When running “Control Printer Monitoring.command” on Mac, for example, to enable a Xerox printer using a Xerox printer driver, it may fail with the error message of: Undefined subroutine &main::add_url_conformant_papercut_backend called at ./configure-cups line 213. A fixed version of the underlying “configure-cups” script can be obtained from support until the fix is released.

This could potentially affect any CUPS printer such as those used on Linux but only if it is using a custom CUPS filter program with the substring “Xerox” in its path name. This could also affect FujiXerox printers using such a CUPS filter with a FujiXerox printer driver.



9808: Publishing printers via Google Cloud Print causes an error to occur

When attempting to publish new printers to Google Cloud Print, the following error message is displayed in PaperCut’s admin UI: “An unknown error occurred while publishing this printer to Google Cloud Print. Please see the server.log file or contact support for assistance.”

This only affects publishing new printers via Google Cloud Print. Existing published printers will continue to work.

Our analysis has identified a recent change made on Google’s side which is causing this failure. We are actively working with Google to identify a path to resolve this, and will update this page as more information becomes available.

This has been resolved in v16.2 (Build 37798).



8810: On the print Release Station, some print queues were missing in certain configurations.

This has been resolved in v16.0 (Build 35131).



8815: In certain configurations when virtual and physical queues set, you may see a direct printing error.

An issue has been found when upgrading to version 16.0 (Build 34962 or Build 34949) and you have a virtual queue and physical queue configured to display jobs on a device, you may see a direct printing error when direct printing is not configured.

This has been resolved in v16.0 (Build 35131).



7553: When using Pay stations to add funds, coins deposited may not increase the balance of a user.

An issue has been found in version 15.3 (Build 34079) whereby a user depositing coins into a Pay Station in some configurations may not receive their funds in PaperCut. Development have found a fix for this issue and have created a custom build available for download.

NOTE: This does not affect Payment Gateways.

Please email support@papercut.com to obtain this build.



7138:Site server sync fails after deleting a group.

If you are using a Site Server, and you remove then re-add a group, any changes made to that group (for example, access to shared accounts or scan actions) are not synced to the Site Server.

To resolve this issue, you need to reset the Site server.

A fix for this bug was included in PaperCut MF 16.0 (Build 34949).



4563:Devices using iOS 9 might be unable to print.

iOS9 changes the way “i”devices talk on a network by preferring IPv6 communication over IPv4.

PaperCut uses IP addresses as an integral component of iOS printing. However, IPv6 addresses might not be recognized by PaperCut, which prevents PaperCut from being able to match a print job to a user.

For more information on how to resolve this issue, see the Knowledge Base article: iOS 9 Printing with IPv4 and IPv6 mixed networks.



4562: 15.1 database upgrade back-up fails under some circumstances, causing the upgrade to halt and preventing the PaperCut services from starting.)

PaperCut has noticed that some customers are facing an upgrade error with the PaperCut Application server not starting after the attempted upgrade. At this point no changes to the existing database have been made.

This appears to be caused by a failure in the back-up of the existing database before the upgrade continues. We are currently investigating the cause of the problem.

Workaround:- PaperCut recommends installing V15.0 (latest build) over the top of the stalled upgrade to repair the issue and continue with V15.



4561: Username normalisation on Novell fails in some environments 15.0 (Build 31930) (Resolved in 15.0 (Build 32334))

Customers may notice that there are new users (or users being denied access) that meet the following syntax: username.novell.domain

This is after upgrading to 15.0.

This issue has been identified and has been fixed in in 15.0 (Build 32334).



000008: Authentication is denied when running a Windows Server 2003 Domain Controller

PaperCut Support have seen a number of installations affected by authentication issues after installing Windows Update MS15-027 (3002657) whereby Active Directory denies access to users logging into PaperCut, giving the user an incorrect username/password error.

This Windows Update was rolled out to Server 2003, 2008 and 2012. However, this issue only occurs when using Windows 2003 domain controllers and PaperCut is hosted on a separate member server. If PaperCut is installed on the same server as your domain controller, this should not affect authentication.

This issue is also affecting other software using this authentication method. PaperCut is currently investigating this issue with Microsoft.

A temporary workaround is to uninstall this Update MS15?−027 from your Windows 2003 domain controllers, until Microsoft confirm that this issue has been fixed. We will also list any updates on this page when we hear back from Microsoft.



4489: Refund approvals and reject fail in version 15.0 (Build 31930) (Resolved in 15.0 (Build 32334))

Refund approvals/rejections fail when email notifications for refunds are enabled.

As an interim solution, please turn off “Email user when their request is processed” under Options → General → User Features → Allow users to request refunds.

This will avoid the unexpected error and will let the refunds through.

This issue has been fixed in 15.0 (Build 32334)


Keywords: problems, bugs, hotfixes, release notes

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on May 25, 2017, at 03:14 AM
Printable View   |   Article History   |   Edit Article