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.

For Device-Specific Known Issues:

Feature-Specific Known Issues:


Issue ID

Description

Reported in

Status

Resolved in

PD-533

Updating Print Deploy on macOS resets the default value of the UserIdentityMethod config key to auto.
More info…

1.1.904

Open

PC-16907

In extremely busy environments where certain changes to the print queues are being made during working hours, or jobs are being printed around the ~4am maintenance window, jobs could appear not to be released properly, or could land up being double-charged.
More info…

19.1.5

Open

Hot-fix in progress

PC-16823

Print Provider can crash when when documents are printed though Windows 10 Store apps like Edge when Print Archiving is enabled.
More info…

19.1.5

Open

Hotfix available

PD-493

Print Deploy Server Admin interface shows HTTP ERROR 500
More info…

v1.1.814

Resolved

19.2 GA or later
Print Deploy v1.1.904
or later

PC-16526

Client installations using pc-client-admin-deploy.msi fail
More info…

19.1.3

Open

PC-15072

Some USB print queues will be duplicated on macOS clients running the Direct Print Monitor
More info…

18.1.4

Workaround

PC-16680

Print Provider can fail when redirecting print jobs with Print Archiving enabled
More info…

19.1.4

Resolved

19.1.5

PC-16493

Scan to Cloud Storage can fail in rare circumstances, in certain environments - when the scan job file size is greater then 4MB.
More info…

19.0.7

Resolved

19.1.1

PC-16458

For customers that have enabled the LPD service on Windows Servers and are actively printing via it (e.g. Printing from UNIX systems). The username associated with the print job would incorrectly include the IP address of the client, and this may stop users from being able to print, or incorrectly log these jobs.
Workarounds are available in More info…

19.1.0

Resolved

19.1.2

PC-16414

Font color on the input fields on a Release Station gets customized to the font color of the non-input text
More info…

19.0.0

Resolved

19.1.3

ZD-918583

TouchNet Onecard VIP payment gateway users are experiencing problems because the vend-money-url and balance-inquiry-url values are incorrect
More info…

19.0.0

Resolved

Documentation
update
19.1.1

PC-16334

TouchNet Onecard VIP payment gateway users who are using track 2 card lookup are experiencing problems
More info…

19.0.0

Resolved

19.1.1

PC-16244

Server Performance issues and database timeouts may occur with SQL server, when using the default database connection example.
More info…

19.0.0

Resolved

19.1.1

PC-15889

When using Web Print and you’re printing a PDF and you don’t have Adobe Reader installed (or you’re using xpdf in the Web Print options), the Web Print job will fail with a message ‘Failed: Timed out’.
More info…

19.0.4

Resolved

TBD

PC-15713

When using the ‘pc-client-local-cache.exe’ method of running the user client, the client files may be copied to the client workstation again, even if the client is actually up to date with the latest version - sometimes resulting in a slower user client launch time.
More info…

19.0.0

Resolved

19.0.4

PC-15736

The App Server can experience higher than usual CPU usage in scenarios where there are a large number of users running the PaperCut User Client software, and the balance window is hidden in some way.
More info…

19.0.0

Resolved

19.0.3

ACA-803

Activating Scan to Cloud shows a warning ‘No internet connection or other connection issues’, only if you installed 18.x and did not activate Scan to Cloud while on 18.x.
More info…

19.0.0

Resolved

19.0.3

PC-15711

If you’re using the client-local-install.exe (only), and you’re upgrading the client from 18.x or before, to version 19, the client doesn’t run. Fresh installs of the client, and old versions of the client currently installed will not experience any issues.
More info…

19.0.0

Open

Workaround

PC-15712

When re-configuring Active Directory syncing, the UI won’t allow you to preserve “Do Not Sync” for the primary number field unless the secondary number field is also set to “Do Not Sync”.
More info…

19.0.0

Resolved

19.0.3

PC-15617

Message: ‘cups-api-helper is not optimised for your Mac and needs to be updated’ appears on macOS if you’ve installed the Print Monitor (Secondary Server, Direct Print Monitor, Site Server).

macOS
10.13.4

Resolved

19.0.3
More info

PC-15699

When using Integrated Scanning and using OCR and using the ‘Prompt for more pages’ feature, you’ll receive a scanned file (e.g. PDF) for each page of the document rather than one file containing all pages.
More info…

19.0.0

Resolved

19.0.3

PC-15674

Important: When upgrading to version 19 from previous versions, held jobs printed prior to the upgrade will not be available to release once the upgrade is complete.
More info…

19.0.1

Resolved

19.0.2

ACA-548

OCR will fail to detect text when the input image is not in its natural orientation. This issue affects both cloud and on-premise OCR.

18.3

Resolved

19.0.4

PC-15524

PaperCut Print Provider crashes when certain PCL5 drivers are used.
More info…

18.3.6

Resolved

18.3.8

PC-15206

5 second delay on Server-Command.exe/Payment Gateway interfaces
More info…

18.3

Resolved

18.3.7

PC-14851

Jobs are refunded when Hardware Page Checks are enabled and conversions or watermarks are also enabled.
More info…

18.2.5

Resolved

18.3.7

PC-15220

Publishing a printer through Google Cloud Print (GCP) results in an error:
An error has occurred while processing your request, please check the logs
More info…

From
Jan 23
2019

Resolved

Jan 26
2019

PC-15179

Authorize.Net is phasing out MD5 based transHash support
More info…

From
Jan 31
2019

Resolved

18.3.7
Action required

PC-14841

Email to Print doesn’t respect the default driver settings configured on the queue (e.g. duplex etc)
More info…

18.2.3

Resolved

18.3.3

PC-15040

Some print scripts do not work after upgrading to 18.3
More info…

18.3.2

Resolved

19.0.0

PC-14874

If you’re on v18.2.6 with a Server running MacOS/Linux, jobs won’t print with Google Cloud Print and Email to Print
More info…

18.2.6

Resolved

18.3.2

PC-14600

Canon Pro devices not working well on High Sierra.
More info…

All

Resolved

18.3.2

PC-14580

The PayPal payment gateway now requires using HTTPS for the IPN URL.
More info…

All

Resolved

Config change
More info…

PC-14526

In PaperCut version 18.2.4 the Print Provider may crash when Hardware Page Checks are enabled.
More info…

