-
Jobs held for Reprint on a Pharos controlled Printer would result in a 'Deleted Print' transaction record being created when the job was purged at the end of the Reprint Hold Period. The application of this Hot Fix ensures that only purged jobs that have never been printed (ie from Spool Queues) are recorded for Waste Reduction reporting.
-
Attempting to move a print job from one Pharos Spool Queue to another within Pharos Web Remote could result, under certain conditions, in the error: "Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host." The application of this Hot Fix ensures that jobs can be successfully moved between queues.
-
If a Change Control request was issued while the Print Server was under high load, then there was a possibility that it would a) stall (deadlock), b) reduce the number of threads available to process jobs, until none can be processed, or c) crash the Print Server. The application of this Hot Fix ensures that the Print Server will continue to function correctly when Change Controls are issued under high load.
-
Support for certain EMF Advanced Printing Features has been improved for UNC printing. This also requires an updated pagecounter.exe which can be retrieved from the Pharos website. Features such as N-up, Watermark and Booklet are now retained through to the printing of the job and can be pagecounted and charged for. Note: If the printer driver or print processor of the spool queue and the print queue do not match, the Advanced Printing Features data will not be passed to the printer, to avoid potential issues with the Windows Spooler. (Pharos Popups also supports advanced Printing Features, however the job is not submitted in EMF form. It will always be rendered to the driver type in use, eg Postscript, PCL, before being sent to the Pharos services.)
-
Print jobs sent to a Direct Pharos Spool Queue, where the user declined the Popup cost acceptance dialog, were incorrectly reported as 'Job disallowed by Uniprint'. The application of this Hot Fix ensures that direct queue jobs where the cost is not accepted are correctly reported as 'User declined cost acceptance'.
-
Filtering print jobs within Pharos Web Remote would be restricted to filtering of the set of records retrieved before the filter was applied. The application of this Hot Fix ensures that the number of records shown when a filter is applied in Remote will be up to the maximum set in the appSettings.config file, rather than a subset of the original records.
-
If a script set PlugIn.Error to a value including a percent sign, the Print Server service would crash. The application of this Hot Fix ensures that error messages containing percent signs do not cause service failure.
-
When using the previous Print Server Hot Fix, print jobs sent to a Direct Pharos Queue while the Print Server service was offline would not be queued for handling following restart of the service. The application of this Hot Fix ensures that jobs will be held for processing once the service is restarted for both Spooled and Direct Queues.
-
Building Packages with certain Canon PS3 printer drivers would result in an "out of memory" error. The application of this Hot Fix ensures that packages including these printer drivers build correctly.
-
If the printer object corresponding to a Pharos Spool Queue was deleted in the Windows printer dialog, this would result in either some or all print jobs not being visible within Pharos Web Remote. The application of this Hot Fix ensures that queued print jobs are displayed correctly in Remote.
-
Under certain conditions, the JobArrival events were not always being fired for all print jobs received by the Print Server. The application of this Hot Fix ensures that all print jobs are correctly handled on arrival.
-
Unexpected logging ouptut from the IPBilExt.exe plug-in recorded in the Print Server log could cause the Print Server to crash. The application of this Hot Fix ensures that unexpected logging output is correctly handled.
-
Under certain conditions, certain printers may update an error status either incorrectly or with poor timing, resulting in jobs being lost when they could have been printed correctly. A workaround has been added to the Print Server to allow the bypassing of the reported error states. For details on how to implement the workaround, please contact Pharos Support.
-
It was not possible to set the Server HostName record in the Pharos Server Configuration to use either a Fully-Qualified Domain Name or a DNS Alias. This would result in some Popup clients not being able to connect to the Service. The application of this Hot Fix allows the use of Fully-Qualified Domain Names or DNS Aliases. To update your server to use a FQDN or Alias: