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

Knowledge Base & Downloads

August 1, 2013 Previous day Next day

All Pharos-supplied modules produce a file called results.txt, which contains information about the success or failure of the module's install. Custom modules can produce a results.txt file as well. However, if this error occurs the custom module does not create this file.

To stop this error and allow the package to install successfully open Pharos Administrator and go to:

Distribution System->Packages->Custom Modules->Select the module->Module Behavior (on properties tab) and check “Module does not write results.txt file”

This happens when an Analyst/Collector loses connectivity to a device depending on where the queue is located. The reason is that the thread that is responsible for keeping this connection alive never times out, which leads our software to believe that there is a true connection to the device.

Troubleshooting:
1)     Restart the Pharos Systems TaskMaster
2)     Run Debugview to monitor activity
3)     Print a Test Job through
4)     Release the printed job through the Print Troubleshooting menu under Secure Release Here on the server
5)     Note the name of the printed test job
6)     Turn off Auto Scroll in Debugview(Ctrl + A)
7)     Trace the printed job through in Debugview and you should see a call being made on the printed job i.e OnDevicePrintQueuePrintJobCompleted] Updating job 'Test Page'  note: 'Test Page' would be the name of the job.
8)     If the OnDevicePrintQueuePrintJobCompleted call is made on a print job, it means it has successfully printed the job through

 

Future Prevention:

Back up the existing GlobalConfig file to a secure location before making changes.
Edit the SendTimeout and ReceiveTimeout settings in the GlobalConfig file to 120000. Keep in mind that the unit for timeout is in milliseconds.

<LprConfig ConfigVersion="3.3">
      <ConnectTimeout>30000</ConnectTimeout>
      <SendTimeout>120000</SendTimeout>
      <ReceiveTimeout>120000</ReceiveTimeout>
      <UseStrictLprSourcePorts>false</UseStrictLprSourcePorts>
    </LprConfig>

 

Restart the Pharos Systems TaskMaster to apply the new settings.

The following alert appears in Pharos Administrator:

Error Code 29060 "Error while setting KEEPPRINTEDJOBS printer attribute: The printer name is invalid"

What do I need to do to resolve this problem?

A screen shot of the error is attached.

Cause:

The reason you receive this error is because one or more of the Windows printer objects in Pharos has been removed from the Windows Printer folder (Printers and Faxes).

Solution:

To resolve this issue you need to re-install the deleted printer. The steps are as follows:

1. The general tab of the alert will include the name of the device that was deleted. Note down the name and open the Control Panel > Printers screen.
3. Click the Add Printer button.
4. Install a printer with the same name as listed in the above alert, with the correct drivers and port.
5. Restart the Pharos Print Server service.

The alerts in the Pharos Administrator should stop and the printer should correctly appear in Pharos Administrator.

Popups can fail for a number of reasons, and it's important to understand how printing through Popups works within Pharos.

The client submits a job to the server.  The first one to receive the print job is the Popup server.  We therefore, need to make sure communication to the Popup Server is intact.  The communication is made of two parts:

  • The server name or IP address
  • The IP port on which the Popup Server listens (28203)

The server name will either be the short NETBIOS name, or the FQDN (Fully Qualified Domain Name).  Both the short name and the FQDN rely on DNS to get the IP address, so we have to make sure DNS gives the right IP address.  This can be done on the Mac using the terminal (/Applications/Utilities/Terminal) using

  • nslookup [servername]

or

  • ping [servername]

Please replace [servername] with the short name or FQDN, without brackets, whichever was used to create the queue on the Mac, and confirm that the IP address given back is the correct IP address for the server.

If the IP address is correct, then the next step would be to verify we can send a packet over port 28203 to the server.  The test, again through The Terminal (under /Applications/Utilities) , would be to type:

telnet [servername] 28203

This will quickly fail if communication to the server is blocked, and will result in a FAILED output.  This will mean somewhere along the way to the server, or perhaps at the server itself, 28203 is either not listening or blocked by the network.

Possibly lastly, you will want to verify Popup.app is running.  You'll find Popup.app under /Library/Applilcation Support/Pharos/ in the Finder.  You can verify it's running by looking at Activity Monitor, which can be found in /Applications/Utilities.

If all else fails, please contact Pharos Systems Support

When printing to a Canon Multifunction Device (MFD), some of my documents are not being charged as expected in Uniprint.

 


Example :
      MS Office documents are detected and charged as mono when they include color text and/or backgrounds. They are detected and charged properly if they include a picture or clip art.

Install the latest Page counter (Pcounter) files attached.

The newer versions of the Canon drivers use different commands to send color codes to the MFDs.  Our latest page counter files detect this properly.

Create the following registry value on the Pharos Station with a value of 0.

HKLM\SOFTWARE\Pharos\Station
ShowBalance  REG_DWORD

 

If the value for this key = 0, the Pharos Print Release form does not display the user's balance value.
If the value for this key = 1, the Pharos Print Release form does display the user's balance value.

This is a known issue after performing an upgrade of Print server components to 8.0 due to the Windows Services manager window being open while upgrading.

If this happens, open a command prompt at the Pharos\bin directory and run the command PSLPDSrv -install, then start the LPD Server from the Services list. This will add the LPD Server back into the Services list.

The current support level for all Pharos product releases is covered by the Pharos Product Life Cycle Support Policy. In addition to outlining the current support policy for released products, this document defines the different support levels and the standard process used to determine the support level for a specific release.

Please refer to the attached document below.

 

If you have any questions, please contact Pharos support.

 

https://community.pharos.com/docs/DOC-1674

  • The Analyst, Collector, and Server Tracker components support 64-bit (as well as 32-bit) versions of Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, and Windows Server 2008 R2.
  • The Workstation Tracker component supports 64-bit (as well as 32-bit) versions of Windows 7, Windows Vista, and Windows XP.

For more information about Blueprint 4.2 supported software platforms, see

 

The following attached diagram outlines the connection between the Pharos Uniprint system and the Blackboard TIA system.


Note: You may also see a '503 Service Unavailable' error when using Web Remote due to larger amounts of data being returned by the server to the web client above what the system is initially configured for. The application of this Knowledge Base article should alleviate the problem. Should it not resolve the problem please contact support@pharos.com

 

To update Web Remote to display something other than the default of 100 items, follow these steps:

 

  1. Open the file Inetpub\wwwroot\Pharos\appSettings.config in a text editor

  2. Find this line and change the value attribute:
    <add key="WebApps_MaxNumOfRows" value="100"/>
    Set this value to the maximum number of rows you wish to be displayed in the Web Remote screens.

  3. If the previous value is set to anything much higher than 100 (eg 150), then follow these additional steps:
    1. Open the file Inetpub\wwwroot\Pharos\Web.config in a text editor
    2. Find the following row:
      <binding name="netTcpBindingCustomization">
      and change it to:
      <binding name="netTcpBindingCustomization" maxReceivedMessageSize="2097152">
    3. Find the following row:
      <binding name="authenticatedNetTcpBindingCustomization">
      and change it to:
      <binding name="authenticatedNetTcpBindingCustomization" maxReceivedMessageSize="2097152">

  4. Restart IIS, for example by running iisreset.

The Pharos clients, applications and servers obtain their time settings from the Windows OS.

Specifically:

SignUp clients get their time from the Pharos Database Server, which gets its time from the underlying Windows OS.

Terminal devices get their time from the Pharos EDI Server, which also gets its time from the Windows OS.

All other Pharos clients and servers get their time from the Windows OS on their local machine. Provided Windows has been updated for the new DST schedule, Pharos products will continue to function normally.

No changes are needed on the Pharos components for the daylight savings change.


Microsoft Windows 2003 Server Service Pack 2 changed the way SNMP is handled on a Windows Server 2003 Print Server. Please see the following Microsoft Knowledge base Article for further information.

http://support.microsoft.com/kb/946198


Here are 2 additional web site links from the internet that provide some additional notes.
http://blog.tiensivu.com/aaron/archives/1344-Upgrade-from-Windows-2003-SP1-to-Windows-2003-SP2-printers-get-marked-as-offline-workaroundfix.html

 

http://marc.info/?l=patchmanagement&m=119084230817381&w=2

 

See the attached Pharos TechNote.

Currently only the HP 4730 MFD will work with a USB Card Swipe

Approved USB Card reader for this device: Magtek HID Card Swipe

1. If you are experiencing problems with the USB Swipe Card reader check the following:

