Skip navigation
All Places > Knowledge Base & Downloads > Blog > 2013 > August > 07

SignUp offers three reservation modes: Immediate, Queued and Scheduled. As of SignUp Vx2, any combination of reservation modes may be offered at a site; however, issues arise when certain combinations are used. This document describes the consequences of using each of the possible combinations of reservation mode. See the attached Pharos TechNote.

If I try to use the "Create Associated Terminal" to create a terminal for an existing device, it only works when the terminal type selected is "Generic." Also, if I view a previously-created terminal in Blueprint Administrator, I only see the "Settings" tab; the "Configuration" tab is missing.

This can happen if the Analyst or Collector has been reinstalled for whatever reason, but the existing database remained intact and is being used by the new installation.

To correct this behavior, do the following:

  1. On the Collector or Analyst (whichever is hosting the EDI service), locate the terminal's ".terminal.config" file. In Windows 2003, this would be in C:\Documents and Settings\All Users\Application Data\PharosSystems\Blueprint\TerminalPlugins. In Windows 2008, this would be in C:\Program Data\PharosSystems\Blueprint\TerminalPlugins. For this example, the Omega PS200.1.0.1.terminal.config file will be used.
  2. Move this file to the Blueprint \Bin directory (C:\Program Files\PharosSystems\Blueprint\Bin; on 64-bit systems, start in C:\Program Files (x86)).
  3. In a Command Prompt window that is running as an Administrator, navigate to the \Bin directory.
  4. Execute the following command:

    C:\Windows\Microsoft.NET\Framework\v2.0.50727\InstallUtil.exe /TerminalConfigFile="Omega PS200.1.0.1.terminal.config" PharosSystems.Blueprint.TerminalPlugins.Ini.dll

    Note that this example assumes that Microsoft Windows is installed to the Windows directory. Also, replace the file name (shown in blue) with the .terminal.config file that has been moved.
  5. Back in Blueprint Administrator, go to Devices > Terminals and select the terminal. The terminal definition should now include the "Configuration" tab.

At this point, you may also use the "Create Associated Terminal" button and reference that terminal type in the resulting dialog box. You will need to repeat these steps for every terminal type that exists within the solution.

Omega PS100 Power Supply Specifications

Power: 5VDC regulated output
Current: 2.4A minimum output

Connector: The output connector must be center positive and 2.1 (inside diameter) x 5.5 (outside diameter) x 9.5 (length).

Please note: most power supplies available off the shelf are 2.5x5.5 or 2.1x5.0 and they will be unreliable. We recommend you purchase a Pharos replacement power supply by contacting Pharos or your Pharos Reseller.

This is a known issue. The workaround to obtain a PDF is to export to Word format and print to PDF using Adobe Acrobat. All reports print correctly.

I get the following error when I run the Blueprint Server Configuration Test:

Blueprint 3.5 SP1+ Server Configuration Error: "The request failed with HTTP status 403: Forbidden." for the following services : Tracker Web Service and EDI Web Service

Please check the attached screen shot to verify the error and the answer.

Solution:

For Server 2003:

1) Please make sure under IIS for the Default Website that the "Scripts only" is selected for the Execute permissions which exists under the Home Directory tab. (Overview.jpg)

2) Once that is done, the PharosEDI(PharosEDI.jpg) and PharosSystems(PharosSystems.jpg) should have the Execute permissions as per attached screen shots. After changing, confirm that the PharosEDI and PharosSystems virtual folders are both set to "Scripts only"

For Server 2008:

1) Confirm "Read" & "Script" features are selected for the Default Web Site. (IIS -> Handler Mappings -> Edit Feature Permissions). Check the attached screen shot to verify the settings(Server 2008_IIS.JPG)

Every time I use the Blueprint Server Configuration utility, I get an error when testing the Web Server.

Errors:

1. The request failed with HTTP status 404: Not Found

Or

2. Web server responds with unrecognized html
This is related to a permissions issue:

1. Open IIS
2. Click Web Server Extensions
3. Make sure Asp.net 1.1.4322 is set to Allowed

Note: If the client is running version two of ASP.NET this is not supported with 3.1 or 3.2. Have the client install 1.1.4322 and make sure it is set to Allowed in the Web Server Extensions. Blueprint will look for and use version 1.1.4322.

When a user sends a print job configured for "black and white" printing (also called monochrome or grayscale in several printer drivers), it is identified as a color print job in reports, and is also priced out as a color print job for billing or charge back. Why is this?

Why This Happens

Different printer makes and models have different ways to specify if a job is to print in color or monochrome. Sometimes, this can change even between printer driver versions for the same printer model. The Pharos Page Counter software (part of the Blueprint Tracker client and the Uniprint Print Server application) is the component of the Pharos solution that parses the print job for its color (or lack thereof) mode. While this component understands most of the ways that printer drivers identify the color mode of a print job, it must be constantly updated to ensure that it remains compatible with new printer models and drivers as they are released.

How To Fix It

To determine if the latest available Page Counter software resolves your specific challenge, download and install the new Page Counter. The download location is https://private.filesanywhere.com/pharos/fs/v.aspx?v=8a7066889e9c6fb9a9ae. To install, follow the steps below for the different Pharos products:

Installation steps (Uniprint)

 

- Browse to the folder ..\Pharos\bin\
- Archive (save, rename, etc.) the existing Page Counter files
- Copy the new Page Counter files into the ..\Pharos\bin folder
- Test the Page Counter with print jobs that are known to be problematic

 

Installation steps (Blueprint)

 

- Browse to the folder ..\PharosSystems\Blueprint\Bin
- Archive (save, rename, etc.) the existing Page Counter files
- Copy the new Page Counter files into the ..\PharosSystems\Blueprint\Bin folder
- Test the Page Counter with print jobs that are known to be problematic

And If It Still Doesn't Work?

 

If the upgraded Page Counter does not resolve the issue, then the driver (or file format of the spool file) is producing a command for the color mode that Page Counter does not understand, and it must be upgraded to support it. In this case, generate several spool files (see KB Article "Capturing Spool Files" at http://pharos.custhelp.com/app/answers/detail/a_id/498) and submit them to Pharos Support. After submitting the files, they will be reviewed and changes, when possible, will be made to Page Counter and provided to you through the same download link as above. In some cases, we may suggest additional changes to the printer driver configuration to ensure consistent color mode capture.

Other Ways Around This

The way the Device is configured will also help alleviate the problem. Both Uniprint and Blueprint allow the administrator to specify if a Device is monochrome or not. In Uniprint Administrator, modify the Printer Type property to "Black and White". In Blueprint Administrator, select the Device and make sure that the Model specified is a monochrome device. This change will affect all go-forward interaction and reporting.

Note that in Pharos Blueprint, this method will not resolve client-side issues with Policy Print (where a Policy can flag for color printing). To manage a Policy Print correction, the Page Counter application will have to be updated to accommodate the printer driver.

Uniprint 8.x Support for PS100

 

Product:

 

Pharos Omega PS100 terminal
Part Number: 
OMG-PS100
Effected Regions:
World wide
Notice Date: 
October 12th, 2011

 


This notice serves as a clarification of the support of the Omega PS100 terminal with Uniprint 8.x. 
Starting with Uniprint 8.0, the Omega PS100 terminal is no longer officially supported. It is no longer
included as part of Pharos certification testing for newer versions of Uniprint.  If problems were to
be found, they would not be fixed.

 

Although it is not officially supported, no changes have been made to prevent their operation. 
Uniprint 8.x does not accept the original PS100 schema (used to determine the PS100 settings).
The Knowledge Base article Uniprint 8.x ‐ XML schema file to use for Omega PS100 describes the steps
needed to modify the PS100 schema for use in Uniprint 8.x.

 

The Omega PS100 terminal has been replaced by the Omega PS200 terminal.  The PS200
provides the functionality of the PS100.

 

 

 


Distribute to:

 

Pharos World-wide Customer Operations
Distribute by:

 

12 October, 2011

You can request a download link by e-mailing Pharos Licensing at licensing@pharos.com.

A) If running a full version of SQL Server, follow these steps:

1) Start the SQL query analyzer.
2) Select the pharos database.
3) Run the following script:

       update system
       set licenced_to = 'license key name', license_quick_key = 'sitecode01'

where:
       new license key name = license key name
       new site code = sitecode01

 

B) If running MSDE, follow these steps:

1) Find the user name and password needed to log on to MSDE.  These can be found on the PC where the Pharos Database server has been installed by running 'regedit'.

 

In the registry, go to:

HKEY_LOCAL_MACHINE\Software\Pharos\Database Server\Database

2) The "User Name" value holds the login name and the "Password" holds the password.

 

3) Go to the command prompt, and do a change directory to the \Binn sub-directory or sub-folder holding OSQL. If MSDE was installed at C:\MSSQL7  (commonly used default directory) then the OSQL is in the directory C:\MSSQL7\Binn.

 

4) Create a batch file with the following command:

OSQL -Uusername -Ppassword -Q"update system set licenced_to='license key name',license_quick_key='sitecode01'"

where:
           user name = username
           password = password
           new license key name = license key name
           new site code = sitecode01

5) Run the batch file (run the command in item 4 in the directory in item 3).

During an intial install of the Blueprint 5.0 Collector Server, the WCF Secure Communication service may fail its health status check.  In the Blueprint Server Configuration tool, the Enterprise Service Tester displays the error message:

Unable to update the server health status for the local server.  Please ensure the Pharos Systems TaskMaster service is running and that the parent server can be contacted.

Please see the screenshot below for an example:

Blueprint WCF Secure Communications test failure

Cause

The WCF Secure Communication service fails during an intial install of the Collector Server when the Analyst Server is running Blueprint 5.0 Service Pack 2 (SP2), but the Collector Server is not.

Technical Details