18.2.4

Resolved

18.2.5

PC-14525

Issue with the built-in database driver causing excessively long connection times to SQL 2016.
More info…

18.1

Resolved

19.0.0
More info…

PC-14440

PaperCut NG/MF 18.2.3 for iPrint does not work on anything other than OES 2018.
More info…

18.2.3

Resolved

18.2.6

PC-14214
(was 13625)

Value of Regex is not saved when syncing primary/secondary card numbers from the sync source (i.e. AD, LDAP) under Options → User/Group sync.
More info…

18.0.5

Resolved

19.0.0

PC-13923

When trying to access the PaperCut Admin console, under certain circumstances the following message is shown “An error occurred starting the PaperCut MF application server service “.
More info…

N/A

Resolved

18.3.6

PC-14295

additional-groups.txt file no longer includes internal users when performing sync.
More info…

18.2.0

Resolved

18.2.4

PC-14220

Errant warning displayed upon first load of the Bulk User Operations page of Admin web interface
More info…

18.1.4

Resolved

18.2.3

PC-14161

The pay and release station (where coin boxes are attached to a release station) will stop working when upgrading to Papercut MF or PaperCut NG 18.2.0 or above. This issue may also affect some a rarely used standalone payment or hardware integrations.
More info…

MF 18.2.0

Resolved

18.2.1

PC-14091

Shared Account selection via Mobile web client not working as expected in some environments
More info…

14.x or earlier

Workaround

PC-13934

An access denied message appears when switching from Job Ticketing to the PaperCut MF Admin web interface
More info…

18.2

Resolved

18.2.3

BA-1863

If the Job Ticketing version is older than November 2018 and auto updates have been turned off, upgrading to the latest version of Job Ticketing will fail once auto-update is enabled.
More info…

Nov 2018

Resolved

18.3

PC-13687

The PaperCut Admin interface and some device screens may not show specific language translations correctly
More info…

18.1.1

Resolved

18.1.2

PC-13542

Google Cloud Print status stuck as “Initializing”
More info…

18.0.4

Resolved

18.1.3

PC-13437

User re-prompt to enter their Account Selection/Comment/Invoice details again for held jobs after upgrading to 18.0.4 or higher
More info…

18.0.4

Open

PC-13311

Users color selection ignored when printing from the Chrome browser on Windows
More info…

Chrome browser
60.0.3112.78
to 67.0.3396.99

Resolved

Chrome
67.0.3396.99

PC-13231

Integrated Scanning “Scan to Folder” and “Scan to Custom Email” Scan Actions fail to deliver document if user’s email address not populated on Application Server
More info…

MF 18.0.2
(Build 42955)

Resolved

18.0.3

PC-13037

A rare issue on older devices can cause a connection failure with the Application Server.
More info…

All versions

Resolved

18.0.4

PC-12987

Jobs released from the queue are not being printed then showing back up in the queue on hold.
More info…

17.3.4

Resolved

18.0.5

PC-13066

Orphaned print jobs can cause jobs in the print release queue to be hidden for all users.
More info…

18.0

Resolved

18.0.5

PC-12935

On MacOS High Sierra only (10.13), when you run the Control Printer Monitoring.command, PaperCut does not track the print queues
More info…

All versions

Resolved

17.4.4

PC-12243

PaperCut NG and MF is not yet compatible with PostgreSQL version 10 or later.

All versions

Resolved

17.4.3

PC-12505

We have had some customers experience issues relating to incorrect paper size when printing from Apple’s Pages, Keynote, and Numbers apps on iOS devices. This seems to be affecting the latest update of the apps, v3.3. If you are experiencing issues with incorrect paper size when printing from Apple’s Pages, Keynote, and Numbers v3.3, can you please contact support via http://support.papercut.com
More info…

All versions

Open

PC-12292

PaperCut 17.3 has introduced a security enhancement to improve the coverage of HTTP header origin checks, in line with OWASP recommendations. However, in some cases, attempting to log into the Admin or User web interface after upgrading to 17.3, sometimes produces a CSRF validation error message. This can be resolved by following these additional actions.

MF 17.3.2
(Build 41733)
NG 17.3.2
(Build 41734)

Resolved

MF 17.3.4
(Build 41947)
NG 17.3.4
(Build 41948)

PC-12290

There has been an issue reported where the Application Server is failing to read the service.conf file. This means custom memory allocation settings may be ignored and the Application Server will run with a default memory allocation (1/4 of the system memory).
More info…

MF 17.3.2
(Build 41733)
NG 17.3.2
(Build 41734)

Resolved

MF 17.3.3
(Build 41828)
NG 17.3.3
(Build 41829)

PC-12181

Slow response time on card swipes when using RFIDeas 241 Client Mode.
More info…

All versions
(since July 2017)

Resolved

RFIDeas
newest firmware

PC-12173

You may receive an error message “Unknown Error” when accessing “Jobs Pending Release” screen in the PaperCut Admin Web UI.
More info…

MF 17.2.4
(Build 41500)
NG 17.2.4
(Build 41501)

Resolved

MF 17.3.3 (
Build 41828)
NG 17.3.3
(Build 41829)

PC-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)

Resolved

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

PC-10959

An issue preventing Admins from accessing the configuration pages of Value Loaders and Kiosks.
More info…

MF 17.0.2

Resolved

17.0.4

Note:
Known issues with older releases of PaperCut NG and PaperCut MF (v16 and earlier) are covered here


Device Specific Known Issues

For issues specific to given devices see the following links:




PD-533: Updating Print Deploy on macOS resets the default value of the UserIdentityMethod config key to auto.

By default this value is set as auto, however you may have changed this to trust or prompt.

Updating the config key followed by restarting the Print Deploy service will fix this issue. More info can be found here.

This issue affects all current Print Deploy users.



PC-16907: In extremely busy environments where certain changes to the print queues are being made during working hours, or jobs are being printed around the ~4am maintenance window, jobs could appear not to be released properly, or could land up being double-charged.

Under certain circumstances in extremely busy environments this could happen when:

  1. User sends a print job to a hold/release queue.
  2. Print Administrator makes a change to the print queues on that print server, e.g. removing a print queue, adding a print queue or renaming a print queue - or the ~4am Print Provider daily maintenance refresh happens. (Note that making property changes like driver defaults is not included in this list - only major changes like add printer / remove printer / rename printer).
  3. User then releases the job.