a. Is the card reader Magtek (this is the only approved reader currently)
b. Is the card reader HID. If it is a Magtek keyboard emulator you may be able to update the card reader by going to the Magtek website and downloading the Mini Wedge Configuration Program:

http://www.magtek.com/support/software/demo_programs/mini_wedge_config.asp

2. If you are still experiencing a problem you can obtain a log from the MFD which should show what is happening.

Steps to collect log:

a. plug in the usb card reader
b. power the MFD off, then back on (this starts a fresh log and makes sure the card reader info is captured)
c. On a PC open IE and use this URL:

http://<ip address of MFD>/hp/device/hp.ChaiWatchPort

Note: This is case sensative
Note: This requires that Java is installed in IE

When the page opens you will see a blank window with a "Go" button, and it will say 'disconnected" in the window.

Click "Go" and let the file process until it stops adding information.

Select, save the text log and send to Pharos.

When looking in the windows event log viewer I am seeing the following error message:

Event Log Error: PSDatabaseSvr,4000:Caught a general error with message '[PSComDBServer::ServiceListDetail] COM -- ADO error: IDispatch error #3092. Description: Missing some data (service_types).'

 

 

This is a known error at this time and has no impact on the pharos system and it's functionality. This Error can safely be ignored and will be resolved in a future release of Pharos.

Cause:
Multiple instances of Print Servers were installed that were not used.

 

Solution:
Update the License Server Service

Pharos is configured to use a Card ID and the data is getting truncated. The IPBILExt log shows that all the data is received up to a special character in the middle of the string (in this case, the character is an equals sign ' = ' ) then the rest of the data is dropped. The card reader is configured correctly for the device (HID for iMFPs, and keyboard emulation for PC Pharos Station and Omegas). The reader is transmitting the data properly (as tested by using MagTek's utility), but the data is still dropped.

 

Actual Track 2 Card Data
;6230170064541472=49110009596131?

 

Received by IP Biller Log
;6230170064541472

 

Configuring the network terminal settings to Strip Sentinels (Yes or No) and All Tracks vs Track 2 have no effect.

 

How can I resolve this ?

In the Network Terminal settings, choose the device in question. Make sure that all the settings are as expected for the card type and which track, etc. Select the USB tab, then click on the Advanced Features button at the top of the screen to reveal additional settings. Set the following

 

Ignore Sentinels While Parsing Tracks = ' No ' (Attached Screenshot)

VMware and various versions of GSX server have been tested and are utilized by Pharos to QA and Support the product. The product can be installed on VMware GSX versions and will be supported with best efforts by Pharos Systems. The use of VMware GSX and versions by Pharos QA and Technical Support does not simulate a true customer environment and therefore some consideration to the use of this platform in a production solution needs to be given. Clients wanting to use VMware GSX and other versions should consider the following:

  1. Issues specifically relating to the use of VMware and version will be assessed and a best attempt to resolve the issues will be made
  2. Issues may take longer to resolved because of the additional complexity of VMware

Note: This article applies to all Pharos Software products.

If you see this error it means that the Pharos Station sending the request should not be sending the Include Credit Limit as this is not set to be received by the Blackboard TIA system.

 

To resolve this issue you need to update the Pharos Station information in the BBTIAcfg.exe tool.

 

Set the corresponding Pharos Station to not send the Include Credit Limit in the Pharos Blackboard TIA Gateway. Screen shot attached.

Pharos 8.0 and 8.1

The Pharos 8.x versions have been tested against the HP UPD and is confirmed as supported by these Pharos product release.

 

Pharos Uniprint creates two printer objects in Windows. One is the Pharos Controlled Spool (Held) Queue and the other is the Printer Queue.

 

The Pharos Spool (Held) Queue never communicates with the physical printer and will need to be configured manually. It must also have Bi-directional printing disabled.

 

The Printer Queue does communicate with the physical printer.

 

Pharos 7.2 has used the UPD successfully.

 

There are several known issues and solutions are listed below.

 

To resolve 7.2 known issues:

 

1.  Prior to creating the server package make sure that the spool queue printer object is set to "Winprint" and "RAW" for the Print Processor.
2.  Prior to creating the server package make sure that the Advanced Printer Features have been disabled.
3.  Prior to creating the server package make sure that Bi-directional printing has been disabled.
4.  Prior to creating the server package make sure that the spool queue has received the printer setup configuration by temporarily pointing it at the printer.
5.  Install the driver on the local workstation first
6.  DON'T install the popups on the server!

The above steps should be completed in the to resolve any UPD issues.

Confirm that the registry key “One Duplex Page Mod” is set to 1 (this is the default value) - this will ensure that single page duplex jobs have their attributes modified to remove the duplex attribute (e.g. [1, A4, duplex] becomes [1, A4, simplex]. Therefore single page jobs will be charged as simplex jobs.

 

Where to find the Registry Entry:

 

My Computer \ HKEY_LOCAL_MACHINE\SOFTWARE\Pharos\Print Server

1) During the package creation, what paths do the files take?

The driver files are obtained from the Pharos Print Server. That is, the package creator (which runs on the administrator) works as follows:

  • The installer reads the database for the package definitions for each printer in the package.
  • The Installer checks the Pharos Print Server, and get all driver information.
  • Fetch the driver files from the print server, using standard windows API calls.
  • A module is built for each printer. The module files are built in the location given by “Package Build Location” (which should be a windows UNC path)
  • Modules are combined into packages. (Again, in the same location.)

2) If the Pharos Administrator does not have full permissions to the print server (i.e. not on the same domain) does this effect the package creation process?

  • Correct, the person running the Pharos administrator needs permissions on the print server to retrieve the printer driver files.

3) Can packages be created if Pharos Administrator is installed on a remote machine separate from all other Pharos Components?

  • Yes, the package creator could be run on a remote PC (but as pointed out in 2 above, the person running it needs permissions for the print servers.)

4) What method is used during Package creation to copy the files

  • The package creator uses standard windows file copy commands to move files.

5) Is there a need to run the Pharos Web Services?

  • No, the Pharos Web Services are optional. The customer can create their own web site for the packages if they wish. The Pharos Uniprint Web Service is really just us providing a default web page.

<?xml version="1.0"?>

 

Printer error detection is performed by the Pharos Print Server. The Pharos Print Server checks the status of the printer as seen in Windows Print Manager. By default the Pharos Print Server will assume that any printer that has the word "error" in its status is in a faulty state and it will not send print jobs to that printer. Users will be notified either at the Pharos Station or via the Notify client if it is configured to do so.

This method of printer error detection is dependent on the print driver accurately reporting the state of the printer. Unfortunately, not all print drivers report print status accurately, so this means print jobs may still be sent to faulty printers, or alternatively the printer will be reported in an error state when it is in fact functional. In this situation it is recommended you contact your printer manufacturer to see if they can assist you in configuring the printer so its state will be reported correctly. If this is not possible, you can modify or completely disable printer status detection altogether.

What the Pharos Print Server considers as an error state is defined by the "Status String Match " registry key. This key can be configured to check for multiple error conditions. Error state checking can be disabled using the "Status Enable" registry key.

More information on Pharos Registry Key entries can be found in Pharos Help.

Problem:
After re-starting the server, get a lot of Application Log error messages in the Event Viewer. These are "MS Faults", and the Application Log in the Event Viewer is getting full with XML error related messages saying "System could not locate the object specified".

 

Event Viewer Error Messages:

 

Event Type: Error
Event Source: MSSOAP
Event Category: Client
Event ID: 16
Date: 31/03/2003
Time: 9:56:28 a.m.
User: N/A
Computer: TS
Description:
Soap error: One of the parameters supplied is invalid.

 

then...

 

Event Type: Error
Event Source: MSSOAP
Event Category: Generic
Event ID: 16
Date: 31/03/2003
Time: 9:56:28 a.m.
User: N/A
Computer: TS
Description:
Soap error: Loading of the WSDL file failed.

 

also...

 

Event Type: Error
Event Source: MSSOAP
Event Category: Generic
Event ID: 16
Date: 31/03/2003
Time: 9:56:28 a.m.
User: N/A
Computer: TS
Description:
Soap error: XML Parser failed at linenumber 0, lineposition 0, reason is: The system cannot locate the object specified.

 

Now, non of the Monitor devices are talking to Pharos anymore, and are displaying "set-up request" and "waiting set-up" messages.

 

Applies To:
Pharos 5.1.1632 with SP 1, EDI Server version 5.1.0.1883, Monitor firmware version OG20M06.405
Solution:

 

Re-start both the Pharos EDI Server service and the Monitor Translator.