Blueprint 5.0 SP2 uses 1024-bit certificates, while prior versions use 512-bit certificates.  The Collector Server and Analyst Server are unable to establish an SSL connection due to the mismatched security configurations.  Blueprint 5.0 SP2 transitioned to 1024-bit certificates in response to the minimum certificate key length set by Microsoft Security Advisory 2661254 and NIST special publication 800-131A.

Resolution

Apply SP2 to the Collector Server, then re-run the Enterprise Service Tester from the Blueprint Server Configuration tool.  The WCF Secure Communication service should pass now.

The "UNKNOWN" user appears in reports from Pharos Blueprint Enterprise when a device meter feed is added to the configuration. When Blueprint imports meters for devices, there will always be a gap between the page volume the meter provides for the period and the page volume recorded by Tracker and Secure Release Here (SRH) for the period. This gap can either be positive (the meter count is higher than the volume established through combined Tracker/SRH data) or negative (the meter count is lower than the volume established through Tracker/SRH data).

  • Positive gaps are incurred through copier- or fax-enabled devices that are not being captured by a Pharos terminal, and can also happen when print occurs through a non-tracked desktop (a non-Windows system, usually) or from system print (mainframe, print generated at the device).
  • Negative gaps are incurred through miscounts on the part of Tracker/SRH due to some aberrant operating system or driver behavior, or by print cancelled at the device (for example, when an Excel worksheet is formatted incorrectly, so is cancelled by the user and resubmitted).

Because there is a gap, the page counts are scaled to accommodate during publication (Blueprint 5) or Period Close (Blueprint 4.2 and lower). In the case of positive gaps, an UNKNOWN user is created to hold the excess. How UNKNOWN is handled varies in reports. For example, if a Budget Center report is pulled, the UNKNOWN volume for a device is assigned to the Budget Center defined for the device, or, if not configured this way, to the Budget Center who has the highest volume on the device. In the case of negative gaps, the Tracker data is scaled down proportionally across the device's users to fit the meter volume.

If you wish to determine what devices are providing the gap, the only option within Blueprint Reports is to run a Device Transaction report (in Blueprint 5, this is Supporting Material > Transactions > Device).

NOTE: Blueprint 5.0 includes integration with an application called Site Monitor by default. Site Monitor is an SNMP-based tool that utilizes the Connection information inside a device to obtain device meters.

Costing information is sent to the device during the authentication process. It's in the DevResExtGetAccountMap message. That message contains an Account Map consisting of 4 sections: Copy, Print, Scan, and Fax. Each of those contains a DocumentAccountList that is an array of cost data for each paper size that the machine supports, for several color options, and for simpex/duplex. There is quite a bit of data in total.

 

When the job is complete, the device sends back the cost for the job in the DevReqExtNotifyCounter message. There's a Counter element in that message that reports all of the counters that the machine maintains for a job (number of originals, number of prints, copy total, etc.). There's also a DocumentChargeList for each type of job that was executed. Within this element is information about the media type, the color type, the number of sides, the document count, and the charge for the job.

Pharos Omega Cable Table

Posted by toleary Aug 7, 2013

Overview

The Pharos Cable Table provides a cross-reference of Pharos Omega copy control cable information by specific copier make and model. The intent is to provide a quick reference document for use in quote development. Not all device models are included in the list. Information is not available for all models. As time goes on the intent is to grow the information in the cross-reference to keep it evergreen.

Standard versus Advanced cables - what's the deal?

The CopyLink Cable (hereafter referred to as "the cable") connects the manufacturer specific connector on the MFP to the Pharos SmartLink cable. The MFP generates an electrical pulse on this cable when an event occurs (such as when a page hits the output tray). All MFP's generate a pulse when a page hits the tray. This information is detected using a STANDARD cable. Some MFP's generate more pulses when different types of events occur (such as differentiating color from B&W or differentiating letter paper from legal). In order to respond to these advanced electrical signals an ADVANCED cable is required. The advanced cable is a more expensive option because the cable is more complicated and costs more to produce.

All devices can be controlled using a standard cable. This will allow the Omega to count the number of pages delivered. Some devices are capable of supporting an advanced cable (they have more information available on their foreign device interface). The type of additional data available depends on the MFP manufacturer. It is typically things like color versus B&W and page size.

The Pharos Cable Table

The Pharos Cable Table has been compiled from a variety of sources. Data that is filled in has a high probability of being correct. Data that is not filled in should be included as the information becomes available. The goal is to continually update this table with our experience from actual installations.

Standard Cable

This is the Pharos part number for a standard cable. If an asterisk (*) is present in the field then this represents an actual customer install with the cable. Non-asterisk data was derived based on the TRS Copier Cable and vendor information.

Advanced Cable

This is the Pharos part number for an advanced cable. If an asterisk (*) is present in the field then this represents an actual customer install with the cable. Non-asterisk data was derived based on the TRS Copier Cable and vendor information. A value of n/a indicated that this MFP is not capable of generating advanced pulsed and an advanced cable is not an option (only the standard cable is available).

TRS Copier Cable

This is the model number of a competitors copy cable. It can be used to deduce information about MFP's that we have not yet connected with an Omega.

Vendor Supplied Harness Kit

This is information about the harness kit required on the actual MFP.

Sister Model

This is information about the other branding options of a given MFP.