Note: if there are no changes being made by the print server administrator, and if jobs aren’t happening around the 4am maintenance window, then this issue will not be seen.

If the scenario above was experienced, the behavior seen would be:

  • The user walks up to a release station and releases the job. It would look as though the job didn’t successfully release to the printer, and the job would not actually print.
  • If the user then went back to the release station and released the job again (it could be displayed again), the job would successfully release, but the user would then be charged twice for the job.

The likelihood of this happening is even less if a find-me queue is in use, and the job is redirected to a different target queue on release.

We’re actively working on a hot fix for this issue, and we’re looking to include this in the next available public release.



PC-16823: Print Provider can crash when when documents are printed though Windows 10 Store apps like Edge when Print Archiving is enabled.

Some customers may report that users will not be able to see their print jobs are available for release due to a Print Provider crash with this issue. PaperCut Sys Admins may see a similar message to this in the logs: Print Provider “printsrv01|192.0.0.1”: Print job “Document-1.pdf” printed by “user1” is offline and has been temporarily hidden from the Print Release screen.

Through our analysis we have determined that the Print Provider may stop when documents are printed using Windows 10 store apps to a shared print queue on a Windows Print Server with Print Archiving enabled on the same print queue. Workarounds to this include disabling Print Archiving on the relevant print queues, correcting the use of XPS2GDI print jobs to the PaperCut Print Server or have Windows 10 devices print through Mobility Print.

This issue seems to only affect PaperCut 19.1.5. Please reach out to the PaperCut Support Team for the available hotfix.




PD-493: Print Deploy Server Admin interface shows HTTP ERROR 500

Several customers have reported that the Admin Console for Print Deploy displays a HTTP ERROR 500 along with a timeout error.

This error is difficult to reproduce and only happens in unreliable network environments where connections are terminated improperly.

This issues has been resolved in PaperCut NG/MF 19.2 GA and Print Deploy version 1.1.904, otherwise Restarting the PaperCut Application Server will resolve this issue temporarily.

Example partial error message:

HTTP ERROR 500
Problem accessing /print-deploy/admin/. Reason:

Server Error
Caused by:
java.net.SocketTimeoutException: timeout



PC-16526: Some Client installations using pc-client-admin-deploy.msi may fail.

Several customers have reported that after deploying the pc-client-admin-deploy.msi package the client crashes soon after launching. The speed of the crash prevents logs from being obtained.

This is more likely to affect customers running PaperCut MF 19.0.5 and newer.

It’s possible to prevent this from happening by deploying a different PaperCut client by following the links below. Install the User Client on Windows

Alternately you may be able to resolve the issue by manually replacing the following files inside the Client installation directory.

Steps:

  1. Download the latest Microsoft Visual C++ Redistributable
  2. On the affected client computer, browse to the PaperCut MF Client folder
  3. Replace msvcp140.dll and vcruntime140.dll with those downloaded from the Microsoft Visual C++ Redistributable
  4. Run the Client



PC-15072: Some USB print queues will be duplicated on macOS clients running the Direct Print Monitor

Several customers have reported that after installing the Direct Print Monitor on macOS computers, USB print queues will be recreated in Printers & Scanners every time the printer is restarted or reconnected.

This is more likely to affect customers running PaperCut MF 18.1.4 and newer, because in that version we changed the default behavior for Mac and Linux clients so that printers will automatically be imported.

It’s possible to prevent this from happening by disabling the printer auto-import feature.

Steps:

  1. On the affected macOS computer, browse to the PaperCut application folder and run the executable Control Printer Monitoring.command.
  2. Enter the Mac’s admin password in the Terminal window when prompted.
  3. Type “yes” and press the enter key to disable the auto-import feature. This will prevent the print queues from being duplicated accidentally.
  4. Run the Control Printer Monitoring.command file again.
  5. Follow the prompts to disable the print queues you don’t want monitored, and enable monitoring for the printers you do want tracked.
  6. Lastly, open System Preferences and choose Printer & Scanners. Select any duplicated printers and click the minus sign to remove them.



PC-16680: Print Provider can fail when redirecting print jobs with Print Archiving enabled

The PaperCut Print Provider service can redirect print jobs from one print queue to another, facilitating workflows such as Find Me Printing. It was found that a change introduced in version 19.1.4 could cause the Print Provider service to fail if Print Archiving was enabled on a print queue and a print job was redirected to it.

A fix for this issue has been included in version 19.1.5.




PC-16493: Scan to Cloud Storage can fail in rare circumstances, in certain environments - when the scan job file size is greater then 4MB.

When scan files from PaperCut Integrated Scanning are greater than 4MB, the file transfer consists of multiple packet uploads. In some rare circumstances with certain environments using the PaperCut Scan to Cloud Storage feature, the uploads to the cloud can intermittently fail.

Due to libraries updated with the 19.1 release, customers at those locations are reporting that the uploads to the cloud are now more reliable.

This has now been resolved in 19.1.1 (but 19.1.2 is highly recommended).



PC-16458: For customers who have enabled the LPD Service and are actively using it, and are using PaperCut build 19.1.0 or later, the IP address of the job gets included in the PaperCut username.

This can cause issues if you’re expecting to track jobs based on the username e.g. ‘tim’ - rather than the username and the IP address as it appears in the print queue e.g. ‘tim (10.1.10.13)’.

If you are using the PaperCut LPD Service you can workaround this issue by:

  1. Make sure that you’re using the latest LPD Service version, by running the installer in [app-path]\providers\lpd\win\pc-lpd-installer.exe
  2. Edit the LPD Service config file: [app-path]\PaperCut LPD Service\pc-lpd.config
  3. Add the line RemoveHostAddress = true (and save the config file)
  4. Restart the LPD Service

This will remove the IP address from the username - both in the Print Queue view and also from the PaperCut logs - so that tracking against the usual username e.g. ‘tim’ will continue. This method strips out the IP address at the LPD Service level.

If you’re using the Microsoft LPD Service - or if you still want the IP address to show in the username at the OS level for other reasons (other integrations or workflows), there is also an alternative workaround:

  1. Log into the PaperCut admin interface
  2. Go to the Options tab
  3. Go to the Config Editor (Advanced) action
  4. Search for the system.normalize-network-username-regex config key
  5. Enter a value of ^([^\s]+) and then click ‘update’