The following list displays the supported Lexmark iMFP models and Pharos Product Versions:

MFP Model Pharos Supported Product Version eDAS Version

X644e

Uniprint 7.1, 7.2 eDAS for Pharos Uniprint v1.2.0
Blueprint 3.5 eDAS for Pharos Blueprint v1.2.0

X646e

Uniprint 7.1, 7.2  eDAS for Pharos Uniprint v1.2.0
Blueprint 3.5 eDAS for Pharos Blueprint v1.2.0

X646dte

Uniprint 7.1, 7.2eDAS for Pharos Uniprint v1.2.0
Blueprint 3.5eDAS for Pharos Blueprint v1.2.0

X646ef (X4600 + T64x)

Uniprint 7.1, 7.2eDAS for Pharos Uniprint v1.2.0
Blueprint 3.5eDAS for Pharos Blueprint v1.2.0

X772e (X4600 + C772)

Uniprint 7.1, 7.2eDAS for Pharos Uniprint v1.2.0
Blueprint 3.5eDAS for Pharos Blueprint v1.2.0

X782e (X4600 + C782)

Uniprint 7.1, 7.2eDAS for Pharos Uniprint v1.2.0
Blueprint 3.5eDAS for Pharos Blueprint v1.2.0

X850e

Uniprint 7.1, 7.2eDAS for Pharos Uniprint v1.2.0
Blueprint 3.5eDAS for Pharos Blueprint v1.2.0

X852e

Uniprint 7.1, 7.2eDAS for Pharos Uniprint v1.2.0
Blueprint 3.5eDAS for Pharos Blueprint v1.2.0

X854e

Uniprint 7.1, 7.2eDAS for Pharos Uniprint v1.2.0
Blueprint 3.5eDAS for Pharos Blueprint v1.2.0

X940e

Uniprint 7.1, 7.2eDAS for Pharos Uniprint v1.2.0
Blueprint 3.5eDAS for Pharos Blueprint v1.2.0

X945e

Uniprint 7.1, 7.2eDAS for Pharos Uniprint v1.2.0
Blueprint 3.5 eDAS for Pharos Blueprint v1.2.0

Register for article updates to receive updated information on device support.

Backend logging

To enable more verbose Print and Popup backend logging, edit the /etc/cups/cupsd.conf file, replacing the text:

LogLevel info

with this text:

LogLevel debug

Leave everything else as is.

UI logging

To enable logging for the Popup user interface, edit the /etc/syslog.conf file, replacing the text:

lpr.info

with the text

lpr.debug

Leave everything else as is.

 

For Mac OS X 10.8 (Mountain Lion): as indicated within syslog.conf, changes should instead be made to /etc/asl.conf.  To enable the necessary logging, add the following line:

? [= Facility lpr] file /var/log/lpr.log

NOTE: You must restart the client machine to make sure the changes take effect.

If you encounter Popup problems, send the following files to Pharos Support:

  1. /var/log/cups/error_log
  2. /var/log/lpr.log

The first file is the print system log.  The second is the Popup application log.

When no longer needed, stop logging by changing the edited files back to the original state, as logging can generate very large files.

This error message means that the Popup Client was able to talk to an LPD service on the server (Microsoft TCP/IP Print Services or Pharos LPD Service) but the LPD server refused the print request. This is expected if the workstation sending the print job is sending the print job to a Spool Queue that no longer exists.

To properly diagnose the source of this problem, turn on logging on LPD Server, send a job that fails, then send Pharos Technical Support the log files.

To enable logging see Article 626: The Pharos Logsetter

When the Pharos Administrator can't connect to a Pharos Pop Up server, this error message might be displayed. Possible resolution as follows,

1. Open Windows Services and check whether the "Pharos Popup Server" is running.

NOTE: If  the Pharos Popup Server does not appear in Windows Services, it will need to be installed.

2. If there is a firewall running on the Pharos Server, make sure that "PopupSrv.exe" is in the exceptions list and the port 28203 is open.

1) Install the printer locally on the Pharos Station and share this printer.

 

2) Install the Pharos LPD Server on the Pharos Station. This needs to be installed off the Pharos installation CD:
a) Follow the installation steps up to the point where you are prompted for which product to install.
b) Select Uniprint > Print Server > Pharos LPD Server (uncheck all other options) and finish the installation.

 

3) In Pharos Administrator, install the printer using the Device Insert Wizard in the Printers context (the green '+' button).
a) Install the printer using the same driver as used on the Pharos Station.
b) On the next screen of the wizard install a new port (Add Port...). The port needs to be an LPR port, the name of the server providing LPD needs to match the machine name or IP address of the Pharos Station and the print queue needs to match the share name of the newly installed printer on the Pharos Station. Finish the printer installation as you normally would.

 

4) To secure the printer so users cannot print directly to the printer share, modify the permissions on the printer at the Pharos Station PC so that Everyone does not have any permissions on the new printer. Then give full permissions to System on that printer.

 

Alternatively, within the properties of the Pharos LPD Server in the Windows Services manager, enable the service to log on using a domain admin and give that domain admin full permissions on the printer.

This is a known issue with the M Series device range and the Pharos iMFP solution.

This issue is resolved by ensuring that the latest HP firmware available at HP.COM is installed on the device.

Analyst and Collector OS support

  • Microsoft® Windows Server 2003 (original edition and R2)
  • Microsoft® Windows Server 2008 (original edition and R2)
  • 32-bit and 64-bit on all supported OS’es
  • Active/passive clustering on all supported OS’es

Analyst Database Support

  • Microsoft® SQL Server 2005
  • Microsoft® SQL Server 2005 Express
  • Microsoft® SQL Server 2008 (original edition and R2)
  • Automated local and remote database installs

Workstation Tracker

  • Microsoft® Windows XP (SP2 or later)
  • Microsoft® Windows Vista (Business, Enterprise or Ultimate)
  • Microsoft® Windows 7 (Professional, Enterprise or Ultimate)
  • Microsoft® Windows Server 2003 (SP1 or later) (Terminal Server)
  • Microsoft® Windows Server 2008 (original edition and R2) (Terminal Server)
  • 32-bit and 64-bit on all supported OS’es

Server Tracker

  • Microsoft® Windows Server 2003 (SP1 or later, original edition and R2)
  • Microsoft® Windows Server 2008 (original edition and R2)
  • Active/passive cluster support
  • 32-bit and 64-bit on all supported OS’es

This article applies to both Pharos Uniprint and Pharos Blueprint using PCounter.exe 8.2.6129.0 and lower.

The Portable Document Format, or PDF, originally introduced by Adobe Systems, Inc., has become an almost ubiquitous file format for the distribution of information intended for web, mobile devices, or for print. And while the PDF document can be printed to just about any type of printer, it has a special affinity - a connection - to PostScript printers, as the two share a very common ground.