The Pharos Blueprint Tracker 4.2 install and uninstall packages have been designed to be compatible with the User Access Control (UAC) and Program Compatibility Assistant (PCA) in both Microsoft Windows Vista and Microsoft Windows 7. However, a bug in Microsoft Windows 7 64-bit can produce an erroneous PCA dialog box during installation of an application. This dialog box states that the "Program might not have installed correctly" and provides options for making the installation compatible. This bug is described in detail in Microsoft KB 978637 (http://support.microsoft.com/kb/978637). This typically only presents itself when the installer is initiated in a 32-bit context, such as may be encountered with many software deployment systems using 32-bit client endpoints.

More often than not, applying the hot fix described in KB 978637 is sufficent for removing the spurious error and deployment can resume (note that this hot fix requires a workstation reboot). However, in some instances when the hot fix is installed, a "This update is not applicable to your computer" message displays and installation will not continue. This hot fix requires that the workstation operating system be validated against Windows Genuine Advantage. If the workstation is not verified, this hot fix will not install. On a workstation-by-workstation basis, this can be done by visiting Microsoft's "Genuine Microsoft Software" site at http://www.microsoft.com/genuine. For larger populations, please consult your Microsoft reseller.

The SmartPAD contains an internal serial port, which can be used to attach a serial card reader. This port is accessed by removing the back of the SmartPAD.

Note: If the customer removes the back of the SmartPAD, it voids the Pharos warranty to the customer. However, Pharos staff are allowed to take the SmartPAD back off to connect a card reader.

The port is a 9-pin RS-232 serial male connector that supports card readers configured to 9600 baud, 8, n, 1 that send an ID string terminated by a non printable char like CR. The DTR pin on the socket can supply 5 Volts at 500 mA to the card reader. The pin-outs for the port are as follows:

Pin Name

1 NC
2 Rx
3 Tx
4 DTR
5 GND
6 NC
7 RTS
8 CTS
9 NC

NC = not connected

SmartPAD software does not support the RTS and CTS signals. No control signals are sent or acknowledged by the DTR pin (pin 4).

All print jobs sent to a queue are being deleted, and an alert is created for each job with the following message:

Print job arrive error on job '[jobname]': CJobCostMethodsLoaderBase::GetDefaultPerJobCost Couldn't find Method ''

How can this be resolved?

This can happen if the queue name in Pharos does not match the printer name in Windows exactly (matching case as well).  The simple way to address this is:

  1. Select the queue in Pharos Administrator.
  2. Append an 'x' to the queue name, and click another field to ensure the change is saved.
  3. Remove the 'x', and then issue a Change Control.

The queue name should now match exactly, and the error should be resolved.

There are two reasons that this message can occur.

The first, and most obvious, is that licenses for Canon iMFPs have actually been exceeded. To resolve this you would either need to set devices as "inactive" making them unusable in the system, or purchase additional licenses.

The second reason, is that any failure of communication between the device and the Pharos EDI (on the Pharos server) will result in this message being displayed. It could be a network "glitch," an issue with the Pharos EDI not functioning properly, or anything that corrupts the data traveling between the Canon and the EDI. In these cases the message displayed is not an accurate description of the problem.

Development is currently investigating this.

In the Pharos Administrator interface, you have to define the IP address of the Fiery device (not the printer's IP; in some cases, when the Fiery is embedded, the IP address for both are the same) and the correct LPR queue name for the destination printer. For all Fiery controllers that were manufactured after 1998, the LPR queue name will be "print" (all lowercase, no quotation marks). Examples of a Device (Uniprint 9.0) and a Terminal (Blueprint 5.1) are shown below:

 

Pharos Uniprint 9.0 Device ConfigurationPharos Blueprint Enterprise 5.1 Terminal Configuration

This can be configured by modifying the "com.pharos.signup.plist" located in the /Library/Preferences folder.  The key is named "Client Cache File Directory".

You can make the change by running this command in Terminal.app (you will be prompted for your password):

sudo defaults write /Library/Preferences/com.pharos.signup "Client Cache File Directory" "PATH"

Be sure to replace PATH with the correct path to your persistent storage area (e.g. the DeepFreeze thawspace).  You will need to restart the machine for this change to take effect.

A problem with printing from Microsoft office applications (Word, Outlook, Excel, Powerpoint) are printed out with jumbled or missing letters. The workstations all have different configurations (Windows XP and 7, Office 2007 and 2010.) They have release their jobs from different printers. If they print directly to the printer and bypass the print server, the documents come out fine. If the document is saved as a PDF and then printed through the Pharos queue, it comes out fine. We have already tried updating/reinstalling/ upgrading Office and the print driver of the affect computers, this does nothing.

 

A sample PDF is attached to this Knowledge Base document. Page 1 is a good print, Page 2 is a print with the problem. The problem gets considerably worse depending on the document and its formatting.

Clearing the "Enable Advanced Printing" option on the driver's properties (on the server queue) "Advanced" tab resolves this formatting problem. An example of this setting is attached to this document.


Prior to Windows XP, this feature was known as "Always Spool in RAW" ... it made more sense, but Microsoft decided that "Advanced Printing" was more applicable, as it enabled potentially more printing options in the WinPrint print processor (multi-sheet printing on one page, for example). In Windows Vista/7/2008 Server, the feature is now called "Client Side Rendering" and is normally enabled for that function.

 

So what does it do? Its fundamental purpose is to force rendering targets in print server-based queues. If checked, the client spools the print job as EMF (Enhanced MetaFile) to the server. At that point, the server has to convert the EMF to whatever PDL (Page Definition Language) the driver is using; normally this is either PCL or PostScript. Rendering to PDL at the server implies that some server resources (like fonts) may be used in the process. If there is a mismatch between any file version between the client and the server, the server's version will win, and this does not often produce desired results. When unchecked, the client does the processing into the PDL. This has several benefits:

 

1. Faster processing at the print server. As the job is already formatted for the PDL, the print server needs only relay the job to the print device (or, in our case, keep the job until it is requested for release).

2. Only local workstation resources are used. Text in documents remains intact without unexpected missing characters, different line breaks, or substitutions.
3. More accurate page counting and job attributes through the PServer service.
4. Improved customer experience.

 

One drawback is that some print drivers that use the WinPrint processor rely on the initial EMF file in order to support certain features like booklet-mode printing or other finishing tasks. Please validate whether your driver(s) are affected by this. If the driver uses a Print Processor that is not WinPrint (see Properties > Advanced > Print Processor), this should not be a problem. Note that some applications (like Adobe Acrobat/Acrobat Reader) send RAW to the print server anyway, regardless of the setting.

After I install Pharos Blueprint Analyst or Collector, the installation test routine fails for both the Tracker Web Service and EDI Web Service. The message for both says "The web service test failed. Client found response content type of 'text / html', But expected 'text / xml'."

You may experience this error message for the Pharos Blueprint web services if another web application is installed on the server hosting Blueprint.

Background

When installing Pharos Blueprint Collector or Analyst, a segment of the installation installs two web applications for the purposes of Tracker function (PharosSystems) and Terminal functions (PharosEDI). These applications run in the 32-bit address space, even on 64-bit systems, through the PharosAppPool application pool/worker process created for IIS.

Definitions

For the purposes of this document, "Third Party" is any non-Pharos web application installed on the core server operating system, including any Microsoft application like SharePoint or WSUS.

Installing Third Party Web Applications

While the Pharos Blueprint Installation documentation does not specifically state this, Pharos Systems does not recommend the installation of other applications on servers hosting the Blueprint Analyst or Collector application. The reasons for this are manifold, and include:

1.    Resource contention by other applications diminishing the user "print" experience. This is a specific risk when the Collector is being used for any of:

a. Preton Toner Savings integration

b. Secure Release Here

c. Policy Print

d. Print job tracking (in other words, no Blueprint Tracker software installed on client workstations)

2. Incompatibility with a Pharos Blueprint function. Antivirus, malware, and security software provide challenges for many of Blueprint's operations, but are considered a necessary component of a stable computing environment. However, other software that provides different functions may interfere with Blueprint to the point where core functions cannot operate. This includes:

a. Altering the normal security settings in a Microsoft IIS implementation

b. Replacing core IIS components and/or files with versions that do not permit normal operation of, or preclude, 32-bit use (on 64-bit systems).

c. Unregistering or modifying COM+ objects, causing the Blueprint web applications to fail.

Resolution

Microsoft WSUS Service

There is a known when installing Pharos Blueprint (Analyst or Collector) on a server that is already installed with Microsoft WSUS. The issue stems from a 64-bit version of suscomp.dll installed by the WSUS role/feature in Windows 2008 R2. The resolution is to find a 32-bit version of suscomp.dll (from another install of WSUS) and copy it to c:\windows \SYSWOW64\ and perform an 'iisreset.' Once that is complete, the Pharos Blueprint Tracker and EDI web services should both pass (if there is a Pharos-supplied SSL certificate bound to TCP 443 in IIS Manager; otherwise, the EDI Service check will fail for lack of a certificate).

Other Web Services

Pharos Systems develops its products to work within the standard framework provided by a normal installation of a supported Microsoft Windows operating system. It is our expectation that the software performs as designed when inside that framework. If the addition of (or presence of) a third party web application causes our software to fail, the short term resolution will be to remove the third party application to restore Blueprint operation, or install Blueprint on a dedicated server.

I am getting an error when attempting to connect to the Pharos database server when installing Uniprint

Image

ERROR: Cannot connect to <server>. Login failed for user 'sa' when logging into SQL Server using Microsoft SQL Server Management Studio.

Image

Uniprint must be installed on a SQL Server that is configured for 'mixed mode' access. This allows both Windows domain users and SQL logins to access the database.

To resolve, log into the SQL Server as the administrative Microsoft domain account credential and:

 

1. Right-click the server name.
2. Choose Properties (at the bottom of the shortcut list).
3. Click the Security option.
4. Select "SQL Server and Windows Authentication" under "Server authentication." Click OK.

Image


5. Restart the SQL Server service as directed by Management Studio.

When trying to start the "Pharos Systems Secure Release Service" it fails to start with an error message Could not start the <Service Name> on the local computer - Error 193: 0xc1

Pharos Systems Secure Release Service is not able to start

 

You may see an error in the Windows Application Event log.
1. "The Pharos Systems Secure Release Service service failed to start due to the following error: Pharos Systems Secure Release Service is not a valid Win32 application."
2. Service cannot be started. The service process could not connect to the service controller. Another error you would see is if you tried to start the service manually.
3. You receive a windows error message stating:
Could not start the <Service Name> on the local computer
Error 193: 0xc1

To fix this issue it was found to change the image path located in the below registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Pharos Systems Secure Release Service

 

Change FROM:
C:/Program Files (x86)/Pharos/SecureRelease/PharosSystems.SecureRelease.SecureReleaseService.exe

 

Note: The changes are the double quotes surrounding the entire string and the slashes going from forward slashes to backward slashes.

Change TO:
“C:\Program Files (x86)\Pharos\SecureRelease\PharosSystems.SecureRelease.SecureReleaseService.exe”

The service should now start correctly.

Cause

This occurs because the print processor defined for the package is not suitable for the workstation it is being installed upon. This normally happens when the package supports both 64- and 32-bit architectures, but is being installed on a CPU bit depth that differs from the Uniprint Print Server (for example: a 64-bit Windows 7 client installs the package, and the Print Server is 32-bit Windows 2003). Some drivers may use different files for the print processor on different architectures.

Resolution

There are two courses of action.

Course 1. Change the Driver's Print Processor

 

Many print drivers can use the standard WinPrint as a print procesor. To change to this print processor, go into Properties for the queue on the Pharos Print Server, click the Advanced tab and click the Print Processor button. From there, choose the WinPrint processor from the list on the left, and then choose Raw from the list on the right (see the attached, PP.JPG). Once complete, rebuild the packages, initiate a change control and install again. If your packages include the Automatic Updater, clients will receive the new driver over time.

The risk with this course is that the manufacturer may have designed the driver to only support certain features through the custom print processor. If this change allows the driver to install, but yields unexpected (or unwanted) results or lack of features, go on to Course 2.

 

Course 2. Modify the Windows Registry for the included Print Processor

 

Rather than switching to Winprint, which can potentially drop printing features, there is an alternative solution you may be able to apply. Also, clients may not update for a day or more, and printing through mismatched print processors can cause failures in the system.

 

On a 32-bit server, go to the Windows Registry and look under HKey_Local_Machine\System\CurrentControlSet\Control\Print\Environments, you will see a number of subkeys. Look under the Windows NT x86\Print Processors key and find the exact name of the print processor (it will be listed as a value for "Driver") that you're using successfully on your 32-bit clients. Then look under Windows x64\Print Processors key and find the x64 equivalent. It will almost certainly be named subtly differently. If you rename the x64 print processor key so that it matches the x86 one, then rebuild the packages, your 64-bit clients should install fine and your 32-bit clients will not need to update.

Note: In order to rebuild the packages correctly, you may need to delete the existing driver modules from the modules subdirectory in your package build location.  The driver modules have filenames beginning with drv_.

Activating Logging
Pharos MobilePrint allows log files to be captured to help administrators when troubleshooting with MobilePrint.
To activate logging:

   1. Click the Show advanced options on the top right corner of the Pharos MobilePrint Web Administrator.
   2. Select Logging from the menu.
   3. Check the Enable box and configure the following settings.
      a. Select the Log Detail
      b. Select the Log to File
      c. Enter the Log folder path.
   4. Once all the settings are configured, click Save Changes.
   5. Restart the MobilePrint Workflow Service for logging settings to take effect.
   6. The log file MobilePrint.Service.Workflow, Version=1.2.0.log is automatically created.

More information about Mobile Print Logging can be found on page 36 of the Pharos MobilePrint  1.2.0 Installation and Configuration Guide.

The Pharos EDI API is protected and copyrighted code that we do not share without a formal agreement with our partners and clients. We can provide your request to business development if you'd like to pursue this capability.  Simply email sales@pharos.com.

This has been seen when using Managed Preferences on the Mac's.

If a machine had managed prefs, it didn't work, if they did not have managed prefs, it worked.

In one case it has been narrowed down to a setting seen in the attached screen shot.  This is under Login Items and an option called "User may add and remove additional items".  If the box is unchecked, printing with Pharos Popups will not print and if it is checked the client is able to print.

Environment

·  Pharos Uniprint v8.3

Symptoms

· Jobs are not successfully sent to printer.

· Job titles at terminal do not match job name.

Cause

In Pharos Uniprint 8.3, print jobs are sent to devices via the Secure Release Service (SRS) whether the queue is Direct or Held. The SRS uses the defined IP address of the Device as an LPR (Line Printer Request) target. Unfortunately, many printers do not support the needed LPD (Line Printer Daemon) service, or handle it poorly. This results in print jobs that are not printed but are billed. The same applies to many devices that are serviced by a front-end Raster Image Processor (RIP), like wide-format printers, that require a specialized port monitor for job transport.

Resolution

To effectively resolve a printer's inability to support an LPRed job, create and share, a printer object that is then used by the SRS as a "pass through" queue:

1) Create a shared printer on the Uniprint machine, and configure it with a port pointing to the RIP server (such ports probably still exist if this machine was upgraded). Keep the share name simple, and do not include any spaces or special characters.

Printer Sharing Tab


2) Modify the Security properties to only allow Administrators (the local group; this will also include, in most cases, Domain Administrators if the server is on a domain) and the special SYSTEM user full control (check all boxes). This prevents a normal user from bypassing Uniprint and printing directly to the device.

