Pacejet

Pacejet Connector 25.2 Release Notes

Enhancement

Improved Print Selection Requirement

Having one Print Connector configured to manage all print tasks causes printing failures, as a result, the Local Shared Printers interface has been updated and will no longer allow running a Print Connector without specific printer(s) identified. During installation, you will now be required to select at least one Local Shared Printer. Select the printer(s) that will be managed by this Print Connector. Ensure that no other Print Connectors are configured for these same printers.

A new Print Connector (.msi) is available. For information about downloading and installing the Pacejet Connector, refer to Downloading & Installing Pacejet Connector.


Bug Fix

ID

Description

MCS - 7476

We corrected an issue in the Print Connector losing its connection to AWS. Restabling the connection was taking too long, and, as a result, slowing down printing. Now, when the connection is lost, it will be reestablished more quickly.

These conditions were reflected by errors in the Print Connector log file, such as: “Error Encountered in CheckForPrintJob - The request failed with HTTP status 502: Bad Gateway.”, or “Error Encountered in CheckForPrintJob - Server was unable to process request. --->A transport-level error has occurred when receiving results from the server.”.