Along with every great step in the development of the PDF format, Adobe Systems releases a new version of the Adobe Acrobat product line. In spite of the functional differences between the Reader, Standard, and Professional editions of Adobe Acrobat, they all share common function in terms of PDF file display, navigation, and basic printing. Which brings us back to PostScript. Adobe has engineered a good chunk of their PostScript driver technology into the Acrobat product line. This was done, primarily, so that Acrobat can reproduce, as mach as the printer and its driver will allow, the PDF file on any print device with equal fidelity. On non-PostScript devices, Acrobat pre-renders as much of the file contents as possible so that the driver isn't doing it. On PostScript devices, Acrobat generates much of the job code so that the driver isn't doing it (the theme: Acrobat trusts the driver to understand the printer's capabilities, but not to convert its PDF file). Because some PDF files can be quite complex, Adobe builds in some optimization functions to make the PostScript file as efficient as possible.

Which brings us to ... well, us. Our current PCounter is good at what it does and can accommodate many different print languages. But the current version (8.2.6129.0) and previous versions may not handle an option in one of Acrobat's PostScrips functions for optimization: sending fonts (and other resources) well. The default setting is "Send as Range." This setting inserts the font at the beginning of the page that it is needed, and then causes the font to be removed from printer memory after the page has printed. With some print drivers, the PCounter may fault with an Unknown, undefined error and may call out a font name if parsed with the Page Counter Tester. An example of this dialog, found in Print > Advanced is attached to this article.

However, the setting "Send at Start" will work when applied with problem drivers or PDF files. This setting uses the most memory (as all fonts in the document are sent at the beginning of the document and retained until the entire file is printed), but is the most compatible. This setting can be made permanent for Adobe Acrobat Reader by opening the Registry key HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\<version>\Originals and adding a DWORD called bSavePSVM and giving it a value of 0. If the location is using an edition of the Adobe Acrobat product like Standard or Professional, the Registry key is HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\<version>\Originals. The same DWORD and value apply.

PCounter's inability to handle PostScript code from Adobe Acrobat with the "Send as Range" option enabled for some printer drivers has been resolved. A new PCounter.exe and support files can be downloaded from  Pharos Systems' FilesAnywhere. To upgrade, stop the Pharos Print Server service on the print server and extract the files into the Pharos\Bin folder, overwriting any existing file. When finished, start the Pharos Print Server service.

For Further Reading: Adobe has a KB article describing other "features" of the "Send as Range" option. Read it at http://kb2.adobe.com/cps/408/kb408015.html.

Internet Explorer by default adds an extra page at the end of a duplex print job when it has an odd number of pages.

 

To avoid the adding of an extra page, on your Pharos Print Servers you need to set the value of the registry key “No Blank Pages” to ‘1’. By default the value is set to ‘0’.

 

Where to find the registry key:

 

My Computer \ HKEY_LOCAL_MACHINE\SOFTWARE\Pharos\Page Counter

On the computer performing the diagnostic logging can change the logging level using the following instructions.

On a Print Server:

Edit the Start menu shortcut 'Pharos Blueprint Enterprise > Print Tracker > Enable Tracker Debug Logging' and change:

"C:\Program Files\PharosSystems\Blueprint\bin\DiagTool.exe" /LoggingOn

to:

"C:\Program Files\PharosSystems\Blueprint\bin\DiagTool.exe" /LoggingOn /DebugLevel:10

Stop and Start the Pharos Systems ComTaskMaster from the Services menu

On a Workstation:

Enter the following from the command line:

"C:\Program Files\PharosSystems\Blueprint\bin\DiagTool.exe" /LoggingOn /DebugLevel:10

Stop and Start the Pharos Systems ComTaskMaster from the Services menu

The logs are usually located under the following directory (C:\Documents and Settings\All Users\Application Data\PharosSystems\Blueprint\Logs) depending on which directory Pharos Blueprint is installed on to.

How to create custom reports

Posted by toleary Aug 1, 2013

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.

Possible Cause 1:
Server has run out of hard drive space.

 

Solution 1:
Free up hard drive space on the server.

 


Possible Cause 2:
The Pharos Spool Queue is not set as Shared.

 

Solution 2:
Set the Spool Queue as 'Shared.'

See attached (MS Word 97-2003 format) documents.

Pharos Offline Billing isn't working as expected. The Administrator and IPBilExt settings all seem to be correct for Offline billing to be enabled. But at the Pharos Station the users only get the message Error 29046 "Billing system offline" and users are not able to print.

 

The IPBilExt settings were correct on the DB server, but that IPBilExt isn't being used. The IPBilExt being called is on the Print Server. Configured the IPBilExt on each of the Print Servers to have the "return pharos offline" box checked.

Packages can be installed silently using the -quiet command line option

Specifying this option causes the package to run silently, i.e. no dialogs are displayed to the user.

For additional command line options see the following Knowledge Base article:

Title: Command Line Options for 7.0 Packages
URL:http://pharos.custhelp.com/cgi-bin/pharos.cfg/php/enduser/std_adp.php?p_faqid=561&p_created=1137078662


The Pharos Popup Client module is not part of the package. Add this module in Pharos Administrator (Package Definitions > Pharos Supplied Modules), rebuild the package and distribute. The problem could also be related to the following issue

 

- Check to see if you installed the Print Services for Unix on the workstation
- Then check the port to see if it was created using LPR, if so does the port name start with name Pharos

 

LPR port with the name starting with Pharos also causes the same error message

 

Example
PHAROS72:test1_q

Distributing and Using Packages

 

Once created, packages are distributed to client PCs by whatever means you prefer, although it is assumed they will be made available at a shared location, so that users can browse and install the packages relevant to them. This location may be a network share known to all users or a web site containing links to the packages.

 

Setting the Package Root Path property allows packages to be generated directly into a web server or share. Alternatively, packages can be generated in an export location, then transferred manually to a web server or share.

If packages are made available on a web site, several options are available for presenting the packages to users:

 

- You can write your own web pages, containing links to the package files.
- Users can be given access to the Manifest.xml file, which contains links to all available packages.
- Users can be given access to the Uniprint Web Site.

 

The Pharos Print Map Builder is opened from Pharos Administrator by clicking the button on Package Definitions toolbar.

 

Running Packages

 

Packages are run by double-clicking on them. Full packages install the Pharos components and Spool Queue printer(s) immediately. Lite packages detect the operating system and any existing Pharos components, then download and install only those modules that are needed. Depending on the modules installed, a reboot may be necessary following the install.

 

Note: Lite packages contact the URL specified by the Module URL property to download modules.

 

When running an installer, an Advanced button is available to show details of the install as it progresses.

Updating Packages

An updater module is included in all install packages. The updater runs a service and checks the manifest file for updates whenever the Pharos components are used, provided a specified period has elapsed since they were last used.

Microsoft released an update to MSN Messenger 7.5 which caused the services file to be unavailable.

You need to perform the following steps to resolve the issue on the client machine:

Check this registry key :

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

In this key, the DataBasePath Value must have a REG_EXPAND_SZ and not a REG_SZ Type.

The data here must be %SystemRoot%\system32\drivers\etc

Note: It seems that this will appear when you update MSN Messenger with a new version.

Once you have done this you need to reboot the client machine and the problem should be resolved.

Here's how to capture a Windows spool file:

 

This needs to be done when no users are using the system.

 

1) Pause all print queues so that documents are not released to the physical printers.
2) Go to Windows Print Manager ( Start > Settings > Printers and Faxes ), select File > Server Properties > Advanced tab and open the folder specified by the Spool folder property.
3) Make sure this folder is empty. If it is not, delete any existing files. You may need to stop the Print Spooler service to do this. Restart the service once you have deleted any files.
4) Once the folder is empty, print a document that replicates the problem you are having. This will create two files, with the extensions .shd and .spl.
5) Copy and zip these files. These are the spool files that you need to send to Pharos Support.
6) Delete these files from the spool directory and unpause any print queues with the comment "Pharos Controlled Device". Do NOT unpause the Pharos Spool Queues.
7) Normal printing can resume.

 

Here's how to capture a Mac spool file:

This needs to be done when no users are using the system.

1.Temporarily stop the printer, or turn off the printer so that jobs hold in the queue. Print a test job that demonstrates the problem behavior.

2. Open the Terminal under Applications/Utilities

 

3. Type the following in the terminal:
        sudo su -
        [enter your password]
        cp `ls -t /var/spool/cups/d* | head -2` /Users/<username>
        exit
