When two Trackers with the same name tried to connect to the Analyst a number of exceptions were thrown. This usually happened when Workstations were renamed and the names used to belong to other machines with Trackers on them. The application of this Hot Fix ensures that if a Tracker with the same name exists then the second Tracker will be renamed by adding (1), (2), etc to the end of its name.
This Hot Fix includes the following enhancements and fixes that increase support for Novell environments:
- When using NDPS printers in a Novell environment where the printers have been pushed to client workstations and have port names such as \\NDPS01, \\NDPS02 etc, the printers were reported in Blueprint using their port names instead of the printer name. The application of this Hot Fix ensures that the Tracker will report the printer name as seen by the user in the Printers window on the client workstation.
- This Hot Fix ensures that the Tracker correctly retrieves Novell printer driver names and other Novell information correctly, and fixes problems when other software unhooks the Tracker, e.g. Novell client update.
This Hot Fix includes fixes to prevent the spooler crashing in the following cases:
- When using printer drivers with a bi-directional language monitor on Windows XP or later.
- When using 64-bit Windows.
This Hot Fix adds support for extracting the port hostname/IP address from the "Lexmark Enhanced TCP/IP Port" registry key.
If an error occurred in the Tracker during the batching of print jobs, the Tracker would abort the batch process. If the error related to a problem on the Tracker, it would occur again during the next attempt to batch, which would hold up the job sending indefinitely. The application of this Hot Fix ensures that such errors do not hold up the batching process.
If the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation was set to "1" and the Tracker was not installed in the default location, page counting operations would fail. The application of this Hot Fix ensures that pages are counted correctly in this situation.
Slow processing of print jobs on a server or client machine with the Tracker installed. The problem is caused where there are restricted permissions to %Program Files% \ PharosSystems \ OutputManagement \ PrintTracker \ Spool or temporary directories on the machine. The problem can be identified by a large number of zero length psp*.spl files collecting in one of these directories.
The ComTaskMaster service consuming high CPU and memory resources within minutes of starting up. The problem was caused by the way that older Blueprint 3.0 jobs were processed and sent to the server. This issue only applies to sites which have upgraded from Blueprint 3.0.
When using NDPS printers in a Novell environment where the printers have been pushed to client workstations and have port names such as \\NDPS01, \\NDPS02 etc, the printers were reported in Blueprint using their port names instead of the printer name. The application of this Hot Fix ensures that the Tracker will report the printer name as seen by the user in the Printers window on the client workstation.
In the presence of certain printer drivers, the Blueprint Diagnostic Tool would fail with an error message when run on Tracker workstations. The application of this Hot Fix ensures that the Diagnostic Tool runs correctly on Tracker workstations.
The Blueprint Diagnostic Tool would fail with an error message when run on Tracker workstations using a French locale. The application of this Hot Fix ensures that the Diagnostic Tool runs correctly on Tracker workstations.
Previously, the Tracker could pagecount jobs incorrectly when printing PDF documents to certain printers. The application of this Hot Fix ensures that such jobs are counted correctly.
This Hot Fix includes enhancements that increase support for Novell environments. It ensures that the Tracker correctly retrieves Novell printer driver names and other Novell information correctly, and fixes problems when other software unhooks the Tracker, e.g. Novell client update.
If a Tracker was unable to contact its Collector for a long time, it would attempt to send all stored print jobs in a single, potentially very large batch file when contact was re-established. Application of this Hot Fix ensures that Trackers will never send a batch larger than the Maximum Batch Size property (configured on the Tracker > Settings screen in Blueprint Administrator). Jobs will be grouped into multiple batches smaller than this size if necessary.
If the Blueprint Diagnostic Tool was left running, or the process stopped unexpectedly, diagnostic gathering would not be turned off, which used up system resources. This Hot Fix ensures that diagnostic gathering will be stopped after 2 hours. The Hot Fix includes stability improvements to the Diagnostic Tool.
This Hot Fix adds a command line option was added to Tracker installer, so that you can specify an install directory:
InstallPackage.exe /dir="c:\install\directory"
(Note the quote marks, and no space between the /dir= option and the install directory path.)
The application of this Hot Fix improves error handling, error reporting and robustness of the Tracker when the server is under load.
The Tracker now supports Lexmark C770 and C772 printer drivers.
This Hot Fix improves the Tracker installer's detection of the Windows operating system.
This Hot Fix removes the AlwaysSpoolToRaw, FilterDataTypes and GetJobAnalysis settings, as they are no longer necessary.
The Hot Fix adds the ability to define the location of the Print Tracker spool directory should it be necessary. Contact Pharos for more details.
In situations where a Tracker was unable to communicate with its Collector for some time, and a large number of job XML files built up in the outbound jobs store, attempts to send a batch to the Collector would still fail when communication was restored. The application of this Hot Fix ensures that batches can always be forwarded when communication is possible.
Attempting to upgrade the Tracker on a busy print server (with print jobs continually coming through) would sometimes result in an incomplete upgrade, where not all of the required files were updated. This Hot Fix ensures that Tracker upgrades always succeed.
Copyright © 1994-2008 Pharos Systems International, Inc.