This second workaround is taken from Example 5 on the Normalizing Usernames KB article.

This will mean that the username in the print queue is untouched - however when PaperCut receives the job for tracking, it strips out the IP address at the App Server level.

Update: Please note that this has now been resolved in the 19.1.2 release.



PC-16414: Font color on the input fields on a Release Station gets customized to the font color of the non-input text

When customising the Release Station software (e.g. using the second Step 1 from the Installing the Release Station article), if you’re using the font-color customization to change the font color of text, you’ll find that prior to 19.x, this did not impact the input fields (they would remain black text on the white input box background).

However since 19.0, that customization now impacts the input field text - for example if you’re running 19.0.1 and you have customized the release station to use grey text, you’ll find that the input box (e.g. username and password) text will also be grey.

Update: this has now been fixed in the 19.1.3 release.



ZD-918583: TouchNet OneCard VIP payment gateway users are experiencing problems because the vend-money-url and balance-inquiry-url values are incorrect .


We have seen several users who have not configured the above URL settings in the TouchNet OneCard properties file correctly.

Make sure your vend-money-url setting ends with /transactions/onecard/vendmoney/process and balance-inquiry-url setting ends with /transactions/onecard/inquiry/process.

For example:

touchnet-onecard.vend-money-url=https://www.test.com/api/transactions/onecard/vendmoney/process

touchnet-onecard.balance-inquiry-url=https://www.test.com/api/transactions/onecard/inquiry/process

Then restart your PaperCut MF/NG server.

Update: this has now been clarified within the config files included with the latest version of the payment gateway.




PC-16334: TouchNet OneCard VIP payment gateway users who are using track 2 card lookup are experiencing problems


If your TouchNet OneCard VIP gateway is configured for account types of track2Data then you will experience balance and transaction failures on those accounts.

Note that this has now been resolved in 19.1.1




PC-16244: Server Performance issues and database timeouts may occur with SQL server when using the default database connection example.


We have seen several users with external databases housed on SQL servers where connection timeouts and rollback issues are causing server stability and performance issues. This behaviour stems from a difference between the previous SQL database driver (used in V18 and earlier) and the current driver (used in V19 onwards) We’ve corrected this in an upcoming version of PaperCut, however there is a simple workaround that can be implemented in conjunction with a PaperCut server restart.

To implement the workaround please add the following to the end of your existing SQL connection statement

;socketTimeout=600000

This has now also been resolved in 19.1.1.




PC-15889: When using Web Print and you’re printing a PDF and you don’t have Adobe Reader installed (or you’re using xpdf in the Web Print options), the Web Print job will fail with a message ‘Failed: Timed out’.

Update: this has now been resolved with the public 19.0.5 release.




PC-15713: When using the ‘pc-client-local-cache.exe’ method of running the user client, the client files may be copied to the client workstation again, even if the client is actually up to date with the latest version - sometimes resulting in a slower user client launch time.


We have seen instances where the client files are re-copied from the server, to the local workstation C:\Cache directory, even if the cached location is up to date. On slow networks this can result in a slower startup time for the user client.

In some cases with shared workstations (multi-user switching), users may see the error ‘Unable to create the local cache in ‘C:\Cache’.

We’re hoping to resolve this in the next release.

Update: there is now a hot fix available for this - please contact us if you need this!

Update: this has now been resolved in the public 19.0.4 release.




PC-15736: The App Server can experience higher than usual CPU usage in scenarios where there are a large number of users running the PaperCut User Client software, and the balance window is hidden in some way.


This could be through setting the config key client.config.show-balance to ‘N’ (on the server side) or using the config properties hide-balance=Y config option, or using the —hide-balance command line option when starting the client.

This has been fixed in 19.0.3.




ACA-803: Activating Scan to Cloud shows a warning ‘No internet connection or other connection issues’, only if you installed 18.x and didn’t activate Scan to Cloud while on 18.x.

If you activated Scan to Cloud while on 18.x, then Scan to Cloud will work as expected. Likewise if you installed version 19.0 or later and you are activating Scan to Cloud for the first time, everything will work ok.

This has been fixed in 19.0.3.

A workaround is to head into the config editor, and set system.scan.cloud.api-url to https://scan.cloud.papercut.com.

If you’re wondering what Scan to Cloud is - check out Scan to Cloud Storage.




PC-15711: If you’re using the client-local-install.exe, and you’re upgrading the client from 18.x or before, to version 19, the client will not run. Fresh installs of the client, and old versions of the client currently installed will not experience any issues.

The other versions of the client (including MSI, pc-client.exe and pc-client-local-cache.exe) are not impacted by this.

For users experiencing this, the behavior of client-local-install.exe will be that installation will work fine, however then when running the User Client, it won’t run at all - no error.

The workaround currently is to either not upgrade using the client-local-install.exe (old versions of the client work perfectly ok with later versions of the App Server), or uninstall the client from the local workstation, prior to using the client-local-install.exe to install the updated client.

We are hoping to have this resolved in the next upcoming release.




PC-15712: When re-configuring Active Directory syncing, the UI won’t allow you to preserve “Do Not Sync” for the primary number field unless the secondary number field is also set to “Do Not Sync”.

On saving, the ‘primary number’ source is updated to match the ‘secondary number’ source.

Note that this will not impact the sync behavior on upgrade unless someone uses the UI to update either the ‘primary number’ or ‘secondary number’ source configuration.

This has been resolved in 19.0.3.




PC-15699: When using Integrated Scanning and using OCR and using the ‘Prompt for more pages’ feature, you’ll receive a scanned file (e.g. PDF) for each page of the document rather than one file containing all pages.

The ‘prompt for more pages’ option allows you to scan multiple pages in, and have them all bundled as one PDF. For example if you don’t have a document feeder, or if you have a particularly large document, you can scan a number of pages through separately, and using ‘prompt for more pages’ you’ll receive 1 PDF with the entire document.

This has been fixed in 19.0.3.

Please note that if you’re not using OCR, then you’ll not see this issue happening.




PC-15674: When upgrading to version 19 from previous versions, held jobs printed prior to the upgrade will not be available to release once the upgrade is complete.

