Hot Fix 23 supersedes Hot Fix 21 and addresses the entire list below.
However, only the first five items below are unique to Hot Fix 23.
The others were previously addressed in Hot Fix 21 or earlier.
Support for EMF Advanced Printing Features has been added to the Pharos Print Server 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. (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.)
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 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.
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.
If someone inadvertently deleted the printer object in the Windows printer dialog corresponding to a Pharos Spool Queue, then some or all print jobs would not be visible within the
Pharos Station, or the Printing context in Pharos Remote. The application of this Hot Fix ensures that queued print jobs are displayed correctly.
Under certain conditions, the JobArrival events were not always being fired for all print jobs received by the Print Server.This could result in print jobs appearing to be lost.The application of this Hot Fix ensures that all print jobs are correctly handled on arrival.
Via SNMP, certain printers may report an error status incorrectly or with poor timing. Currently, Uniprint default behavior is to stop printing to such printers until they return to a non-error state. However, some print jobs may be lost when they could have been printed correctly had Uniprint continued to send the jobs to the printer regardless of it reporting an error state. With the application of this Hot Fix, the Pharos Print Server now supports disregarding SNMP error messages. For details on how to enable this, you will need to contact Pharos Support.
This Hot Fix provides support for three new Plug-in points in the Print Server: CopyEndJob, FaxEndJob and ScanEndJob. Should you wish to utilize these, please contact Pharos Support for details.
The application of this Hot Fix prevents possible crashes or errors that could occur when performing a Change Control while the Print Server was under load or in the process of restarting or shutting down.
The application of this Hot Fix will prevent the Print Server from crashing if an invalid Script causes an access violation error.
PrintJobArrive scripts attached to the Print Server could fail with a Job_Info_2 error when the printer driver produced 2 spool files (the first a temporary zero size file). The application of this Hot Fix means that the zero size file is now ignored and the failure does not occur.
Discount Rates were not applied when Standard Charging was used. The application of this Hot Fix ensures that Discount Rate Schedules are now applied to Standard Charging.
When Users are not identified in the Pharos database (such as when using cash cards or gateways) an Alert was raised for each print job submitted to a Spooled Queue. The application of this Hot Fix ensures that Alerts are no longer raised in this scenario.
When Users are not identified in the Pharos database, they were unable to print color jobs as their permissions could not be verified. The application of this Hot Fix ensures that Users who are not identified in the Pharos database are assumed to be members of the 'Public' User Group and are assigned the permissions of this User Group.
If all Regular Expressions were deleted from the Pharos database, usernames would be returned as empty strings. This meant that users were unable to print, with an error message: 'Unable to retrieve funds for your Logon ID'. The application of this Hot Fix ensures that usernames are returned correctly and users can print when no Regular Expressions are present.
An Encrypt function has been added to the String class of the Pharos Scripting Language. This means that a separate stored procedure is no longer necessary if encryption is desired. The function is used as follows:
import "String";
new sampletext = "abc";
String.Encrypt(sampletext);