Printer Security tab


2) Send a job to this queue and ensure the job prints correctly on the printer or RIP.
3) In Pharos Administrator, create a new Device, using 127.0.0.1 as the device IP address, and set the queue name to the shared name of the printer you just added in step 1. Disable the Online State Check.

Inserting Device in Uniprint

Disabling the Online State Check

No, it cannot.

The Pharos server expects a direct connection from the client printing the job.  If and when a sub-client who is piggy-backing off of a properly connected client prints, the correctly connected host Mac will get the Popup rather than the shared sub-client.

So if Mac A connects to the server properly and shares the printer, and Mac B connects to that share and prints, Mac A will get the Popup rather than Mac B, and the job will fail unless Mac A completes the Popup request.  Furthermore, if Mac A doesn't know Mac B has connected to Mac A's share, Mac A will get seemingly random Popups.

NOTE: To complete the uninstall of the iMFP software you will need access to the Pharos iMFP software that was used for the installation. If you do not have this software in possession, a request to Pharos Support will need to be made to receive a download link for the software. The uninstall software will work for versions 2.9 and older. Please verify your version prior to requesting the software. You can follow the steps below to verify your version.

1.     1. Browse to the webpage of the printer.

2.     2. Select the Pharos Systems button.

3.     3. Under Version, the version you have will be listed next to Pharos Systems Print Service

NOTE: If you have a newer version, please specify the version in the request and we will provide the appropriate uninstall software and instructions.

To Uninstall the Pharos HP iMFP Application on the MFP:

1. Copy the contents of the Pharos HP iMFP Installation Package to a computer running a Windows Operating System. Be sure to maintain the directory structure of the package as supplied.

2. Browse to the "Install" directory of the installation package from Step 1.

3. Double-click on Pharos HP Installer.exe, located in the Install directory of the package.

4. On the installation application, enter the IP address of the target printer and the Administrator Password. (The default name and password for the MFP are both "admin". The name cannot be changed.)

5. Select Uniprint or Blueprint.

6. Click Verify Printer. This checks that the supplied address can be contacted, and that the MFP is a supported model.

7. If the checks are successful, the Remove Pharos Application button is enabled. Click this button to uninstall the components on the MFP. The installer dialog displays the progress of the uninstall.

8. Once the removal is complete, click "Done" to exit the installation application.

NOTE: Due to licensing limitations, this software cannot be provided unless you have a valid license.

The Pharos Ricoh iMFP software is charging for a copy job and then sends four incorrect additional charges through the system. This shows in Pharos reports and in copier logs as well as an external gateway should you have one being used.

Reinstalling the Pharos Ricoh iMFP software briefly corrects this behavior for sometimes as little 5 minutes.  The current version of the Pharos Ricoh iMFP software that this was seen with was Golden Master 1.3.2, what steps can be taken to curb this behavior being seen.

Disabling the "Auto-Off" setting corrects this behavior and the machine should still be able to utilize the Power Save functionality, but it should keep the machine from fully powering down.  What this does is keep the machine from hanging on to one thread and then 'firing' up a parallel thread/process which is the cause of the multiple transactions for one copy job being recorded.

Note: This setting may for "Auto-Off" be in slightly different places on different models.

The Blueprint PrintScout supports installation on Citrix VDI clients, and all features and functions of the PrintScout are supported as well. This means that the following:

  • Policy Print will popup and notify the user correctly when they have triggered a policy
  • Desktop management (deletion) of Secure Release Here jobs
  • Secure Release Here print job delegation
  • Tracking of "local" and print server queue-based jobs

will work. The one caveat to this statement is that there may be normalization issues due to the way print queues can be defined within the Citrix session (in other words, the queues will most likely require manual normalization to a device).

 

Please note that if the Blueprint PrintScout software (any released version as of 10 Oct 2017) is installed with the "/installonbaseimage" switch within the VDI infrastructure, users' policies, delegate selections, and logical printers will be removed and recreated between sessions because the logical definition of the VDI client changes.

Turn Logging On
DiagTool –LoggingOn [-DebugLevel:X]
The tool will enumerate through the PharosSystems registry keys looking for a ‘Log’ key name.
Under this it will enable the TraceLog entry, set the FileName to be a log file named after the parent registry key, which will be stored in the Pharos Logs directory. It will also set other registry logging settings to their default values.
The Profiler will have the ‘Enabled’ log key set to 1.
The optional Debug level command line parameter can be used to override the default value. Valid values of X are from 0 to 10.

 

Turn Logging Off
DiagTool –LoggingOff
The tool will enumerate through the PharosSystems registry keys looking for a ‘Log’ key name.
Under this it will disable the TraceLog entry and remove the logging FileName value.
The Profiler log key will have ‘Enabled’ set to 0.

 

Uninstall the Profiler
DiagTool –UninstallProfiler
This command line option will unhook the Profiler from the Print Spooler, effectively removing our software from the printing pipeline on the machine. Print jobs will no longer be captured.
The tool will first save the current state of the Profiler logging settings then turn on the logging for the Profiler component.
It will attempt to locate the ProfUtil.dll file. If this is unavailable it will try the older Profiler.dll file.
The Profiler Uninstall method will be executed using the command line RunDll32 utility to unhook the profiler.
Logging for the profiler will revert to the previous state.

 

Install the Profiler
DiagTool –InstallProfiler [-Enable]
This command line option will hook the Profiler into the Print Spooler so that jobs will be captured by our sotware.
The tool will first save the current state of the Profiler logging settings then turn on the logging for the Profiler component.
It will attempt to locate the ProfUtil.dll file. If this is unavailable it will try the older Profiler.dll file.
The Profiler Install method will be executed using the command line RunDll32 utility to hook the profiler.
Logging for the profiler will then revert to the previous state.
The optional ‘Enable’ argument will also reenable the profiler as it is installed.

 

Zip Log files
DiagTool –ZipLogs
This command line option will create a zip archive of all *.log files stored within the Pharos Log directory. A Zip file will be created in the users temp directory with a date stamped filename in the format of
PharosLogs_YYMMDDhhmmss.zip

 

Machine Information
DiagTool –PCInfo
This command line option will access the PCInfo COM object, if it has been installed, to obtain the complete set of machine info. This will then be written to a PCInformation.xml file located in the Blueprint Logs directory.

 

Report Tracker Status
DiagTool –Status
This command line option will output the current status of the Print Tracker. This can be extended in future but for now will display the following:
Application installation path
Application Data path
Tracker component version number
Profiler Installed registry key
Profiler Enabled registry key
Profiler Faulted registry key
Counts of the number of files in each of the file Stores

 

Print Server Shortcuts
A Blueprint tracker that was installed with the /PrintServer option is treated as a special case by the Blueprint Tracker. For these machines we will add DiagTool shortcuts to Enable/Disable the Tracker and turn logs On/Off. These shortcuts will not be available under a normal tracker installation.

 

As some of these commands will be run from a shortcut the user will be informed of the operations success or failure via a pop up message box. This message box can be disabled by adding the command line option
/Silent

There is bug within the printer pooling functionality. If the queues that are participating in the pool are set to B&W then load balancing does not occur the way it should.

 

When the queues are set to color load balancing works as expected.

 

As of yet there is no descision as to whether this will either be a hot fix for the current 8.2 version or rolled into the next release which is well along in its development.

To update the License key for Mobile Print please find the quick steps below.

 

Mobile Print 1.3.x

1. Stop the Pharos Mobile Print Services on the primary Mobile Print server (all 4 of them).
2. In the directory "C:\Program Files (x86)\PharosSystems\MobilePrint" (on a 64-bit system) locate the file called 'license.xml' and rename it to something like 'license.xml.old'.
3. Copy your new Mobile Print License key file into the above directory and rename it to 'license.xml'.
4. Restart all the Mobile Print services.
5. On any additional Uniprint Print Servers that have the Mobile Print Worker Service installed stop the Pharos Mobile Print Worker service.
6. Follow the above steps 2, 3 above then restart the Mobile Print Worker Service.
7. Validate Mobile Printing.
Mobile Print 2.0

1. Stop the Pharos Mobile Print Services primary Mobile Print server (all 3 of them).

         Services:

               Pharos Systems MobilePrint Configurator Service

               Pharos Systems MobilePrint Worker Service

               Pharos Systems MobilePrint Workflow Service

2. In the directory "C:\Program Files (x86)\PharosSystems\MobilePrint" (on a 64-bit system) locate the file called 'license.xml' and rename it to something like 'license.xml.old'.

3. Copy your new Mobile Print License key file into the above directory and rename it to 'license.xml'.

4. Restart all the Mobile Print services in the following order.

               i. Pharos Systems MobilePrint Configurator Service

               ii. Pharos Systems MobilePrint Workflow Service

               iii. Pharos Systems MobilePrint Worker Service