Instead, users will see the message “account needed”, displayed in the “Jobs Pending Release” page, or on the device or release station, when trying to release their print jobs. All jobs printed to hold/release queues subsequently (i.e. after the upgrade to version 19) will behave as normal, and will be available for release by the users.

This will only impact those jobs that were printed prior to the upgrade.

If you find yourself in this situation, the workarounds available are:

Clear your hold/release queues

We strongly advise to do the version 19 upgrade out of hours, and to ensure that Hold/Release Queues are cleared down pre-upgrade where possible.

If possible, clear out your hold/release queues - so that the pre-upgrade jobs are removed, and don’t cause confusion for users. Unfortunately this does have the obvious side-effect that users will have to re-print their jobs if they still need them.

Remove the job-status data from the Application Server

This issue has come about due to changes and improvements in the ability to select accounts to charge jobs to, at release time. See Assigning accounts at the MFD if you’re interested in this feature. To handle this, the status information about jobs being held has been changed.

One way to get around this is to:

  1. Shut down the App Server
  2. Remove the following files from [app-path]/server/data/internal/state/systemstate/
    held-jobs.curr.ser
    user-client-data.curr.ser
  3. Start the PaperCut Application Server service

This will have the positive effect that the old status information will be removed, and the App Server will regenerate status information for any held jobs in the system. However there are also side effects:

  • Jobs that were printed by users who have their account selection set to ‘Automatically Charge to Personal Account’ or ‘Automatically Charge to a Single Shared Account’, will then be available for release for those users. This is the good news.
  • The bad news is that jobs that were printed by users who have their account selection set to e.g. ‘Show Standard Account Selection’ (i.e. the user has to select which account to use) will need to re-select the account required. If your users have the ability to assign accounts at the MFD, then they can do this - otherwise they will have to return to their computer, make sure that the PaperCut User Client is running, and re-select the required account.

If in doubt, reach out to us to chat!




PC-15524: Print Provider crashes when certain PCL5 drivers are used.

Starting with PaperCut 18.3.6 the Print Provider may crash during page analysis when certain PCL5 drivers are used. When this occurs, job will not be tracked or held and the Print Provider will need to be restarted.

Update: This has now been resolved in the 18.3.8 release.




PC-15206: 5 second delay on Server-Command.exe/Payment Gateway interfaces

If a environment uses Server-Command.exe (often used by our Payment Gateways via our Web Services API), the executable will not shut down until after the command has gotten its result. It will instead hang for roughly 5 seconds before finally shutting down.

While this can be annoying for System Administrator that are using the command line, since they cannot enter another command within those 5 seconds, the main problem comes from external devices that use the server-command to function, as it can slow them down a lot (e.g. getting a users balance suddenly takes 5 more seconds).

PaperCut end-users can see this as a perceived network delay when authenticating at a Payment Gateway Cash Loader for instance.

Update: This has now been resolved with version 18.3.7



PC-14851: PaperCut version 18.2.5 can mark jobs as refunded when Hardware Page Checks are enabled when conversions or watermarks are also enabled.

A workaround is covered below: Please leave the hardware checks feature enabled but edit the print-provider.conf file following the steps below.

  1. On the PaperCut server, browse to [Application-Directory]\Providers\print\win\.
  2. Open the file print-provider.conf with a text editing program.
  3. Add the line IsPrintingBasedOnPortMonitor=off to the file and save.
  4. Open Services.msc, find the service “PaperCut Print Provider” and choose Restart for the new configuration to take effect.

Other alternatives would be to disable “Convert to Grayscale” and “Convert to Duplex” settings on each printer’s Filters & Restrictions and disable “Apply watermarks / digital signature to all pages” on each printer’s Summary page.

Update: This has now been resolved in 18.3.7



PC-15220: Publishing a printer through Google Cloud Print (GCP) results in an error: An error has occurred while processing your request, please check the logs

Please note that this does not impact any GCP printers that have already been published. Printing should continue without issues.

Early indications are that something has changed on the Google Cloud side of things, which means that when the PaperCut App Server is asking to publish a printer it gets a reply from Google with a malformed URL. This results in the printer failing to publish.

Update: Google reached out to us on the 26th Jan to confirm that they’ve fixed the malformed URL response. There are no updates needed on the PaperCut side. Testing has confirmed that publishing printers now works as expected.



PC-15179: Authorize.Net is phasing out MD5 based transHash

Authorize.Net has announced they are phasing out the MD5 based transHash support - which PaperCut uses when communicating with the Authorize.Net Payment Gateway.

You may receive an email from them containing the below information:

Authorize.Net is phasing out the MD5 based transHash element in favor of the SHA-512 based transHashSHA2. The setting in the Merchant Interface which controls the MD5 Hash option will be removed by the end of January 2019, and the transHash element will stop returning values from March 14,2019 according to their support site above.

Their support article with more information is over on the Authorize.net Support Site

PaperCut will support the new SHA-512 signature with the updated Payment Gateway module. This build is for new SHA2 key hashing changes for Authorize.Net Payment gateway. Though this build will support both SHA2 and existing MD5 keys, we highly recommend that you obtain the new ‘Signature Key’ from the Authorize.Net Merchant Interface, as Authorize.Net will stop processing MD5 hash key by March 14,2019 according to their support site above.

Please ensure that you switch to the new SHA-512 signature prior to this date

I currently use the Authorize.net gateway. What do I need to do?

Upgrade the PaperCut Payment Gateway Module:

  1. Head over to the Payment Gateway Install page, and download the latest Payment Gateway installer for your OS.
  2. Install the new Payment Gateway module on your PaperCut App Server (as documented in the link above).

Next, generate the new Signature key :

  1. Log into the Merchant Interface at https://account.authorize.net.
  2. Click Account from the main toolbar.
  3. Click Settings in the main left-side menu.
  4. Click API Credentials & Keys.
  5. Select New Signature Key*
  6. Click Submit to continue.
  7. Request and enter PIN for verification.
  8. Your new Signature Key is displayed. This Signature key will be string of random 128 character.

*To disable the old Signature Key, click the check box labeled Disable Old Signature Key Immediately. If the Disable Old Signature Key check box is not selected, the old Signature Key will automatically expire in 24 hours. This will also impact any use of the Signature Key for transaction response validation for the SHA2 field. If the old Signature Key is not expired the previous key will continue to be used for the hash/response validation.