where <username> is your short login name. (i.e. this denotes the location of your home directory). Special Note: the character preceding the ls and following the 2 is a back-tick (`).
4.You should how find at least one file in your home directory with a name like:
           d00077-001
5.email the file(s) to support and also include the "expected" information related to the job including:
- the number of pages
- the paper size
- other attributes such as grayscale, copies, etc.


 

See the attached Pharos TechNote.

Alert Codes for Uniprint, Off-The-Glass, and SignUp

To find out more about a coded alert, please use the Pharos Administrator Help system. To do this, select Help in the top menu bar of the Administrator, and then select Help Topics from the dropdown list. You may search on a particular alert code or get an overview of all Uniprint Suite alert codes by searching on "Alert Index".

 

License Server Alerts

Alerts sent by the Pharos License Server are also written to the Events Log of the PC on which the Pharos License Server is running.

Message
“'_' license limit has exceeded the expiry date.”
Discussion
The license on the named Pharos component has expired. Contact licensing@pharos.com for a new license for this component.

Message
“Early Warning: Running low on '_' license limit.”
Discussion
The Early Warning limit configured on the named Pharos component has occurred. Contact licensing@pharos.com for a new license for this component.

Message
“Critical Warning: Running low on '_' license limit.”
Discussion
The Critical Warning limit configured on the named Pharos component has occurred. The License Limit is about to expire. Contact licensing@pharos.com as soon as possible for a new license for this component.

Message
“Attempt to exceed '_' licensed for.”
Discussion
Someone tried to make more use of a component than the system is licensed for.

Message
“Unable to retrieve info on limits not known at compile time.”
Discussion
Registry information is corrupted. It must be reinstalled.

Message
“Unable to start Limit Information Database.”
Discussion
The Pharos License Server cannot start.

Message
“Dongle failure. License server shutting down.”
Discussion
Contact Pharos.

Message
“Limits can't fit into the dongle.”
Discussion
Updated License Limits no longer fit into the dongle. Contact Pharos for a dongle with more memory.

Message
“No matching OpenRequest found.”
Discussion
There is a bug in the Client making the request.

Message
“Item 'X' in list is illegal.”
Discussion
There is a bug in the Client making the request.

Message
“Error when trying to compose a reply packet '_'.”
Discussion
A network fault has occurred/ out of memory.

Message
“Error: Dongle reports error 'DongleError'”, where 'DongleError' is one of:

  • “No Dongle or License Key found”
    The Pharos License Server could not find a license. Check dongle is inserted correctly, that it is in the correct port and that the port is working.
  • “Dongle is corrupted”
    Licensing information in the Dongle is corrupted.
  • “Cached license info is corrupt”
    The cached copy of the Dongle's information kept in the Pharos License Server is corrupt.
  • “Unknown format for data in Dongle”
    The license format has changed. Pharos License Server needs to be updated.
  • “Dongle is faulty”
    Contact Pharos.
  • “Dongle needs replacing, it's almost worn out”
    A Dongle has a finite life. Contact Pharos for a new one.
  • “The Dongle has been removed. Please replace”
    The Dongle has been removed, or is loose or is incorrectly plugged in. Ensure that the dongle is securely plugged in, that it is in the correct port, that the port is OK.
  • “The License Key is invalid.”
    Someone has tried to break the licensing system. Restore the License Key to its original form as supplied by Pharos.
  • “The License Key has expired.”
    Contact licensing@pharos.com for a new license.
  • “Unspecified Error.”
    Some problem has occurred with the Dongle/ License Key other than those specified above.
  • “No Error/ Error has been corrected.”
    Reported problem has been fixed.
  • “Error: Can't read limits in Dongle.”
    The license format has changed. Pharos License Server needs to be updated.


Alerts written only to the Events Log

A limited number of alerts are written only to the Events Log.

Message
“Unable to connect to DB Server.”
Discussion
The Pharos License Server is unable to contact the Database Server to log an alert.

Message
“Unable to send Alert to DB Server.”
Discussion
The Pharos License Server contacted the Database Server but the Database Server would not log an alert.


When installing a 7.x/8.x client package, an error occurs. The workstation displays the following error:

"The install failed. Select Finish to exit."

Additionally, the install log file contains the error:

"AddPrinterDriver Failed - Error code 1722" (or similar)

Certain drivers do not install properly when part of an install package.

In Uniprint 7.x and 8.x, drivers that are known to be problematic can be listed in a file called BadDrivers.txt, which must reside in a  location specified by the search Root Path of the system, such as c:\program files\Pharos\bin on the Pharos Principal (Database) Server

Drivers are listed one per line, for example:

HP Laserjet 4200

When packages are created, the package creator checks each Spool Queue that is specified for a package to see if its driver appears in the BadDrivers.txt file.

If found, the driver will not be included in the package when it is created (compiled).

To install the package , the driver must already be installed locally on the workstation before the package is run. The package will install a printer for the Spool Queue, and will leverage the locally installed driver.

Solution:

Make the following changes to the Spool Queue and Printer Queue objects in the Windows Printer folder on the Pharos Print Server.

Set the:

PrintProcessor to "Winprint"
Default Data Type to "RAW"

Rebuild the package. The package should install correctly.


The following error is seen in the Event Log:

Source: PSDatabaseSvr
Category: (None)
Type: Error
Event ID: 4000
User: (None)
Computer: (the name of the Pharos Server)
Description: Caught a general error with message '[CReaper::OnStart] Failed to start Reaper thread.'

 

 

Pharos has two “Reapers.”

One in the Print Server and the other in the Database Server.

These are "background tasks" that run inside the servers themselves.

The primary function of the Reaper in the Print Server is deleting old jobs from the spool queues. (It also does a number of other “clean-up” tasks.)

The Reaper in the Database Server does similar work in the database, automatically purging transactions older than a specified time (if enabled), purging expired reservation records, and express patrons, etc..

Related Errors:

Check in Pharos Administrator under Alerts:

29038

Message: "Failed to create Reaper thread"

Discussion: The Reaper thread performs tasks like deleting expired jobs, polling SNMP printers and doing offline billing. This may be either a database or Windows problem. Check that the Database Service is not overloaded e.g. on an underpowered machine. Similarly check that the machine the Print Service runs on is not overloaded.

29052

Message: "Reaper thread error: '%1''

Discussion: The reaper is a utility thread that runs background tasks such as reaping (killing) expired jobs, polling SNMP printers and transacting offline billing. '%1' specifies the particular error that occurred.

The error message, combined with the alert 'Operation' field should indicate what caused the problem. For example, if the 'Operation' field records 'Opening queue', then the alert 'Item' field will be the queue name.

The error affecting the queue should be corrected.

The following steps should manually uninstall the Pharos Popup Client. They must be carried out in the order described below:

  1. Stop the Pharos Systems ComTaskMaster service.
  2. Run the profiler manual uninstall as follows:
    1. Go to Program Files\PharosSystems\OutputManagement\PrintTracker. If the folder doesn’t exist, create it.
    2. Check for a file called profiler.dll. If the file is not there, copy in the one attached.
    3. Open a command prompt in that location and type: rundll32 profiler.dll,Exec uninstall
  3. Uninstall the ComTaskMaster service as follows:
    1. Ensure the Services window is closed
    2. Go to Program Files\PharosSystems\Core. If the folder doesn’t exist, create it.
    3. Check for a file called CTskMstr.exe. If the file is not there, copy in the one attached.
    4. Open a command prompt in that location and type: CTskMstr.exe -unregserver
  4. Delete folders:
    1. Ensure the command prompt window (from 3, above) is closed.
    2. Go to Program Files\Pharos. If it exists, delete the folder (and contents).
    3. Go to Program Files\PharosSystems. Delete the folder (and contents).
  5. Check for the following registry keys. If they exist, delete them:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Pharos
    • HKEY_LOCAL_MACHINE\SOFTWARE\PharosSystems
  6. Restart the Print Spooler service in Services.

The PC should now be back to as it was before the Popup Client was installed, and should now be able to install a new package.

If any of these points fail don’t go on to the next step. Please capture the error and report it to Pharos Support for advice on how to continue.

Pharos products use gateways to interact with two main types of systems: billing systems (online funds) and authentication systems (user identification and authorization).

 

This document describes the steps necessary to install and configure billing gateways. See the attached Pharos TechNote.

[2007/06/05 11:45:53 PFB0 T41C Controller] [CRunInstructions::DoStep] A PSException was caught: "Failed to Enumerate Ports, Error Code=1722"
[2007/06/05 11:45:55 PFB0 T41C Controller] [CControllerApp::KillFileLog]

AND/OR

Failed to initialize the Installer Helper DLL: Unable to get a list of ports: The data area passed to a system call is too small..
Check to see if Pharos Popup client has been installed on the Pharos Server.

If so:

Uninstall the Popup client from the server.
Rebuild the Packages.

The Pharos Print Server does not support Windows XP in a default install. Modifications must be made to the registry to use the Print Server on Windows XP. Smaller modifications are also required to use the Print Server on Windows 2003, prior to Pharos 5.4

 

See the attached Pharos TechNote.

If you change the IP Address (or name) of the Pharos (Print/Database) Server you will need to verify the following:

1. From within Pharos Administrator

Go to System > Servers. Make the change and commit by performing a Change Control. This should make the change within the Pharos Database.

NOTE: If for some reason the change in Pharos Administrator did not take:

Open the SQL Query Analyzer and manually update the Server IP Address in the database.

Run the following query against the Pharos Database:

     SELECT * FROM servers

Look for the server id number. You will see the 'old' IP Address on the same line.

Run the following query to update the IP address.

     UPDATE servers SET ip_address='<new IP Address>' WHERE server_id = <ID Number value>

2.  Check the following server registry keys, and edit to display the new IP Address (or Host Name).

Check the Database Server registry entries:

     HKEY_LOCAL_MACHINE\SOFTWARE\Pharos\Database Server

     "Host Address"="<new value>"

     HKEY_LOCAL_MACHINE\SOFTWARE\Pharos\Database Server\Database

     "Server Name"="<new value>" (or IP Address if used)

For the License Server:

     HKEY_LOCAL_MACHINE\SOFTWARE\Pharos\License Se rver

     "Host Address"="<new value>"

For the EDI Server:

     HKEY_LOCAL_MACHINE\SOFTWARE\Pharos\Edi

     [Server]

On machines running Pharos Remote:

     HKEY_LOCAL_MACHINE\SOFTWARE\Pharos\PRemote

     [BankServerName]

3.  Pharos Clients: (using Popups)

     HKEY_LOCAL_MACHINE\SOFTWARE\Pharos\Popup Client\Server

     "ServerAddress"="<new value>"

     HKEY_LOCAL_MACHINE\SOFTWARE\Pharos\Database Server

    "HostAddress"="<new value>"

     HKEY_LOCAL_MACHINE\SOFTWARE\Pharos\Popup Client\Ports

     For the Port *.prn entry

4.  Pharos Stations:

The Pharos Stations should update when the Change Control is made from Pharos Administrator after you change the server IP Address.

5.  Terminal Devices:

Terminal Devices will need to be updated.

Terminal selections for the Print Server (configured in Pharos Administrator). The terminal also may need to be configured to have the correct PEDI server name, if it has been changed.

6.  SSL Certificate:

The SSL Certificate, if used, is based on the server name, and if this was changed a new certificate must be requested. The old certificate won't work.

7.  DNS:

Update entries in DNS to reflect the new server name and IP address.

8. When done:

You will need to restart the services (or reboot the servers). Restarting the License Server Service will restart the other Phaors Services on the Principal Server.

If you experience any problems with this transition please contact Pharos Support at support@pharos.com.

The following Command Line Options are available when creating and running packages

  • Command line options available for the PackageCreator.exe executable:

/d = Debug mode

This enables a Debug Step button on the progress bar dialog, which allows you to step slowly through each part of the package creation process, so you can see where problems arise.

/q = Quiet mode

Specifying this option means that the progress bar dialog is not displayed. This option overrides debug mode.

  • Command line options available for the PackageInstaller.exe executable:

–norepair option

This means that the package will not re-install any existing modules.

–quiet option

Causes the package to run silently, i.e. no dialogs are displayed to the user.

For additional information see:

Pharos Help (search for the following terms):

Package Definitions
Creating Install Packages
Installing Popup Clients

With the Pharos Login Service, Canon's Universal Send requires that the user's email address be provided. If the user's email address is not provided then Universal Send will not allow the transmission to continue. In Uniprint, enter an email address for the user, log off from the iMFP, and try again.

To enter an email address in Pharos Administrator:

1. Open Pharos Administrator
2. Select the Users\User context
3. Highlight the user to administer
4. Select the Email field and enter a valid email address

The Pharos 8.1 CD image contains a "Documents" folder that contains both an "Upgrade Guide" and a "Planning and Installation Guide."

 

Starting on page 14 of the "Planning and Installation Guide" is information on server requirements (including system, hardware, SQL) and page 22 discusses 64-bit server support and VMware.

 

With regards to the statement on page 22 of the provided PDF: "Pharos components are not officially supported on VMware 64-bit virtual machines due to hardware compatibility issues with these virtual machines."

The issue is with VMWare and certain Guest OS and VM image combinations.

 

See: http://www.vmware.com/pdf/GuestOS_guide.pdf

 

Pharos 64-bit VM support is subject to that supported by VMware. Some versions of VMware do not support specific combinations of guest operating systems and host processors.

For example, with older versions of VMware, running a 64-bit guest OS on an AMD Opteron processor may work, while running the same guest OS on a first generation 32-bit Intel Core Duo would result in random crashes and other unpredictable behavior.

 

Pharos installed on VMware in unsupported configurations will have various forms of instability.

Customers will need to establish that their specific combination of host OS, host hardware, guest OS and VMware configuration is fully supported by VMware before they attempt to install Uniprint.

 

Here's a quick breakdown.

 

32-bit CPU + 32-bit Host OS

 

32-bit Guest OS - Supported
64-bit Guest OS - Unsupported

 

32-bit CPU + 64-bit Host OS

 

32-bit Guest OS - Unsupported
64-bit Guest OS - Unsupported

 

64-bit CPU + 32-bit Host OS

 

32-bit Guest OS - Supported
64-bit Guest OS - Supported

 

64-bit CPU + 64-bit Host OS

 

32-bit Guest OS - Supported      
64-bit Guest OS - Supported


A list of all current Alert Codes and their definitions can be found in Pharos Help by searching for the code number, or searching the phrase "Pharos Alert Error Codes."




18000 18001 18002 18003 18004 28005 28006 28300 28301 28302
28303 28304 28305 28306 28307 28308 28309 28310 28311 28312
28313 28314 28315 28316 28317 28318 28319 28320 28321 28322
28323 28324 28325 28326 28327 28328 28329 28330 28400 28401
28402 28403 28404 28405 28406 28407 28408 28409 28410 28411
28412 28413 31100 31101 31102 31103 31104 31105 31106 31107
31108 29000 29001 29002 29003 29004 29005 29006 29007 29008
29009 29010 29011 29012 29013 29014 29015 29016 29017 29018
29019 29020 29021 29022 29023 29024 29025 29026 29027 29028
29029 29030 29031 29032 29033 29034 29035 29036 29037 29038
29039 29040 29041 29042 29043 29044 29045 29046 29047 29048
29049 29050 29051 29052 29053 29054 29055 29056 29057 29058
29059 29060 29061 29062 29063 29064 29065 29066 29067 29068
29069 29070 29071 29304 29100 29101 29102 29103 29104 29105
29106 29107 29108 29109 29110 29111 29112 29113 29114 29115
29116 29117 29118 29119 29120 29121 29122 29123 29124 29125
29126 29127 29128 29129 29130 29131 29200 29201 29250 29251
29300 29400 50000 50001 50002 50003 50004 50005 50006 50007
50008 50009 50010 50011 50012 50013 50014 50015 50016 50017
50313 28212 28204

This issue is caused by a limitation within the printer network card. Pharos has provided a resolution to this issue in the form of a Pharos Omega 150 firmware update. The firmware 2.1.0.6376 or above can be obtained from:

 

http://www.pharos.com/Support/Terminals/Index.html

Pharos is aware of the problem and will produce an update to resolve the problem in future revisions. This article will be updated when the new revision is available.

Pharos Omega PS150 2.1.0 revision 6376

Download Location: http://www.pharos.com/Support/Terminals/Index.html

Prerequisites:

Title: Hot Fix 15 to Pharos 7.2 (Pharos EDI)
URL:
http://pharos.custhelp.com/cgi-bin/pharos.cfg/php/enduser/std_adp.php?p_faqid=1207&p_created=1185756529

Title: Hot Fix 17 to Pharos 7.1 (Pharos EDI)
URL:
http://pharos.custhelp.com/cgi-bin/pharos.cfg/php/enduser/std_adp.php?p_faqid=1208&p_created=1185756735

What's New in this Release

Support for Blueprint Enterprise

Omega devices can be used as terminals in the Secure Release Here™ system introduced in Pharos Blueprint Enterprise 3.5. Omega terminals can be added in Blueprint Administrator, and appear on the Terminals screen in the Device Management section. Copier training at the SmartPAD records its results in the Blueprint database.

Improvements to copier training

Improvements have been made to the copier training wizard (available on the Station > Copier screen of the SmartPAD configuration menu), making it easier to use and more robust:

The screen that allows you to select the attributes you want to configure has been simplified for ease of use.
A Save Current button is available, which lets you save the results of all tests completed successfully so far. This means that you can commit some changes (and test them) even if some tests fail.
The copier training wizard now supports copiers that use a double pulse for Duplex.

File uploads and downloads in Omega Administrator

The new Files screen in the Omega Administrator web application allows you to download selected configuration files and upload new versions of them.

Note: Omega Administrator does not verify the contents of uploaded files. Be very careful when uploading files, as a corrupt or incorrectly written file may disrupt the functioning of the SmartHub.

Changes to screensaver

The properties that control the SmartPAD screensaver have changed. The Screen Suspend Time has been renamed the Screen Turn Off Time, and both it and the Screensaver Time are now specified in minutes, not seconds. Where previously the Screen Suspend Time period began after the Screensaver Time has elapsed, the Screen Turn Off Time period now begins at the same time as the Screensaver Time. Setting the Screen Turn Off Time to a value lower than the Screensaver Time means that the screensaver will never be displayed.

Install Notes

1. Hardware version

This firmware release applies to the PS150 hardware. It cannot be used with older PS100 hardware, and older firmware versions (prior to 2.0) cannot be used with the PS150 hardware.

2. Apply schema to Pharos/Blueprint Database

If you are using Omega with Pharos Uniprint, apply the Omega configuration schema to the Pharos Database after upgrading firmware to ensure that all new properties featured in this firmware release will be available in Pharos Administrator. Apply the schema by clicking Push Schema to Pharos Database on the PEDI screen of the SmartPAD configuration menu.

If you are using Omega with Pharos Blueprint Enterprise, the configuration schema must be updated manually. Copy the contents of the file ini_schema.xml (included in the firmware package) into the file PS150.terminal.config, available in the Blueprint\bin directory of the Analyst server.

It is always a good idea to back up the database before applying changes.

Note: You must apply Hot Fix 17 to Pharos 7.1 or Hot Fix 14 to Pharos 7.2 before updating the configuration schema on Pharos Uniprint. These Hot Fixes contain an update to the EDI Server that allows the configuration schema to be updated to version 2.1.0 and later. Hot Fixes can be downloaded from the Pharos web site.

3. Omega requires SQL Server 2000

While Pharos Uniprint can be installed on SQL Server 2000 or SQL Server 7, Omega installs must use SQL Server 2000 (or MSDE 2000). If SQL Server 7 is used, Omega terminals may be unable to obtain their configuration information from the Pharos Database, and the error "'getutcdate' is not a recognized function name" appears at Omega terminals.

4. Omega Administrator browser support

The Omega Administrator web application (see below) can be viewed with Microsoft Internet Explorer 6.0 or later, and Mozilla Firefox 2.0 or later. Other browsers, e.g. Opera, may work, but are not officially supported.

Omega Administrator's Remote Control application, which allows you to interact with the SmartPAD display remotely, requires version 1.4 or later of the Sun Java Runtime Environment.

5. Custom themes no longer supplied by Pharos

With the addition of user theme customization, it is no longer necessary to obtain custom themes from Pharos Systems. All theme modifications are now performed from the Omega Administrator web application.

Note: The theme format is not version specific - it is no longer necessary to ensure that theme versions always match the current firmware version. Omega will ignore any invalid information it encounters in a theme file. Themes in the old .th format (prior to PS100 version 1.4.4) will not work with the PS150 hardware, however

Known Issues

Using a Billing Gateway with Omega

If Omega terminals are being used with a Pharos Billing Gateway, and users do not have accounts in the Pharos system, a script with the following content must be created and attached to the Bank's Logon event:

PlugIn.Result = true;

A Billing script is also needed if you wish to use the Blackboard TIA gateway with arrears accounts - contact Pharos Support for details.

Omega requires Pharos certificates for SSL

The SSL certificates used by Omega are certified to have been generated by Pharos Systems. If your EDI Server is using a certificate generated by another certification authority, then the Omega devices that communicate with it will not work. Contact Pharos for assistance in adding a CA certificate to your Omega devices.

Server name restrictions when using SSL

When using SSL, server names cannot contain the underscore character ( _ ).

Known Issues with Omega Administrator

The following Known Issues exist for the Omega Administrator web application:

Using the web browser's Back and Forward buttons is not recommended while using Omega Administrator.
If the Remote Control screen is left idle for a long time it may not respond well. Click the Remote Control link again to reload the page.
Number of copy lines must be a power of two

The number of copy lines configured must be a power of two (i.e. 1, 2, 4 or 8); otherwise copying may not work, generating an error saying that copy lines are not configured correctly. Configuring copy lines using the copier training wizard usually results in the correct number of copy lines, unless you click the Save Current button and exit without performing all tests - in this case it is possible to end up with the wrong number of copy lines configured.

Possible time discrepancies

When the SmartHub starts up, it reads the time from the BIOS. When it first contacts the Pharos EDI Server, it receives the correct system time; however, this does not update the BIOS time. This means that it is possible in some situations for the wrong time (i.e. the BIOS time) to be displayed. Any such discrepancies should not stay for long, as the correct time will be retrieved as soon as the EDI Server is contacted. If this does cause problems, you may need to update the BIOS with the correct time.

Communication timeout may be longer than configured

Due to the fact that Omega sometimes re-tries to connect to the EDI Server if the first connection attempt is not successful, it may take longer for the communication attempt to timeout than the time configured for the Timeout property on the PEDI screen of the SmartPAD configuration menu.

Cause:
The (Print) Spooler service was not started.
Solution Windows 2000:
Start the Print Spooler service.
Solution NT4:
Start Spooler service.


UPDATE:
The tool will not work when migrating from SQL 2000 due to a current bug that is being investigated.


Pharos supplies two small command line tools to help in the process of migrating the Pharos Database in a Uniprint Suite install to a new server:

  • DatabaseMigrationTool.exe - this tool copies the Pharos Database from its current server to the new one and upgrades it to version 8.1 of the Uniprint Suite if necessary.

  • NameSyncTool.exe - this tool configures the Pharos Database and registry with the hostname details of the new server, and optionally propagates these changes to the other dependent servers.


To migrate the Pharos Database to a new server, ensure that you have met all the requirements outlined in the Pre-install section of this document, and then run the database migration tool on the new server. When the database migration tool completes, it automatically runs the name synchronization tool to update the Pharos Database with the new server's name. The name synchronization tool can also be run by itself if the server's name is changed after the upgrade. For more information on how to use these tools, see "Migrating the Pharos Database" and "Updating the Database Server Name" sections below.


Migrating to a new Print Server

For systems where the Print Server is installed along with the Database and Principal Services, the suggested procedure for migrating:

  1. Migrate the existing Uniprint database to the new server by running the DatabaseMigrationTool.
  2. Migrate the Print Server’s printers and queues using the Microsoft Print Migrator tool (Microsoft Windows Server 2003 or older) or using the Printer Migration Wizard (Microsoft Windows Server 2008 and Microsoft Windows Server 2008 R2).
  3. Shutdown the old server.
  4. Rename the new server to use the old server's name.
  5. Update the Pharos Database and Registry following the name change by running the NameSyncTool.

Renaming the new machine back to the name of the original Database & Print Server will mean that no other servers or clients will need to be altered to maintain connectivity with the server.


Pre-install

Before running the server migration tools, take note of the following requirements:
  • Install the Pharos Database and Principal Server on the new server. You must install Uniprint Suite 8.1 on the new server.
  • The old server must be running one of the following Uniprint versions: 5.0, 5.1, 5.2, 5.3, 6.0, 6.1, 7.0, 7.1, or 8.0.
  • Both servers must be running SQL Server 2000 or later. If the new server is running SQL Server 2000, you need to perform additional steps. The migration tools rely on libraries from the SQL 2005 native client. These libraries are not installed with SQL Server 2000. You can download the necessary installers from Microsoft: SQL 2005 Native Client downloads. The two specific packages required are the base native client package (sqlncli), and the XMO package.
  • When running the tools, you need to be logged on as a user with administrator rights on both servers (typically a domain administrator).
  • The tools, along with all the deployment files, must be copied to the new server and run from there.

Migrating the Pharos Database

To migrate and upgrade your database using the Database Migration tool, follow these steps:

  1. Stop all active Pharos Services on both hosts.
  2. Extract the deployment files provided in the zip file and copy these files to the new server.
  3. Run the Database Migration tool from the command line on the new server:

DatabaseMigrationTool.exe -OS oldservername [-OU oldsqluserid] [-OP oldsqlpassword] [-NU newsqluserid] [-NP newsqlpassword] [-R] [-?]

Where:

  • oldservername is the host name of the old server
  • oldsqluserid is the SQL Server username of the Pharos Database dbo on the old server
  • oldsqlpassword is the SQL Server password for the Pharos Database dbo on the old server
  • newsqluserid is the SQL Server username of the Pharos Database dbo on the new server
  • newsqlpassword is the SQL Server password for the Pharos dbo on the new server

Note: If no SQL Server authentication details are supplied, Windows authentication is used.

The following options can be specified:

  • -R - attempts to propagate the changes to all Pharos servers.
  • -? - displays Help

The Database Migration tool will attempt to detach the database from your old host, copy it to the new host (replacing the freshly installed database), perform the upgrade on the database, and update the server details in the database. It can also update registry keys on remote servers so they point to the correct Principal server afterward. This last step will assume remote registry access for the logged in user, so servers with separate account databases may not be changed and will need to be adjusted manually.

A log file for the migration operation is created in the Pharos\Temp directory.

Updating the Database Server Name

The Database Migration tool will run the Name Sync tool as part of its operation, but the Name Sync Tool can also be used as a standalone tool. The tool requires remote registry access for the logged in user, so servers with separate account databases may not be changed and will need to be adjusted manually.

To update the Database Server name using the Name Sync tool, run the Name Sync tool from the command line on the new server:

NameSyncTool.exe [-U userid -P password | -W] [-R] [-?]

The following options can be specified:

  • -U userid -P password - use SQL Server authentication (where userid and password are the logon details for the sa account)
  • -W - use Windows authentication
  • -R - update other Pharos servers remotely (to use this new name for the database server)
  • -? - display Help
Copyright © 1994-2009 Pharos Systems International, Inc.

 

To download the version of the Server Migration Tools for your version of Uniprint, visit http://pharos.custhelp.com/app/uniprint. Uniprint 8.3 and 8.4 use the tool provided for Uniprint 8.2; there is a script update for Uniprint 8.4 that must be run for that version.

The following steps should manually uninstall the Pharos Popup Client. They must be carried out in the order described below:

  1. Stop the Pharos Systems ComTaskMaster service.
  2. Run the profiler manual uninstall as follows:
    1. Go to Program Files\PharosSystems\OutputManagement\PrintTracker. If the folder doesn’t exist, create it.
    2. Check for a file called profiler.dll. If the file is not there, copy in the one attached.
    3. Open a command prompt in that location and type: rundll32 profiler.dll,Exec uninstall
  3. Uninstall the ComTaskMaster service as follows:
    1. Ensure the Services window is closed
    2. Go to Program Files\PharosSystems\Core. If the folder doesn’t exist, create it.
    3. Check for a file called CTskMstr.exe. If the file is not there, copy in the one attached.
    4. Open a command prompt in that location and type: CTskMstr.exe -unregserver
  4. Delete folders:
    1. Ensure the command prompt window (from 3, above) is closed.
    2. Go to Program Files\Pharos. If it exists, delete the folder (and contents).
    3. Go to Program Files\PharosSystems. Delete the folder (and contents).
  5. Check for the following registry keys. If they exist, delete them:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Pharos
    • HKEY_LOCAL_MACHINE\SOFTWARE\PharosSystems
  6. Restart the Print Spooler service in Services.

The PC should now be back to as it was before the Popup Client was installed, and should now be able to install a new package.

If any of these points fail don’t go on to the next step. Please capture the error and report it to Pharos Support for advice on how to continue.

1. Run the PopupModule.exe module.
2. Make the initial registry modification of adding the Uniprint driver:

a. Set the registry key:

SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT x86\Print Processors\Uniprint

              i. Create a new key called Uniprint (key)
             ii. Within that key create a new string called driver
             iii. Paste the following dll into that value unipcpnt.dll
             iv. Restart the print spooler service


b. Start Spooler service. The registry entry should be entered in order to successfully uninstall the old version.
c. Reboot

3. Then restart in safe mode and delete the Pharos & PharosSystems folders.
4. Reboot, and run the PopupModule.exe again.
5. You should be able to see the LPT1 & PharosPort ports and add a printer.

Install packages are created in Pharos Administrator

The process of creating install packages involves the following steps:

 

     1.  Prepare the web site that packages and modules will be written to (if one is used)
     2.  Make sure that printer drivers are configured correctly for all Spool Queues and print servers
     3.  Set up Package Definitions and global properties in Pharos Administrator
     4.  Build packages based on the definitions

 

Preparing the Web Site (Optional)

 

If packages are to be made available for download, or if Lite packages (which download the necessary modules from a web server) are being used, the web server that will host the packages and/or modules should be set up before creating packages.
If a web site is already present, all that needs to be done is designate a location for the packages. If a web site does not already exist, one can be set up from the Pharos installers. Select “Web Server” from the Select Role screen, then select “Uniprint Web Site” on the Select Components screen. When the Uniprint Web Site is installed, the Package Root Path and Module URL properties (see below) are automatically set to the Uniprint Web site Site’s directory and URL.

 

Note: The Package Root Path property is set to the full path to the Uniprint directory, e.g. \\SERVER\C\Inetpub\wwwroot\Uniprint\. For security reasons, it is best to make the Uniprint directory into a network share with appropriate permissions, then change the Package Root Path to this share name, e.g. \\SERVER\UniprintWebSiteShare\.

 

Note: Even if you do not need the Uniprint Web Site, it may be a good idea to install and use it for testing, then set up the real web site once everything is working.

 

Setting up Printer Drivers

 

Before creating install packages, make sure that all Spool Queues are using the correct drivers (check the Driver property on the Device tab of the Spool Queues context). The drivers specified for each queue must match the drivers in use on the printers that the queues forward jobs to.
The operating systems supported by each package created depend on the drivers found on each Print Server. To ensure that install packages are available for all operating systems, ensure that drivers for all operating systems are installed on all Print Servers:

 

     1. On each Print Server, open Control Panel > Printers and Faxes.
     2. For each printer that users can print to:
          a. Right-click on the printer and select Properties.
          b. On the Sharing tab, click Additional Drivers.
          c. In the Additional Drivers dialog box, select the check boxes for the additional environments and operating systems you need, then click OK.

 

Note: Windows NT4 printer drivers can be used on Windows 2000/XP/2003. If Windows 2000 drivers are not available, but NT4 drivers are, packages will be created for Windows 2000/XP/2003 using the NT4 drivers.

 

Setting up Package Definitions and Global Properties

 

Install packages are created according to Package Definitions, which contain information on the contents and properties of install packages. Package Definitions are set up in Pharos Administrator at Distribution System > Package Definitions.

Two options are available when creating Package Definitions:

 

You can use the Package Definition Insert Wizard to create one definition for each Spool Queue in the Pharos Database by clicking the button.

 

You can use the Package Definition Insert Wizard to create a single definition, which may contain multiple Spool Queue modules, by clicking the button.

 

Note: If you wish to include an EULA in your install packages, have it ready as a text file before creating Package Definitions.

 

When creating Package Definitions, you must specify the following:

     1.  A name for the definition. If you are creating definitions based on Spool Queues, each definition will automatically be named for the Print Server and Spool Queue it relates to.
     2.  The Spool Queue modules to include in the package. If you are creating definitions based on Spool Queues, each definition will contain only the Spool Queue module for the queue it applies to.
     3.  Whether or not to include an un installer in the package
     4.  The full UNC path to the text file containing the EULA (if one is to be used).

 

All Package Definition properties can be edited in the Package Definitions context after creation, with the exception of the OSes Supported and Last Build Time properties.

 

Note: When Package Definitions are first created, the OSes Supported field contains “<Must rebuild>”. Available operating systems are not known until the package creator is run (see below).

 

In addition to the information contained in the Package Definitions, two global properties affecting install packages are available on the Packages tab of the System Properties dialog (File menu):

 

The Package Root Path property determines the location that install packages will be placed in when they are created.
The Module URL property sets the URL that Lite packages will download modules from.

 

Note: These properties are automatically configured if the Uniprint Web Site is installed.

 

Building Packages

 

The Package Definition Insert Wizard gives the option of building packages as soon as the wizard is complete. Packages based on all Package Definitions can be built at any time by clicking the button on the Package Definitions context toolbar.
The package creator is a separate executable launched by Pharos Administrator. This executable, PackageCreator.exe is located in the Pharos\bin directory, and can also be run from the command line—see below for details on command line options.
The package creator checks the Print Server(s) for all Spool Queues specified in the Package Definitions to determine which operating systems printer drivers are available for.

 

Note: For this reason, the account running the package creator must have rights to read files on all Print Servers.

 

Driver files are copied and included in the relevant packages as they are built. For each Package Definition, the following files are created:

 

Full packages for each available operating system.
One Lite package.
Modules for all components and operating systems included in the full packages.

 

In addition, a “manifest” containing details of all modules and packages is created. This file, called Manifest.xml, is an XML document used by the package updater to determine what the latest versions are. It is formatted with an XSL style sheet, and can be viewed in a web browser. When viewed in this way, it contains links to all packages created, organized by operating system. Packages can be grouped together on the web page by specifying a Web Page Group value for Package Definitions.

 

Note: Click the internet page button on the Package Definitions toolbar to view the manifest as a web page.

 

Packages are created in the directory specified by the Package Root Path property (File menu > System Properties dialog > Packages tab). Modules for the Lite installers are created in a sub-directory under the main packages directory called modules. Clicking the Show Files button on the package creator’s progress dialog opens Windows Explorer to this location.