5. On any additional Uniprint Print Servers that have the Mobile Print Worker Service installed stop the Pharos Mobile Print Worker service.

6. Follow the above steps 2, 3 above then restart the Mobile Print Worker Service.

7. Validate Mobile Printing.

 

 

 

Mobile Print 2.1

1. Stop the Pharos Mobile Print Services primary Mobile Print server (there are 2).

         Services:

               Pharos Systems MobilePrint Worker Service

               Pharos Systems MobilePrint Workflow Service

2. In the directory "C:\Program Files (x86)\PharosSystems\MobilePrint" (on a 64-bit system) locate the file called 'license.xml' and rename it to something like 'license.xml.old'.

3. Copy your new Mobile Print License key file into the above directory and rename it to 'license.xml'.

4. Restart all the Mobile Print services in the following order.

               i. Pharos Systems MobilePrint Workflow Service

               ii. Pharos Systems MobilePrint Worker Service

5. On any additional Uniprint Print Servers that have the Mobile Print Worker Service installed stop the Pharos Mobile Print Worker service.

6. Follow the above steps 2, 3 above then restart the Mobile Print Worker Service.

7. Validate Mobile Printing.

Problem Installing iMFP for HP from Windows 7?

Problem

When running the stand alone HP iMFP installation application on a Windows 7 box the message "Unable to ping device at xx.xx.xx.xx" appears when the Verify Printer button is pressed. However opening a DOS command prompt and using the ping command from the same machine succeeds.

Solution

The mechanism used in the iMFP for HP installer to ping the printer must be run in Windows XP compatibility mode. To do this:

1. From Windows Explorer navigate to the Install folder of the iMFP for HP release

2. Right click on the Pharos HP Installer.exe application and choose Properties

3. Choose the Compatibility tab

4. Check the box for Run this program in compatibility mode and click OK

** THE MENTION OF UNIPRINT In This Article is not related to our Pharos Uniprint Product **
** Original article can be found here along with several White Paper Links at the bottom of the page **
** http://www.msterminalservices.org/articles/Differences-Universal-Printer-Solutions.html **

For as long as Terminal Servers have existed printing has been one of the biggest challenges when administrating a Server Based Computing environment. To solve these problems several manufacturers developed printing products. These products are all based on a Universal Printer Driver. But what’s universal in this driver? In this article I will explain the differences between several Universal Printer Drivers and show some of the key features in the universal printing products.

Types of Universal Printer Drivers

The term Universal Printer Driver does not mean that all the drivers are universal in the sense that they use the same techniques. The term Universal means that the driver can be used for almost every printing device. When comparing the different printing solutions three types of printer drivers can be distinguished.

1) Universal Printer Driver based on a normal basic printer driver

This was the first printer driver available as a Universal Printer solution. This type of universal printer driver uses a normal standard driver. Often the drivers used are HP drivers like the HP Laserjet 4/5 for black/white printing and the HP Laserjet 4500 for color printing. The printer job is handled and transferred like all common printer drivers.

This is not actually a universal printer driver, but just a replacement driver that will be assigned to other printing devices. This type of driver is, as mentioned, the first type of universal driver and is reaching its end of life.

Citrix used this kind of universal printer driver in former versions of Metaframe/Presentation server (till version 4) and a few full SBC products still use this kind of driver. The Microsoft Fallback driver is also based on this type of universal printer driver.

The advantages of this kind of driver are that it is usually available in the product you have already bought, so no additional investment is needed, and it is easy to maintain.

Because the driver is actually a driver from one of the manufacturers, it does not support all printing devices and has limitations with the tray support and duplex sessions.

2) Universal Printer Driver based on the EMF format

EMF is the Windows format for rendering the print job. The EMF file is normally created by the printer driver and sent to the Windows spooler.

Using the EMF driver the print job will be transferred into the Windows printer format by the printing product to the client. On the client the printer product client receives the EMF file and sends it to the client spooler.

Because EMF is only available within the Windows platform it can only be used by Windows based clients. Also EMF files are usually bigger than PDF based files.

EMF files are rendered for the printing device on the client, so the server has less work. On EMF the job keeps its original quality.

Examples of products that use EMF are Citrix Presentation Server 4, Thinprint and Tricerat (Tricerat uses its own format based on EMF).

3) Universal Printer Driver based on the PDF format

The last common universal driver is based on Adobe’s PDF format.

Using this technique the printing solution renders the EMF file created by the local print spooler into a PDF or sometimes a PCL file. This file is sent to the client where the printing solution client renders the file into the EMF format so the spooler can send the job to the printing device.

The PDF/PCL format is available on most systems, so you do not need to have a Windows based client for this universal printer driver. Also the file is usually smaller than an EMF file so less bandwidth will be used.

Using a PDF solution the job is rendered on the server instead of the client. Also PDF compression affects the print quality. Printing features also depend on the PDF driver being used, while EMF depends on the features available in the client printer driver.

Uniprint and Net2Printer both use the PDF format.

The Provision Network printing product, Print-IT, supports both the PDF and the EMF format.

Citrix Printing solution against third party products

As described above, Citrix was using an alternative printer driver as a Universal Printer driver. Because this did not solve all problems, several third party products were introduced on the market. With Presentation Server 4 Citrix introduced their real Universal Driver solution using the EMF format. The main question during the introduction was if there were still situations were you needed an additional printing product. The printer product manufacturers quickly released white papers where they compared their product with the Citrix implementation and mentioned the advantages of their products.

Some examples are Uniprint and Tricerat.

In the article Can Third Party Software Solve Terminal Server Printing Problems I had described situations where a third party product should be used, so I will not go into those details now.

Considerations choosing a product

In most comparisons and also in the section above, I explained the difference between how EMF and PDF drivers work and the method of how auto created client printers are used. If your clients are in the same LAN, it (in my experience) is not always necessary to send the job first to the client because the client only has server print queues defined. In this case the print job would travel twice around the network. Most network printer products have a built-in feature or an optional module whereby the server side of the product sends the job directly to the print server in your infrastructure. This way you do not need a client for the product to be installed on your client machines.

On the other hand, you could have a central data center where the server resides and your clients are located on several sites connected using a WAN. In this situation, compression and bandwidth control are important factors. Probably a PDF based product has benefits, although all products have compression and bandwidth control options. In this situation you should think about your print server functionality. All products deliver the print job to a spooler component that sends the job to the print device. This part of the total print process is not covered by any product so it travels uncompressed and uncontrolled over your network. In this kind of WAN situation this print component should preferably be located on the client side. Therefore, several products deliver a kind of print gateway.

All the products have their special features and solutions. It is a pretty tough market where the several manufacturers compare their products in white papers regularly. I have included a list of comparison documents at the end of the article.

Conclusion

This article was an introduction into the world of Universal Printing solutions. Three types of universal printer drivers are currently available:

Using a default normal driver
EMF based technology
PDF based technology
Nowadays EMF and PDF based solutions are the standard (certainly now that Citrix has an EMF based solution). Both techniques have their advantages and disadvantages. Depending on your infrastructure you should choose the driver which has the most benefits.

If you are considering a product use this article and the comparison charts mentioned to perform your preliminary analysis. You should then download a few products and test them thoroughly in order to make your final decision.

Why can I not view any reports in Pharos Reports?  It gives me a connection error after I log in.

ODBC Pharos Reports error


The connection to the Pharos Database Server is only used once, at the very start.  The connection is used to verify the user's Pharos credentials, and then simply to fetch the credentials to use to log in to SQL Server.  If you can get into the Reports application and view the list of reports, you're already finished with that connection.

 

From that point on, the Reports application deals directly with the SQL Server via the ODBC DSN called PHAROSReports.  It uses the same credentials that the Pharos Database Server itself uses (usually 'pharos' with a generated password).  Pharos is a 32 bit application, and so it configures the 32 bit odbcad32.exe located in \Windows\SysWOW64.  If the server is a 64 bit server, naturally it will attempt to run the 64 bit version of odbcad32.exe in \Windows\System32.  The DSN in the 64 bit ODBC will more than likely be empty of PHAROSReports configuration information, and it's that portion that will need configuration in order for Pharos Reports to successfully talk directly to the database server.

Microsoft SQL Server 2005 through 2012 offer three Recovery Models: Simple, Full, and Bulk Logged. Of the three, Simple and Full are the most common in normal production environments. Aside from their differences in a backup/recovery scenario, they also affect database performance and disk utilization if not chosen and/or configured correctly. Below follows an explanation of both Simple and Full recovery models, and their impact on performance and disk utilization.