Finally, configure your Signature key in PaperCut:

  1. Stop the PaperCut Application Server Service. Follow the steps here on how to do this.
  2. Open the payment gateway config file ‘ext-payment-gateway-authorize-net.properties’ (located in [install-path]/server/lib-ext/).
  3. Add the line ‘authorize-net.sha2-hash-value=‘ and include the signature key from Authorize.net after the = sign.
  4. Important: Make sure that you delete the line with ‘authorize-net.md5-hash-value’ - you can’t have both hash value lines in the config file at the same time.
  5. Start the PaperCut Application Server Service.

Please refer to the updated Authorize.Net - Quick Start Guide for more information.

I ran into an issue - what do I check?

  • When adding funds, in the PaperCut interface I get an error: Unable to resolve expression ‘fingerprintHash’ for ext.paymentgateway.pages.AuthorizeNetRedirect$Enhance.

This indicates that both the ‘authorize-net.md5-hash-value’ and ‘authorize-net.sha2-hash-value’ lines are present in the ext-payment-gateway-authorize-net.properties config file. If you’re using the new SHA2 hash, make sure that you remove the MD5 line from the config file.

  • When adding funds, after entering payment information, in the Authorize.net interface I get an error: An error occurred while trying to report this transaction to the merchant. An email has been sent to the merchant informing them of the error. The following is the result of the attempt to charge your credit card: This transaction has been approved. It is advisable for you to contact the merchant to verify that you will receive the product or service.

This indicates that Authorize.Net has not been able to contact the PaperCut server in order to confirm the transaction to the App Server. Check Stage 1, step 8 in the Authorize.Net - Quick Start Guide to confirm that the ‘Default Relay Response URL’ has been set up correctly in the Authorize.Net merchant interface.



PC-15040: Some Print scripts stop working after upgrading to 18.3.2.

Some Print scripts stop working after upgrading to 18.3, you could be seeing an issue that could be related to the JS engine upgrade we included in this version.

Update: This has now been resolved in 19.0.0.



PC-14841: Email to Print doesn’t respect the default driver settings configured on the queue (e.g. duplex etc)

If you’ve set up Email to Print to print to a queue with default print settings (e.g. you want the jobs to always print in duplex, or grayscale), those settings will no longer be respected in version 18.2.3. Web Print is not impacted by this and will continue to respect the defaults set up on the queue.

Fixed in 18.3.3



14874: If you’re on v18.2.6 with a Server running MacOS/Linux, jobs won’t print with Google Cloud Print and Email to Print

When a job is being processed by the print provider, we don’t end up printing the job. This issue only happens if you’re on PaperCut NG/MF 18.2.6 with the PaperCut Application Server on MacOS/Linux and with Google Cloud Print/Email to Print .

Fixed in 18.3.2.



14600: Canon Pro devices not working well on High Sierra.

We are seeing issues with Canon Pro devices not working well on High Sierra and above. Every time a user tries to send a print job to a PaperCut monitored print queue it shows the following message: Stopped no pages found!

This has now been fixed in 18.3.2



14580: The PayPal payment gateway now requires using HTTPS for the IPN URL.

The Notification URL on the PayPal account site must now use HTTPS.

For your IPN verification postbacks (the Notificatin URL configured on the PayPal account site), if you are currently using HTTP you’ll need to make this adjustment to use HTTPS. There is more information about this from PayPal here: https://www.paypal.com/sg/webapps/mpp/ipn-verification-https

In order to keep your PayPal Gateway working with PaperCut, you’ll need to:

  • Log into your PayPal Manager Interface / Merchant Account Site:
  • For PayPal Payflow: head into Service Settings → Hosted Checkout Pages → Set Up → Silent Post URL
  • For PayPal Website Payments: head into My Account → Profile → Instant Payment Notification → Preferences → IPN Settings → Notification URL

To ensure that the new https:// url will work, copy the current URL listed there, and paste it into a new browser window, changing http to https to make sure that you can successfully hit the end point. If that works, go ahead and change the URL in your PayPal settings to the new value with https://

For example, you would see something like https://papercut.myorg.edu/rpc/gateway/paypal-wps , where papercut.myorg.edu is the external hostname of your PaperCut server. If you’re using PaperCut’s default HTTPS port 9192, then you would see the port in the IPN URL like the following: https://papercut.myorg.edu:9192/rpc/gateway/paypal-wps



14526: In PaperCut version 18.2.4 the Print Provider may crash when Hardware Page Checks are enabled.

To resolve this issue, upgrade to 18.2.5 which has this fixed.

If you can’t upgrade to 18.2.5 right now, you can do the workaround we cover below: Please leave the hardware checks feature enabled but edit the print-provider.conf file following the steps below.

  1. On the PaperCut server, browse to [Application-Directory]\Providers\print\win\.
  2. Open the file print-provider.conf with a text editing program.
  3. Add the line IsPrintingBasedOnPortMonitor=off to the file and save.
  4. Open Services.msc, find the service “PaperCut Print Provider” and choose Restart for the new configuration to take effect.



14525: Issue with the built-in database driver causing excessively long connection times to SQL 2016.

We have seen several tickets come in recently with DB connection times exceeding 6000ms with some organizations using PaperCut and SQL Server 2016. The issue causes a cascade effect as the application opens new connections to perform database tasks. Eventually, the application hits the DB connection limit and appears to crash. Organizations report different symptoms like slow printing, error pages while reaching the application’s user web pages, or can’t log into the admin console.

Organizations have found dropping back to SQL Server 2012 generally solves the problem, however, we also have instructions to use Microsoft’s own SQL driver which claims to be much faster than our current Java driver.

To add the MS driver into PaperCut (prior to PaperCut 19.0) please follow these instructions.

  1. Download the latest version of Microsoft’s JDBC driver for SQL Server (sqljdbc_7.0.0.0_enu.exe) from this link: https://www.microsoft.com/en-us/download/confirmation.aspx?id=57175
  2. Run sqljdbc_7.0.0.0_enu.exe to extract the files.
  3. Copy the file mssql-jdbc-7.0.0.jre8.jar from the location the files were extracted to, to <PaperCut MF or NG install directory>\server\lib-ext\
  4. Comment out your current SQL entries (these will form your backup plan)
  5. Copy the following entries into the server.properties file and modify to point to your SQL server:

database.type=SQLServer
database.driver=com.microsoft.sqlserver.jdbc.SQLServerDriver
database.url=jdbc:sqlserver://<serverName>:<portNumber>;databaseName=<databasename>;socketTimeout=600000
database.username=<user name>
database.password=<password>

If the connection requires additional properties (not expected, based on what we know), they can be found here: https://docs.microsoft.com/en-us/sql/connect/jdbc/setting-the-connection-properties?view=sql-server-2017

Update: This has now been resolved in 19.0.0. If you’re using the old built-in database driver, you’ll now see a warning in the Application Log advising to upgrade to the Microsoft driver. If you’re on PaperCut 19.0.0 or later then you can rest easy. The updated MS DB drivers are bundled in the PaperCut build, so you don’t have to download any extra drivers. However, there are two changes in the database connection settings, in the server.properties file that you’ll need to make:

  • database.driver (update to the driver being used)
  • database.url (update to the format of the connection string)

See below (or the server.properties.template file) for an example (note: you’ll have to change ‘localhost’ to your db server name or IP, ‘1433’ to whatever port you’re using for your SQL Server, ‘papercut’ to whatever your DB name is). See here for a little more information. database.type=SQLServer
database.driver=com.microsoft.sqlserver.jdbc.SQLServerDriver
database.url=jdbc:sqlserver://localhost:1433;databaseName=papercut;socketTimeout=600000
database.username=
database.password=



14440: PaperCut NG/MF 18.2.3 for iPrint does not work on anything other than OES 2018.

Fixed in 18.2.6



13625: PaperCut NG/MF does not save the regex when synching Primary/Secondary numbers.

As a workaround, you can use the following config keys to update the regex for Primary and Secondary Sync source.

user-source.card-id-regex (For Primary sync source) user-source.2.card-id-regex (For Secondary sync source)

These config keys can be updated via Options → Config Editor.

Update: This has now been resolved in 19.0.0.



13923: When trying to access the PaperCut Admin console or user pages, one sees a message pertaining to “An error occurred starting the PaperCut MF application server service “.

If you see a white background instead of the typical login page stating something similar to “An error occurred starting the PaperCut MF application server service,” search for the string “mapdb”. If you find a match, try the following steps:

1) Stop the PaperCut Application server service. Follow the steps here on how to do this.
2) Delete all files in [app-path]\PaperCut MF\server\tmp directory
3) Move all mapdb files in [app-path]\PaperCut MF\server\data\internal to a different directory.
4) Restart the PaperCut Application Server service.

Note that version 18.3.6 includes a fix for the issue preventing the need for the steps above.



14295: additional-groups.txt file no longer includes internal users when performing sync.

When using the additional-groups.txt file to add internal groups to PaperCut we have found that internal users will not be imported into the internal groups when performing a sync. If AD users have been added they will appear in the internal groups.

Resolved in 18.2.4



14220: Errant warning displayed upon first load of the Bulk User Operations page of Admin web interface.

Upon first load of the Bulk User Operations page of the Admin web interface, a warning that “This setting requires this user to run the client software at all times.” is displayed. This warning should only be shown if the Change account selection setting checkbox is enabled and an option warranting the warning is selected from the dropdown menu immediately below it.



14161: Payment hardware (attached to the PaperCut Pay and release station) listed below, and possibly some infrequently used standalone hardware or payment integrations, may stop working after upgrading to PaperCut NG or PaperCut MF 18.2.1. or above

If you use third party terminal integrations then we recommend bringing the latest PaperCut version up in a test environment first to make sure your integration work. Alternatively you may contact PaperCut support with a list of your integrations to see if we think there may be an issue.

PaperCut will provide a maintenance release to address this issue if it is detected.

A fix for the following payment solutions was provided in PaperCut NG and MF 18.2.2

  • Apex 5000
  • Microcoin
  • SEM-ACS 9500Ss
  • Boscop Coin Op



14091: Shared Account selection via Mobile web client not working as expected in some environments

When account selection is required for a printing user, we attempt to locate a matching User Client session to issue an Account Selection Popup to, so that the user can select from their available account options before the print job proceeds. To find the right User Client session, PaperCut MF and PaperCut NG will compare the IP address, machine name, and username associated with the print job with those same details recorded against every currently active User Client session, and the closest match will be selected.

The Mobile web client registers its session with a machine name of web_client, as a machine name is not readily available for browser sessions. This means that the machine name from a print job cannot be successfully used to find a matching Mobile web client session, leaving us to rely upon the IP address and username.

However, under certain circumstances the IP address of the print job and the Mobile web client will not match. For example, if a desktop machine is connected to two networks, and the print job is associated with one IP and the Mobile web client another, this will leave only the username to match on. Some Mobility Print jobs may be similarly impacted in select network environments.

By default, we will not match a User Client session to a print job on the basis of the username alone. Under the rare circumstances outlined above, this means that the Account Selection Popup will not be issued to the user, and the print job will not be able to progress.

This behaviour can be circumvented by changing a particular config key via the Advanced Config Editor, allowing print jobs to be matched to User Client sessions based solely on the username. HOWEVER, making this change can have unexpected impacts for some deployments, so it is best to confer with your primary support contact beforehand, as well as thoroughly testing the adjustment afterwards. For PaperCut MF, you can identify your primary support contact via the Support section of the About tab in the Admin web interface. For PaperCut NG, feel free to raise a ticket via https://support.papercut.com to discuss further.



13934 : An access denied message appears when switching from Job Ticketing to the PaperCut MF Admin web interface.

When switching to the PaperCut MF Admin Interface from Job Ticketing, you might receive an ‘Access Denied’ message. This occurs when as an admin, you have accessed the Job Ticketing customer pages from the PaperCut MF User web interface.

The workaround for this issue will be to manually navigate back to the PaperCut MF Admin web interface.

Note that this has now been fixed in 18.2.3



1863 : If the Job Ticketing version is older than November 2018 and auto updates have been turned off, upgrading to the latest version of Job Ticketing will fail once auto-update is enabled.