Simple Recovery Model. The real impact of the Simple Recovery model is that the database is only as good as the last backup. Transactions (inserts to, updates against, deletions of, and other data activities) are committed almost immediately to the database. The benefit is that the amount of disk space required by the SQL Transaction Log (the transaction log is a serial record of all the transactions that have been performed against the database since the transaction log was last backed up) is minimal, and usually only gets large when numerous transactions (bulk inserts, mass deletions) are occurring. Not having to maintain an active transaction history also speeds the performance of the SQL database, since more processing time can be used for queries and tasks versus managing the log. However, this all comes at the risk of catastrophic data loss (potentially, an entire days' worth or more), depending on the cadence of database backups and their success rate.

Full Recovery Model. The Full Recovery model, when managed properly, allows a database to be restored to a definite point in time, utilizing the information in the transaction log (and backed up transaction logs) to arrive at that point. For example, if a large set of data was inadvertantly inserted or deleted from the database, the full recovery model would allow the restoration of the database to the time right before that action occurred (this would only be possible in a Simple model if the database was first backed up prior to engaging the action). The price for this ability is that the SQL Server must be managed more than many organizations are able, or want, to commit themselves. Most importantly, a regimented back up of the transaction log is required (Microsoft TechNet article http://msdn.microsoft.com/en-us/library/aa173551%28v=sql.80%29.aspx does a great job of outlining a sample plan). This allows the transaction log to remain small enough for continued database performance, but with enough information to readily recover from a database mishap.

If a regular transaction log back up does not occur, it is very possible to reach the point where database response to even simple queries is painfully slow, and/or the disk housing the log file runs out of space (remember, the transactions are only trimmed when the log file is backed up).

For a good jumping point, please visit the Microsoft article on Recovery Models for SQL Server, at http://msdn.microsoft.com/en-us/library/ms189275.aspx

Impact With Pharos Blueprint and Uniprint

By default, databases for Pharos Blueprint and Uniprint are built using the Full Recovery Model. Further, when installing on Standard or better (not Express) SQL Server editions, a SQL Agent job is created that will at least make sure that a regular backup transaction log file is managed. However, SQL Agent on many machines is disabled or not started (sometimes as a SQL Server security measure), and so the backup does not occur without some third-party or manual intervention, and the transaction log file grows bigger and bigger until performance and disk space suffer.

What To Do?

If your organization is already managing Full recovery mode databases, then keeping the Full recovery model selected is wise. However, if answers to the question "How do we manage disaster recovery for our SQL databases?" draws blank stares, giggles, or unanswered email, it is best to configure the database for the Simple recovery model, and make sure that some regular "full backup" is performed, and the resulting backup file stored somewhere safe.

To engage Simple recovery, run the following SQL command as a user logged in with "sysadmin" privilege:

USE master;

 

ALTER DATABASE <DatabaseName>
SET RECOVERY SIMPLE;

Be sure to swap out <DatabaseName> with your database name (do not include the < > characters) and execute. Within Blueprint, you will have to do this to the following databases:

> psbprint

> psjobs1 - ? (depending on your installation settings and organization size, this may be up to psjobs4 or psjobs13 or more)

> psreports (if using Pharos Blueprint v5.0 or greater)

In Uniprint, you simply have to worry about the 'pharos' database.

Solution:
In order for you to create a custom report you need to purchase full version of Crystal Reports. Having a full version of Crystal Reports will allow you to modify existing reports or create new reports.

Reports are standard Crystal Reports .rpt files, and as such can be modified with Seagate Crystal Reports. When modifying reports, first make a copy of the report and place it in the Custom directory (without changing its name), then make the modifications. If Pharos Reports detects a report in the Custom directory with the same name as one in the Standard directory, the Custom report is used instead of the Standard one. In an upgrade, only reports in the Standard directory will be overwritten; any customizations will not be affected.

The following information is taken from the Pharos TechNote "Pharos Database Structure: Reports Tables":

 

Pharos Database Structure: Reports Tables

 


Pharos uses a SQL Server database to hold both configuration information about the system and historical information recording how the system is being used. With the release of Pharos Version 5.0 and the introduction of the new Pharos Reports application, a series of SQL views were created that expose the core tables in the Pharos database. The purpose of this paper is to document the interface to these new SQL views and suggest how clients may use them to generate their own custom reports with Seagate Crystal Reports.
SQL Views
The core table in the Pharos database that records historical information about how the system is being used is the “transactions” table. The information that is recorded in this table varies according to the type of transaction i.e. credit, print, transfer and so forth. For example, a print transaction records the printer where a print job is released, the number of pages/sheets printed and the associated cost of the job. A credit transaction records the Cashier responsible for raising the transaction and the amount of money credited to the user. Some information in the transactions table is common to all transaction types, such as the server where the transaction was raised, the user associated with the transaction and the Pharos bank used for charging.

 

The SQL views on the transactions table resolve the foreign key relationships for the different transaction types and expose a structure that can be queried in much the same way as queries against ordinary tables. The SQL views created for Pharos Reports V5.0 include, in order of importance:

 

® rpt_transactions
® rpt_print_transactions
® rpt_credit_transactions
® rpt_copy_transactions
® rpt_printop_transactions
® rpt_transfer_transactions
® rpt_users
® rpt_groups
® rpt_alerts

 

These views are described later in this document.
Notes
® The SQL views use column names that contain spaces, which means that SQL queries against these views need to “qualify” the column names. For example, the following query that can be run through SQL Query Analyzer uses square brackets [] to identify the column names.
select
[User ID], [Quantity], [Amount Charged]
from rpt_transactions

 

® Double quotes can also be used to identify column names so long as the connection being used to access the database has the “Use ANSI quoted identifiers” configuration option checked ON. This is the setting required for the Seagate Crystal Reports that use the Pharos Reports ODBC data source.

 

® The SQL views exposed for Pharos Reports are built up by joining across multiple tables from the underlying database and should only be used to retrieve data for reports. They should not be used in INSERT, UPDATE or DELETE statements.

 

® When generating custom reports Pharos recommends that as much processing of the results as possible is carried out in the query that is executed on the SQL Server. This reduces the information passed down to the client running the report. If creating custom reports using Seagate Crystal Reports, we recommend that the option “Perform Grouping on Server” is checked ON: found under File > Options > Database > Advanced Options.
Accessing the SQL Server
Pharos Reports uses the same SQL logon and password that is used by the Pharos Database Server to connect to the SQL Server. This SQL logon is the ‘dbo’ for the ‘pharos’ database and has full access to all objects in the database. Any custom report application that uses a different method of authentication against the SQL Server will need to have appropriate access and permissions configured against the ‘pharos’ database.
Creating a Specific Reporting Login
If required, a specific reporting login can be created using SQL Server Enterprise Manager under the Security > Logins context of the SQL Server running the 'pharos' database.

 

When creating the Login, set the default database to the 'pharos' database and select the 'pharos' database under Database Access. At this point the Login is automatically assigned the 'public' role in the 'pharos' database, which allows the user to connect to the database but does not allow the user to query any of the tables or views. If the new login is only going to query against the SQL views created for PHAROS Reports then we recommend that the login is given the 'db_datareader' role under Database Access. Alternatively, set up SELECT permissions for the new login against the specific tables or views that are to be accessed by the custom reports, but note that these permissions need to be reset after any upgrade to the 'pharos' database.
Detailed View Descriptions
rpt_transactions
Description: Report view on transactions table, with common foreign key references resolved

 

Column Type Nullable Description
Transaction ID int Not Null Unique identifier of transaction
Date/Time datetime Not Null Date and time when the transaction was recorded
User ID varchar(255) Null The logon ID of the User associated with the transaction
User Group varchar(255) Null The name of the User Group to which User belongs
Cost Center varchar(649) Null The expanded name of the Cost Center associated with the transaction
Transaction Type varchar(67) Null Transaction type with Resource Name resolved from resources table: Credit Print Computer (Resource Name) Application (Resource Name) Transfer Funds Copy PrintOpJob
Server varchar(32) Not Null The name of the Server on which the transaction was recorded
Bank varchar(64) Null The name of the Bank against which the transaction was recorded
Charging Type varchar(11) Null Flag indicating where the money was debited: Internal, External, or Cost Center
External Billing varchar(7) Null Flag indicating whether external billing was online or offline
Quantity int Null The number of units associated with the transaction (pages, prints)
Quantity Name varchar(32) Null The display name for the transaction quantity: Pages Prints Minutes
Amount Charged money Not Null The amount charged against the transaction

 

rpt_print_transactions
Description: Report view on transactions table filtered against 'Print' transactions

 

Column Type Nullable Description
Transaction ID int Not Null Unique identifier of transaction
Date/Time datetime Not Null Date and time when the transaction was recorded
User ID varchar(255) Null The logon ID of the User associated with the transaction
User Group varchar(255) Null The name of the User Group to which User belongs
Cost Center varchar(649) Null The expanded name of the Cost Center associated with the transaction
Server varchar(32) Not Null The name of the Server on which the transaction was recorded
Bank varchar(64) Null The name of the Bank against which the transaction was recorded
Charging Type varchar(11) Null Flag indicating where the money was credited: Internal, External or Cost Center
External Billing varchar(7) Null Indicates whether external billing system was Online or Offline when transaction was raised.
\\Server\Printer varchar(67) Not Null The name of the Printer or MFD associated with the transaction
Pages int Null The number of pages recorded against the transaction
Sheets int Null The number of sheets recorded against the transaction
Amount Charged money Not Null The amount charged against the transaction

 

rpt_credit_transactions
Description: Report view on transactions table filtered against 'Credit' transactions

 

Column Type Nullable Description
Transaction ID int Not Null Unique identifier of transaction
Date/Time datetime Not Null Date and time when the transaction was recorded
User ID varchar(255) Null The logon ID of the User associated with the transaction
User Group varchar(255) Null The name of the User Group to which User belongs
Cashier varchar(255) Not Null The name of the Cashier User that raised the transaction
Server varchar(32) Not Null The name of the Server on which the transaction was recorded
Bank varchar(64) Null The name of the Bank against which the transaction was recorded
Charging Type varchar(8) Null Flag indicating where the money was credited: Internal or External
Purse Name varchar(32) Null The name of the Purse against which the credit transaction was raised
Amount Charged money Not Null The amount charged against the transaction

 

rpt_copy_transactions
Description: Report view on transactions table filtered against 'Copy' transactions

 

Column Type Nullable Description
Transaction ID int Not Null Unique identifier of transaction
Date/Time datetime Not Null Date and time when the transaction was recorded
User ID varchar(255) Null The logon ID of the User associated with the transaction
User Group varchar(255) Null The name of the User Group to which User belongs
Cost Center varchar(649) Null The expanded name of the Cost Center associated with the transaction
Server varchar(32) Not Null The name of the Server on which the transaction was recorded
Bank varchar(64) Null The name of the Bank against which the transaction was recorded
Charging Type varchar(11) Null Flag indicating where the money was credited: Internal, External or Cost Center
External Billing varchar(7) Null Indicates whether external billing system was Online or Offline when transaction was raised
Copier varchar(32) Null The name of the Copier or MFD associated with the transaction
Prints int Null The number of prints recorded against the transaction
Amount Charged money Not Null The amount charged against the transaction

 

rpt_printop_transactions
Description: Report view on transactions table filtered against 'PrintOp' transactions

 

Column Type Nullable Description
Transaction ID int Not Null Unique identifier of transaction
Date/Time datetime Not Null Date and time when the transaction was recorded
User ID varchar(255) Null The logon ID of the User associated with the transaction
User Group varchar(255) Null The name of the User Group to which User belongs
Cost Center varchar(649) Null The expanded name of the Cost Center associated with the transaction
Server varchar(32) Not Null The name of the Server on which the transaction was recorded
Bank varchar(64) Null The name of the Bank against which the transaction was recorded
Charging Type varchar(11) Null Flag indicating where the money was credited: Internal, External or Cost Center
PrintOp Station varchar(32) Not Null The name of the PrintOp Station where the PrintOp job was processed
Spool Queue varchar(32) Not Null The name of the PrintOp Spool Queue to which the original PrintOp Job was passed
Job Name varchar(255) Null The name of the PrintOp Job that was passed to PrintOp Spool Queue
Number of Copies int Not Null The number of copies of the PrintOp Job that were printed
Pages int Null The number of pages recorded against the transaction (all copies)
Sheets int Null The number of sheets
Amount Charged money Not Null The amount charged against the transaction

 

rpt_transfer_transactions
Description: Report view on transactions table filtered against 'Transfer' transactions

 

Column Type Nullable Description
Transaction ID int Not Null Unique identifier of transaction
Date/Time datetime Not Null Date and time when the transaction was recorded
User ID varchar(255) Null The logon ID of the User associated with the transaction
User Group varchar(255) Null The name of the User Group to which User belongs
Pharos Station varchar(32) Not Null The name of the Pharos Station where the Transfer transaction was generated
Server varchar(32) Not Null The name of the Server on which the transaction was recorded
Bank varchar(64) Null The name of the Bank against which the transaction was recorded
Charging Type varchar(8) Null Flag indicating where the money was credited: Internal (only)
Purse Name varchar(32) Not Null The name of the Purse against which the transfer transaction was raised. (Always against Purse 3)
Amount Charged money Not Null The amount charged against the transaction

 

rpt_users
Description: Report view on people table filtered by 'User' type

 

Column Type Nullable Description
User ID varchar(255) Not Null User’s logon ID
First Names varchar(50) Null User’s first names
Last Name varchar(30) Null User’s last name
Middle Initial char(1) Null User’s middle initial
User Alias varchar(32) Not Null Alternative identifier for User displayed on Pharos Clients and Pharos Station
User Group varchar(255) Null The name of the User Group to which the User belongs
Access Level varchar(20) Not Null The User’s access level:Administrator, Proctor, Cashier or User
Billing Option varchar(10) Not Null The User’s billing option: Advance or Arrears
Discount Rate varchar(77) Null The name of the discount rate that applies to the User. The name is followed by (User) if the rate is directly associated with the User, or (Group) if rate is inherited from the Users User Group
Active? tinyint Not Null Whether the User’s account is active: Yes or No
Address varchar(255) Null User’s address
Phone varchar(30) Null User’s phone number
Purse 1 Balance money Not Null User balance in Purse 1
Purse 2 Balance money Not Null User balance in Purse 2
Purse 3 Balance money Not Null User balance in Purse 3
Purse 1 Name varchar(32) Null Display name for Purse 1
Purse 2 Name varchar(32) Null Display name for Purse 2
Purse 3 Name varchar(32) Null Display name for Purse 3

 

rpt_groups
Description: Report view on people table filtered by 'Group' type

 

Column Type Nullable Description
Group Name varchar(255) Not Null The name of the User Group
Discount Rate varchar(64) Null The name of the discount rate that applies to members of the User Group
Number of Members int Null The number of Users that belong to the User Group
rpt_alerts
Description: Report view on alerts table

 

Column Type Nullable Description
Server varchar(32) Not Null The name of the server that raised the Alert
Date/Time datetime Not Null The date and time when the Alert was raised
Severity varchar(32) Not Null The severity of the Alert: Information, Auditing, Warning, Error or Fatal
Service Type varchar(32) Not Null The type of service on the server that raised the Alert e.g. PSPrintSvr
Error Code int Not Null The error code associated with Alert, identifying in greater detail where the error was generated
Client varchar(32) Null The hostname of the Client machine that raised the Alert
User varchar(255) Null The logon ID of the User recorded against the Alert
Operation varchar(32) Null Detail of the operation that caused the Alert
Item varchar(255) Null The object associated with the operation e.g. PrintJob
Message varchar(255) Not Null Text of the error message recorded against the Alert
Important
Access to the SQL views should be on a read-only basis. Modifying data in the Pharos database by any means other than using standard Pharos applications is not recommended and could result in system instabilities.

When using the Pharos HP iMFP Software 2.8.1 and the 'Scan To Email' with auto population of the FROM and TO fields the Card Identifier for the user (pin code) is listed in the FROM and TO fields instead of the email address.

I have double checked that the user has an Email Address configured and I have tested the authentication script and can validate that the script does return the correct Email Address for the user.

The Full Name field needs to be populated for the Employee record in the Blueprint Administrator.

It is possible to create custom modules for to perform any additional functions outside of the standard modules e.g. setting a printer to default using a registry batch file. To do this you need to do the following:

 

Create the Module executable:

 

You need to do this, but it is the exe to be run on the command line on the client (must be exe).

 

File management:

 

Put the new executable in the C:\program files\pharos\Bin\PackageCreator\StaticModules\ directory.

 

Enter the new module into SQL (via SQL Query Analyzer:

 

insert into modules (type, identifier, os, filename) values (1, '<name of the new module>, 8, <filename exe>)

 

8 = windows XP and 2000

 

Tip for 7.0
The executable needs to be a stamped version but in 7.1 or higher this does not matter

This is normally not possible. Uniprint was designed with a Domain or Enterprise environment in mind. When building the PopUp package, it's built with the server name that's entered in Pharos, and if that's not resolvable, it won't print, and PopUps will not have the ability to function as desired.

However if your DNS is configured such that clients outside your Windows Domain can resolve IP's to host names that re inside your Windows Domain then potentially they may work. Networking and routing also play a big factor in the communications between the Pharos Popu Client and the Pharos Server components.

While Blueprint can use an IP address is to designate the "Server Hostname/Address" in the Blueprint Server Configuration utility, we highly recommend that the IP address not be used for that purpose. Instead, the hostname (fully qualified or otherwise) is acceptable in that field and can be changed. We do require that the Hostname be resolvable in DNS. If the new Hostname does not resolve correctly, it must be corrected before any configuration/reconfiguration can continue.

Changing the Blueprint Server IP Address

If the server's IP address needs to be changed, follow these steps:

1. Change the IP address.

2. Test that the IP address resolves to the host name (use PING -a IPAddress; for example: PING -a 10.0.1.50. You should receive a reply that indicates the proper host name as defined in the Blueprint Server Configuration utility).

3. Launch the Blueprint Server Configuration utility and click File > Re-apply Settings. This causes the Blueprint server settings to be recompiled, the Pharos services to restart, and the configuration Test to run.

The test should run without failure or prompt.

Changing the Blueprint Server Host Name

 

Below are the steps you need to rename the Server and then re-configure the Analyst.

 

1. Change hostname on server through Windows OS and do not reboot the server when asked at this time. Instead, wait.

 

2. Open the Blueprint Server Configuration tool and make the hostname change there and click the 'Apply' button. The  settings will be applied and you will most likely see some of the tests fail when the testing screen pops up and you will  get an error about "Unable to udate the health status of the server" due to the PharosSystems TaskMaster service probably  not running. Acknowledge the error and click close on the dialogs.

 

3. Reboot the server.

 

4. Once you login to the server again you will need to open the Blueprint Server Configuration tool again and this time it  will prompt you with the attached screen shot.

 

5. Once this is all complete you will need to request an SSL Certificate from Pharos Technical Support with the new name to be applied to the  system as the old one will no longer be valid.

 


Other items to be aware of:

 

1. If you deployed a Tracker package referencing this Blueprint Server, you will need to redeploy a new Tracker package to be installed on the client machines. You can Upgrade the install package or uninstall the old then install the new.

 

2. You must go to each Collector and provide the new Hostname of the Analyst as its "Parent Server". (see attached screen shot), then click the test and update button.

 

You have successfully changed the Analyst's hostname and/or IP address.

The job name is gathered from the operating system, not the spool file. If you look in the print queue window for a printer you see the document name. That is the one that Blueprint uses.

CAUSE

This error occurs because of a defect in the uninstaller program. osql.exe is a program used for connecting to databases, and comes with Microsoft SQL Server. Depending on your configuration, the Uniprint Installer may or may not install a copy of osql.exe within the Pharos installation directory. The uninstaller decides whether to use the copy in the Pharos installation directory or the copy in the Microsoft SQL Server directory. If the uninstaller uses the copy in the Pharos installation directory, it removes that copy when it has finished uninstalling the Pharos Database. However, due to an defect in the uninstaller, it actually removes the copy of osql.exe that it uses, wherever that copy is located. This error generally occurs if all the letters in the computer's name are in upper case.

SOLUTION

If the problem is discovered only after the uninstaller has been run and osql.exe has been deleted, the only remedies are to copy osql.exe from a known-good copy of the same version of Microsoft SQL Server as is installed or to uninstall and re-install Microsoft SQL Server.

If the problem is anticipated, the removal of osql.exe may be remedied by finding the file before running the uninstaller, making a copy of the file, running the uninstaller, then replacing the file from the copy.

An alternate solution involves editing the Windows Registry. On the Principal Server computer, the registry value HKEY_LOCAL_MACHINE\SOFTWARE\Pharos\Database Server\Host Address contains the name of the computer. Edit the value to replace the upper case letters with corresponding lower case letters, while taking care to ensure that the value is not changed in any other way. This causes the uninstaller to expect to find osql.exe in the Pharos installation directory; copy osql.exe there, as described in the solution to the first problem described in this article, then run the installer. This alternate solution will not work if the registry value is absent because the Database Server has already been uninstalled (as is likely to be the case if this is a second attempt at uninstalling after failing to find the file the first time), nor if the computer's name does not contain any letters at all.

The uninstaller issue affects computers named with lowercase letters differently.  Please see this related article for details.

Open the printer properties through your favourite Windows mechanism, and check the spool settings on the Advanced tab.  If the printer is set to "Print directly to the printer", change it to "Spool print documents so program finishes printing faster".

This allows the Print Server to finish all processing of the job before handing it off to the Windows spooler.

Blackboard transactions are failing with "Transaction failed - unknown error (#244) or (#224)" in the Blackboard Gateway log file however print jobs may still print but not get charged.

 

"Transaction failed - unknown error (#244)" or (#224)

 

When trying to release a print job at a Pharos Station or Terminal Device you may recieve this error message when trying to "Print" the job. When you click on the "OK" button in the error message, the job does in fact prints, however, the document is not removed from the print job queue and no money is deducted from the user's account.

 

Pharos Alert:
Failed to repay offline transaction for LogonID, "", with card ID,";1234567899?" for amount, "-0.5", on, "2009/03/23-11:48:48", because:"Transaction failed. Unknown Error(Code = 244)

 

IpBiller Log file (snippet):
[01/Apr/09 13:51:06:796 P1912 T6640C00001 d] Number of items in contents:5
[01/Apr/09 13:51:06:812 P1912 T6640C00001 d] Version number: 2
[01/Apr/09 13:51:06:812 P1912 T6640C00001 d] Message type: 1
[01/Apr/09 13:51:06:812 P1912 T6640C00001 d] Sequence Number: 36542
[01/Apr/09 13:51:06:812 P1912 T6640C00001 d] Response code: 244
[01/Apr/09 13:51:06:812 P1912 T6640C00001 d] Display text: Undefined Error
[01/Apr/09 13:51:06:812 P1912 T6640C00001 d] Transaction failed. Unknown Error(Code = 244).
[01/Apr/09 13:51:06:812 P1912 T6640C00001 i] Reply IP Biller:CMD_FAIL[#28]Transaction failed. Unknown Error(Code = 244). To solve this problem the customer will have to contact Blackboard Technical Support.

 

A Blackboard "Tender" issue causing an unknown error code to be be returned from the gateway. The "Printing Tender" was re-created on the Blackboard side of the system and this resolved the issue.

 

This is not an error returned by Pharos but by Blackboard so consultation with Blackboard on this error will be needed.

The Pharos Remote bank does not correctly provide the standard "User level" parameter to executable logon plug-ins. This causes standard Pharos plug-ins (e.g. the ADLDAP or LDAP plug-ins) to fail when trying to log in to Pharos Remote.

A simple workaround can be used to address this issue. Create a batch file in the same location as your plug-in, and assign that batch file to the Pharos Remote Bank's logon event. The content of the batch file should be as follows:

@echo off
set plugin=adldaplogon.exe
"%~dp0%plugin%" %1 User %2 %3

Be sure to change the plugin variable to match your desired plug-in.

This issue may be fixed in a future release, at which point this solution will no longer work correctly. If you use this solution, be sure to check Remote authentication after any Uniprint upgrade, or update of the Pharos Print Server.

Note that users of an appropriate level must also exist in Pharos Administrator as well as the external system. If you wish to handle administrative users without creating them in the Pharos database first, you will need a more complicated logon script.

Often a Uniprint script is used to create users at login time, and can also be applied to the Pharos Remote Bank. The issue described does not affect such scripts, only cases where the executable has been assigned directly to the bank's logon event.

The most likely reason is that the user who has launched the PC Pharos Release Station does not have permission to write to the directory that the Pharos PC Station is configured for its log. By default this path is C:\Program Files\Pharos\Temp\pstation.log.txt

Locate the path configured as the log file of the PC Pharos Release Station:

1. Open the Windows Registry Editor on the workstation running PC Pharos Release Station.
2. Navigate to the registry path below depending on the architecture of the machine.
     a. 32-bit = HKEY_LOCAL_MACHINE\SOFTWARE\Pharos\Station\Log\Filename
     b. 64-bit = HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Pharos\Station\Log\Filename

Choose one of the solutions below.

  1. Run the PC Pharos Release Station as a user who has permission to write to C:\Program Files\Pharos\Temp\pstation.log.txt
  2. Change the path configured as the log file of the PC Pharos Release Station.
    • Open the Windows Registry Editor
    • Locate the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Pharos\Station\Log\Filename, or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Pharos\Station\Log\Filename
    • The key named "Filename" is absolute file path of the log file.  Change file path to a location where users have permission to write files.
  3. Disable logging by the PC Pharos Release Station.
    • Open the Windows Registry Editor
    • Locate the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Pharos\Station\Log\Filename, or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Pharos\Station\Log\Filename
    • Edit the key named "Filename" and clear its value, i.e. leave it blank
    • Logging for the PC Pharos Release Station is disabled when its log file path is blank.

The attached PDF file describes all of the Pharos Uniprint alert and error codes. Each code in the first several pages is hyperlinked to its description later in the document.

 

Please See attached document.


When submitting a Secure Release (or held) job to a clustered Uniprint 8.3 Print Server, the queue goes into an "Error" status, as does the print job. When I review the SecurePort log, I see the following:

"Server was unable to process the print job. See server logs for error."

The PrintService log (referred to by the SecurePort log) shows this for the same entry:

"[JobReceiver] (-AddJob.Failed-) Job Id:f7c6500b-046d-4578-8bde-9cce986e1ee0(0) Input string was not in a correct format."

What is happening?

The reason that this (otherwise unhelpful) message appears is due to a missing registry key "HKEY_LOCAL_MACHINE\Software\Pharos\Print Server\Next Job Id". This is created as a 'DWORD' type when the Secure Release Service is started for the first time.

In a cluster server environment, a technology called Registry Checkpoint is used to sync the Windows Registry between nodes. Because of this feature, any changes to a Registry key while the service is offline is reverted to the previous checkpoint when the service starts up. In the case of the Secure Release Service, it starts up first (due to dependency) and creates the Next Job Id key correctly. However, when the Print Server starts up, that change is rolled back since it is occurred while the Print Server service was offline. This is why there was no Next Job Id key.

The resolution is to manually create the registry key "HKEY_LOCAL_MACHINE\Software\Pharos\Print Server\Next Job Id" (on a 64-bit system this will be in "HKEY_LOCAL_MACHINE\Software\Wow63432Node\Pharos\Print Server\") on the active node. Then either restart the server or Secure Release Service. Users will now be able to submit and release print Jobs from this server. Ensure that this key also exists on the other node(s) when they are the active node for the cluster.

NOTE: This will be corrected in a future service pack, and currently affects PServer.exe for the original 8.3 release and Service Pack 1.

Upgrading Trackers

Trackers are upgraded using upgrade packages. These are created and deployed in the same way as standard install packages (refer to the “Blueprint Installation Guide”). Simply select the Upgrade action instead of Install when creating a package.

When creating an upgrade package, you should also create new installation and uninstallation packages. The new installation package should be used for new workstations.

Handling New and Existing Workstations

A Tracker upgrade package will only perform an upgrade. If the Tracker is not already installed, the upgrade package will exit without installing the Tracker.

To handle the scenario where existing workstations need to be upgraded and new workstations need to be installed, you will need to ensure that the original installation package is still deployed to any new workstations (e.g. if you have created a deployment package in SMS). The installation package should be pushed to the new workstation before the upgrade package is pushed.

Alternatively, a new combined deployment package could be created. The package would check for the presence of the Tracker. If a Tracker is not detected, the Tracker installation package is used. If a Tracker is detected, the Tracker upgrade package is used. Both the Tracker installation and Tracker upgrade packages should be of the same version. Use a deployment tool (e.g. SMS) to ensure that the combined deployment package is run only once on each workstation; otherwise, the deployment package will constantly attempt to upgrade a workstation.

To detect if a Tracker is already installed, you can:

  • Check the Windows services for a “Pharos ComTaskMaster” service.
  • Check the registry for the key: HKEY_LOCAL_MACHINE\Software\PharosSystems\InstalledComponents\Tracker

Note: For 3.1 and 3.2 Trackers, you can detect that a Tracker is installed by checking the registry
HKEY_LOCAL_MACHINE\Software\PharosSystems\InstalledComponents\3100

Upgrading Trackers on Cluster

The following are the steps required when upgrading a clustered 3.5 Release 2 Print Server Tracker to Blueprint 4.2:

  1. Using the Cluster Administrator, take the “Pharos ComTaskMaster” resource offline.
  2. Open the Services Manager on the first node and record the domain account that the “Pharos Systems ComTaskMaster” is running under. It is assumed that you know the password for this account.
  3. Run the upgrade package on the first node.
  4. Open the Services Manager on the first node and select the “Pharos Systems ComTaskMaster” service. Change the startup type to “Manual” and configure the logon account back to the domain account recorded in step 2.
  5. Fail over the cluster to the second node.
  6. Run the upgrade package on the second node.
  7. Open the Services Manager on the first node and select the “Pharos Systems ComTaskMaster” service. Change the startup type to “Manual” and configure the logon account back to the domain account recorded in step 2.
  8. Using the Cluster Administrator, bring the “Pharos ComTaskMaster” resource back online.

If data from Trackers on multiple languages is being sent to a single server, the characters will display correctly as long as those languages are installed on the server. Extra languages are installed at Start Menu > Control Panel > Regional and Language Options.

 

If your Blueprint Tracker install packages are created on a non-English server, the language pack for the server's language must be installed on all client workstations that the packages are run on. If the language pack is not present, the packages will not run.