Upgrading to the latest version via auto updates will fail if the version being upgraded from is earlier than November 2018. A step upgrade to version #2700 (see below links to download) is required before enabling auto updates.



13687 : The PaperCut Admin interface and some device screens may not show specific language translations correctly.

After upgrading to PaperCut 18.1.1, in the PaperCut Admin console, you may notice some translation strings not appearing correctly on some pages if you’re using PaperCut NG and MF. In addition, with PaperCut MF, this may also affect screens on the device like scan action names/details for integrated scanning. The device UI items are all unaffected, i.e. Button labels, dialog names, text descriptions.

The following languages are affected: Catalan, Czech, Danish, German, Spanish, Finnish, French, Croatian, Hungarian, Italian, Hebrew, Japanese, Korean, Dutch, Norwegian, Portuguese-Portugal, Polish, Russian, Slovenian, Serbian, Turkish, Chinese (China, Hong Kong, Taiwan).

This has been fixed in PaperCut NG/MF 18.1.2.



13542 : Google Cloud Print will be stuck in initialization loop if job sync times out after upgrading to 18.0.4 or higher

After upgrading to PaperCut 18.0.4 or a higher version, Google Cloud Print may stop working and the status may change to “Initializing…” or “Initialising…” depending on your locale.

PaperCut 18.1.3 will address this issue. In the meantime, there is a hot fix build available. Please reach out to us via support.papercut.com for assistance.




13437 : User re-prompt to enter their Account Selection/Comment/Invoice details again for held jobs after upgrading to 18.0.4 or higher

When upgrading from an older version of PaperCut to PaperCut 18.0.4 or higher, any held jobs within a Hold/Release queue may cause the User Client to re-prompt the user to enter their Account Selection/Comment/Invoice details again (only if these features are enabled).

Reach out to us via support.papercut.com and we’ll update this known issue page once we have more information.




13311 : Users color selection ignored when printing from the Chrome browser on Windows

Any print jobs sent from the Chrome browser to a print queue on Windows will always print as color even when the user chooses grayscale. This issue isn’t specific to a PaperCut version. It was first introduced in Google Chrome browser 60.0.3112.78.

This has now been fixed in Chrome version 67.0.3396.99. See this Chromium bug report for details.




13231 : Integrated Scanning “Scan to Folder” and “Scan to Custom Email” Scan Actions fail to deliver document if user’s email address not populated on Application Server

In PaperCut MF version 18.0.2, Integrated Scanning will fail to deliver a scanned document via a “Scan to Folder” or “Scan to Custom Email” Scan Action if the associated user account does not have an email address defined within their User Details on the Application Server. The scan jobs are tracked and accounted for in the Job Log as normal, and no error message will be displayed, but the document won’t arrive at the folder location or custom email address. Users with an email address populated in their User Details are still able to use these Scan Actions successfully.

A hotfix build is available from support.papercut.com, and this same fix will be formally available in the impending PaperCut MF 18.0.3.




13037 : A rare issue on older devices can cause a connection failure with the PaperCut Application Server.

A rare issue exists on some older devices whereby if the Application Server SSL certificate has a ‘Not Valid After’ date that exceeds January 19 2038, a data overflow exception can occur which could cause a connection failure with the PaperCut Application Server.

More information can be found here.

The workaround for this issue is to regenerate the certificate using keytool, with a ‘Not Valid After’ date that is before January 19 2038.

This issue has been fixed in v18.0.4.




12987: Jobs released from the queue are not being printed then showing back up in the queue on hold.

Occasionally jobs that are released from the queue are not printed and then listed again in the hold release queue indefinitely.

This has been fixed in v18.0.5, or the workaround for this issue is controlled by setting the config key ‘release-station.released-job-processing-timeout-secs’ to 680.




13066: Orphaned print jobs can cause jobs in the print release queue to be hidden for all users.

On rare occasions, an orphaned print job can cause all print jobs in the same print release queue to be hidden for all users until that PaperCut print provider is restarted.

This has been fixed in 18.0.5, or this error condition can be avoided by increasing the timeout config key ‘print-provider.offline-if-no-contact-seconds’ to 31536000.




12935: On MacOS High Sierra only (10.13), when you run the Control Printer Monitoring.command, PaperCut does not track the print queues.

The print queues don’t show up in the PaperCut Admin console > Printers tab. This is now fixed in v17.4.4.




12505: iOS apps Pages, Keynote, and Numbers v3.3 (5052) paper size issue

We have had some customers experience issues relating to incorrect paper size when printing from Apple’s Pages, Keynote, and Numbers apps on iOS devices. This seems to be affecting the latest update of the apps, v3.3.

If you are experiencing issues with incorrect paper size when printing from Apple’s Pages, Keynote, and Numbers v3.3, can you please contact support via http://support.papercut.com




12290: There has been an issue reported where the Application Server is failing to read the service.conf file. This means custom memory allocation settings may be ignored and the Application Server will run with a default memory allocation (1/4 of the system memory).

This is resolved in PaperCut MF version 17.3.3 (build 41733) and PaperCut NG (build 41734).




12181: Slow response time on card swipes when using RFIDeas 241 Client Mode. (since July 26th, 2017)

When using ‘RFIDeas 241 Client Mode’ as the connection type for a Network Card Reader, there may be a short delay (~3 seconds) from when the card is swiped, until when the swipe is registered by the PaperCut App Server.

The ‘RFIDeas 241 Client Mode’ interface itself is responsible for this delay, and as such PaperCut cannot provide any improvements for it. RFIDeas have mentioned that they are aware of this delay and are working on bringing out an improved firmware.




12173: You may receive an error message “Unknown Error” when accessing “Jobs Pending Release” screen in the PaperCut Admin Web UI.

This is resolved in PaperCut MF version 17.3.3 (build 41733) and PaperCut NG (build 41734).




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.




10959: An issue preventing Admins from accessing the configuration pages of Value Loaders and Kiosks.

When you’re trying to access a Value Loader or Kiosk from the PaperCut Admin console > Devices tab, the following error occurs:

Unable to resolve expression 'supportsGuestAccessAndUserAuthMix()' for web.components.....

Please contact PaperCut support for the hot-fix build.




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.


Categories: Known Issues


Keywords: known issues, 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 December 05, 2019, at 12:00 PM
Printable View   |   Article History   |   Edit Article