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

You may need to recreate the SQL ODBC connection on your client. The instructions on how to do this are below:

 

1) Go to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC).
2) Go to the System DSN tab.
3) Click "Add".
4) Select SQL Server from the list and click "Finish".
5) Specify the name of the data source as PHAROSReports, select your Pharos Principal Server from the server list and click "Next", overwriting the existing data source.
6) Select the radio button "With SQL server authentication..." and specify the SQL sa Login ID and Password. This is only used for testing the connection.
7) Click "Client Configuration" and confirm that the TCP/IP radio button is selected under "Network libraries", the correct server alias and the server name is specified (the host name of your Pharos Principal Server). Also confirm that "Dynamically determine port" is checked. Click "OK".
8) Click "Next".
9) Check the "Change the default database to" checkbox, select pharos and click "Next" the click "Finish".
10) Click "Test Data Source..." to confirm the connection works, click "OK" and "OK" to exit Data Sources.

 

Once this is done, test Pharos Reports. If it still fails, in step 7 specify the server IP address instead of the host name for the server alias.

How do I install xp_encrypt?

Posted by toleary Aug 2, 2013

Pharos Systems supplies an extended stored procedure that can be called using T-SQL to encrypt passwords into the form used to store them in the database. The extended stored procedure, XP_Encrypt.dll, can be obtained from Pharos Systems on request. It must be installed before it can be used in scripts.

 

Note: There are two versions of XP_Encrypt.dll: one for SQL Server 7 only and one for SQL Server 2000 (which also supports SQL Server 7). Make sure you have the correct version.

 

Installing XP_Encrypt.dll

 

To install the extended stored procedure, copy XP_Encrypt.dll to your SQL Server \Binn directory (depending on which version of SQL Server you use, this will be MSDE\Binn, MSSQL7\Binn, or Microsoft SQL Server\MSSQL\Binn).

 

Add your new extended stored procedure by using the SQL Server Enterprise Manager, or by using the SQL Server Query Analyzer to execute the following SQL command against the master database:

 

     sp_addextendedproc 'xp_encrypt', 'XP_Encrypt.dll'

 

You may drop the extended stored procedure by using the SQL command:

 

     sp_dropextendedproc 'xp_encrypt'

 

You may release the DLL from the server (to delete or replace the file), by using the SQL command:

 

     DBCC xp_encrypt(FREE)

 

In order for a script to use the xp_encrypt stored procedure, the "pharos" account in SQL Server must be assigned EXECUTE permissions against the master database in the SQL Server Enterprise Manager.

 

To use the extended stored procedure, call it from a SQL Server SQL script. When called from a script, it expects two arguments:

 

     - The first argument is the password to be encrypted.
     - The second argument must be OUTPUT.

 

The parameters can be passed either by name or by position (unnamed). If the remote stored procedure call is made with some parameters passed by name and some passed by position, an error occurs.

 

Sample Script

 

Below is a sample SQL script that uses xp_encrypt to update a user’s password:
create procedure change_users_password
( @user_id varchar(16),
@new_password varchar(16)
)
as
begin
declare @crypttext varchar(64)
-- encrypt the password and put it into @crypttext
exec master..xp_encrypt @new_password, @crypttext output
-- update entry in database
update people
set password = @crypttext
where id = @user_id
end

Adding the backup to the Master Database:

1. Create the backup procedure in the Master database:

USE master
EXEC sp_addumpdevice 'disk', 'Pharos_backup', 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup'

2. Check to see if the backup procedure was inserted correctly:

select * from master.dbo.sysdevices

Create the backup job:

3. Scroll down to SQL Server Agent

4. Right Click on Jobs and choose New Job .

Under the General Option:

5. Set Name = Pharos Database Backup
6. Set Owner = sa

Under the Steps option:

7. Click on New
8. Step Name = Database Backup
9. Type = Transact-SQL script (T-SQL)
10. Runas is blank
11. Database = Master
12. Command (Copy and paste the following):

backup log pharos with truncate_only backup database pharos to pharos_backup with init

13. Keep the advance options standard.

Under the Schedule option:

14. Name = Database Backup Schedule
15. Schedule Type= Recurring
16. Occurs = Daily
17. Set the date and time (1:00am) when you would start then click apply

If you would like to complete a test, run the following query:

USE master
backup log pharos with truncate_only backup database pharos to pharos_backup with init

Then check to make sure the backup file was created in the following directory:

'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup'

The EDI Server runs as part of Microsoft Internet Information Services (IIS). For security reasons, IIS runs under a special account that can read and write to only a small number of directories. (This is so that if the IIS server is compromised, the damage can be contained.) It is likely that this account does not have permission to write to the directory you specified.

Configure the directory permissions for the directory that you want the logging output to be written to, so that the IIS account has permission to read and write to it. The exact account used by IIS depends on its version and protection level. The simplest solution is to allow permissions for all three of the possible accounts, as follows:

  1. In Windows Explorer, right-click on the directory that you want the logging output to be written to and select Properties.
  2. On the Properties dialog, select the Security tab and click Add.
  3. Click Locations and select the machine itself at the top of the list.
  4. Enter "ASPNET" in the Enter the object names to select box and click OK.
  5. The "ASP.NET Machine Account" now appears on the security tab. Select this account and tick the Allow box for the Write permission. Click Apply.
  6. Repeat steps 2 - 5 for the accounts "IWAM_<MACHINE NAME>" ("Launch IIS Process Account") and "IUSR_<MACHINE NAME>" ("Internet Guest Account"). Replace <MACHINE NAME> with the name of the PC.
  7. Click OK to close the Properties dialog.

Clicking the Change Control button propagates information from the Database to all Pharos services. A Change Control is only required if you change some of the information that is cached at servers.


You should use the Change Control button after you:

  • Update a Bank
  • Update a Logon DLL
  • Update Print Server settings
  • Update Spool Queue or Printer settings
  • Update Job Cost Methods
  • Update Copier settings
  • Update Terminal settings (where you are using PS20 devices, you also need to stop and start the Monitor Translator)
  • Update a Pharos Remote Layout
  • Update a Pharos Station
  • Update Pharos Popup Questions
  • Update any SignUp Global Parameters
  • Update any SignUp Branch Settings
  • Change Access Times
  • Change Prompts
  • Change Server Properties
  • Update Scripts


You do not need to use the change control button when you:

  • Update User information
  • Update User Group information
  • Update Discount Rates
  • View Transactions
  • Update Packages
  • Add a Message of the Day
  • View Alerts
  • Set up an Export Profile
  • Open a Support Incident
  • View License Limits
  • View Server properties

Please note there are situations (such as updating a script) where a service may behave inconsistently until a change control is issued.

I am installing the SignUp Client on a PC that has Deep Freeze installed. The Pharos Installation and Configuration manual states that when the Pharos installers detect the presence of Deep Freeze, they display a screen that allows me to enter the path to a “safe” location where the SignUp Client can store configuration information, so that it will not be erased on a reboot.

However, when I run the installers, this screen doesn't appear, and I am unable to specify a "safe" location.

The SignUp Client installer checks for the presence of a Deep Freeze system file in order to determine whether or not Deep Freeze is installed on a PC. In newer versions of Deep Freeze, this file is not present in the expected location, so the check fails and the Deep Freeze screen is not displayed.

In this case, you must specify the "safe" location manually after the SignUp Client is installed. Specify the location by editing the registry on the SignUp Client PC. The relevant value is:

HKEY_LOCAL_MACHINE\SOFTWARE\Pharos\SignUp Client\ConfigFileDir

Pharos Support for Windows 8 and 8.1


Windows 8.0

Uniprint 8.3 General Release

  • Not Supported


Uniprint 8.3 Service Pack 1 (SP1)

  • Pharos Station
  • Popup and Notify Client


Uniprint 8.4 General Release

  • Pharos Administrator
  • Pharos Remote
  • Pharos Reports
  • Pharos Station
  • Popup and Notify Client
  • SignUp Client


Windows 8.1

Uniprint 8.3 General Release

  • Not Supported


Uniprint 8.3 Service Pack 1 (SP1)

  • Pharos Administrator: Not Supported
  • Pharos Reports: Not Supported
  • Pharos Station: Untested
  • Popup and Notify Client: Requires the additional Hot Fixes listed below (or later)
    • Print Services - Revision 411
    • Popup Client Installer - Revision 396
    • Pharos Administrator - Revision 386: This Hot Fix is required by Popup Client Installer - Revision 396, even though Pharos Administrator 8.3 SP1 itself isn't supported


Uniprint 8.4 General Release

  • Pharos Administrator
  • Pharos Remote
  • Pharos Reports
  • Pharos Station
  • Popup and Notify Client
  • SignUp Client

No.

The Pharos upgraders can upgrade most older versions to the current version, so you only need to upgrade once to get from your current version to the latest version.

The only exceptions are if you are upgrading from a very old version (pre version 5.0) - contact Pharos Support in these cases.

Mac Client Interactions
1.  Print jobs coming through CUPS are intercepted by a custom LPD backend.
2.  The backend invokes the Popup Client to collect Popup data.
3.  The Popup Client obtains Popup Questions from the Popup Server and interacts with the user.
4.  User answers and job properties from CUPS are collated and returned to the backend.
5.  The backend prepends the information to the current spool file, and sends everything to the LPD Server.
6.  When a job has been fully spooled on the server, it is picked up by the Print Server.
7.  If Informed Print is configured, the Print Server sends an Informed Print Request to the Notify application.
8.  If required by the Print Server, the Notify application returns a response.
9.  If all is well, the Print Server will either release the job, or hold it for Secure Release Here.

 

 

 

Windows Client Interactions
1.  Print jobs coming through the Spooler are intercepted by a custom Port Monitor.
2.  The Port Monitor invokes the Popup Client to collect Popup data and job information.
3.  The Popup Client launches the Popnet executable (if not already running) to keep track of a file that contains Last Answers.
4.  The Popup Client obtains Popup Questions from the Popup Server and interacts with the user.
5.  The Popup Client requests job information from the AppTracker Task, which collects data by injecting code into running applications.
6.  The AppTracker returns available data. No data is available with Terminal Services, Vista or Office.
7.  The Popup Client provides Popup Answers and AppTracker data back to the Port Monitor.
8.  The Port Monitor prepends the information to the current spool file, and sends everything to the LPD Server.
9.  When a job has been fully spooled on the server, it is picked up by the Print Server.
10.  If Informed Print is configured, the Print Server sends an Informed Print Request to the Notify Task.
11.  The Notify Task displays information to the user using the Popup GUI, and obtains a response, if required.
12.  If required by the Print Server, the Notify Task returns a response. Status balloons do not require a response.
13.  If all is well, the Print Server will either release the job, or hold it for Secure Release Here.

This happens when the new Pharos PopUps for Mac version 10.8 is installed in combination with the older 8.1 version of the PopUp package.  The PopUp error appears repeatedly, and will generate a new error dialogue box every few seconds.

This can be remedied in 3 different ways:

  • By going to the Terminal under Applications --> Utilities --> Terminal and typing "killall Popup" and hitting the Return key
  • rebooting
  • or logging out and logging back in.

The fix will be in removing the Popup Login Item from the Users & Groups section in the System Preferences of the Mac as the 8.3 launchd process starts the Popup process instead of the older Login Item method.

Pharos is aware of the challenge, and is working on a solution which will be posted on Pharos KB article 1783


When I install a Popup Package on a Windows 7 client machine I notice that the printers are grouped and not displaying individually.

How do I undo this grouping in Printers & Faxes?

 

 


Below is the information one of our customers has put together for us to share as this is not a Pharos caused issue and is controlled soley by the Windows 7 Operating System.

Pharos takes no responsibility for any of these changes to your system should you attempt one of the solutions below.

In working with Microsoft we were unable to find a fix address this behavior; however, we did find several indirect solutions (some of which are more usable than others in my opinion). A summary of these indirect solutions are below.

 

The behavior was documented by Microsoft and one workaround was documented in the following Microsoft KB Article:
http://support.microsoft.com/kb/2015694

 

A blog post was also created by the technician I was working with:
http://blogs.technet.com/askperf/archive/2010/03/02/windows-7-where-are-my-printers.aspx

 

A variant on this resolution (first link) would change the 5 listed steps to the following (my preference):
1)     Open the registry editor (Regedit.exe) and navigate to:  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Control Panel \NameSpace
2)     Right click on NameSpace and choose 'New Key'
3)     Name this new key {2227a280-3aea-1069-a2de-08002b30309d}   (be sure to include the brackets)
4)     In the right pane, edit the value of 'Default' as 'Printers'
5)     Close Registry Editor and refresh the Control Panel
a.     Note that the View will need to be switched from Category to either Small Icons or Large Icons to see the new icon.

 

I'm fairly certain that step 4) has no impact in both scenarios.  The KB method will place an icon on your desktop to an alternate printers interface/UI via the registry.  The method above will place a similar icon in your Control Panel (my preference) via the registry.  Neither icon appeared to be delete-able for the end user (prevents accidental deletion); however, it means that a method to undo the above should also be provided to the end user.  Both methods are scriptable.

 

Here is a portion of a batch file I put together quickly to add the functionality above (Control Panel Icon) into place:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@echo off
ver | find "6.1." >nul
if %errorlevel%==1 echo Windows version does not appear to be Windows 7.  No changes will be made.
if %errorlevel%==1 goto BYPASS

 

reg query "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion" /v "ProductName" | find "Windows 7" >nul
if %errorlevel%==1 echo Windows version does not appear to be Windows 7.  No changes will be made.
if %errorlevel%==1 goto BYPASS
if %errorlevel%==0 echo Windows version appears to be Windows 7.

 

reg query "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel\NameSpace\{2227a280-3aea-1069-a2de-08002b30309d}" >nul
if %errorlevel%==0 echo Key already exists.
if %errorlevel%==0 goto BYPASS
if %errorlevel%==1 echo Key does not exist.

 

reg add "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel\NameSpace\{2227a280-3aea-1069-a2de-08002b30309d}" /ve /t REG_SZ /d "Printers"  >nul
if %errorlevel%==1 echo Problem adding key.
if %errorlevel%==0 echo Key added.

 

:BYPASS
echo Done.
pause
exit
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

Here is a portion of a batch file I put together quickly to remove the same functionality:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ver | find "6.1." >nul
if %errorlevel%==1 echo Windows version does not appear to be Windows 7.  No changes will be made.
if %errorlevel%==1 goto BYPASS

 

reg query "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion" /v "ProductName" | find "Windows 7" >nul
if %errorlevel%==1 echo Windows version does not appear to be Windows 7.  No changes will be made.
if %errorlevel%==1 goto BYPASS
if %errorlevel%==0 echo Windows version appears to be Windows 7.

 

reg query "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel\NameSpace\{2227a280-3aea-1069-a2de-08002b30309d}" >nul
if %errorlevel%==1 echo Key does not exist.
if %errorlevel%==1 goto BYPASS
if %errorlevel%==0 echo Key exists.

 

reg delete "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel\NameSpace\{2227a280-3aea-1069-a2de-08002b30309d}" /f >nul
if %errorlevel%==1 echo Problem removing key.
if %errorlevel%==0 echo Key removed.

 

:BYPASS
echo Done.
pause
exit
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

The above scripts have not been tested and thier functionality validated with previous versions of the Windows Operating systems which is why they tried to restrict the functionality of the script to Windows 7.

 

Another method with which would place a delete-able icon on the desktop (would show awkward file extension if user's system was configured to do so) is below.
1)     Create a folder on the desktop
2)     Name this folder as 'Printers.{2227A280-3AEA-1069-A2DE-08002B30309D}'

 

We were unable to find a good method of placing any of these icons into the Start Menu (e.g. institutional specific program files group).  I believe the rename folder version above allowed you to customize the folder name to something other than 'Printers' and worked in at least one non-Windows 7 Windows operating system.

 

The customer did not not test the Server 2008 R2 (or non-R2) terminal services environment to see if this problem persisted into that operating system.

 

Hopefully this information is useful and if you do attempt any of these steps Pharos is not responsible for changes you make to your system.

Should you have further questions on this please contact Microsoft and open a support case with them.

The Pharos suite of products uses TCP/IP for all client/server communications. The attached document lists the ports that the various Pharos components use by default, and discusses issues that arise when Pharos components attempt to communicate through firewalls using these ports.
See Attached TechNote

1. Create an Install Package and run it on one PC.

2. Modify the printer registry with the values you want. Or make the changes to the printer in the Wndows Printers folder, which should modify the printer registry.

3. Export that specific printers registry key.

4. Using the exported registry key create a batch file that silently executes that registry key (use regedit /s). Name this batch file "PopupReg.bat." (see attachment)

5. Use WinRAR to create a zip file with these two files. Once the zip file is created, open it with WinRAR. Make the zip file self-extracting by clicking the SFX button, configuring the following settings:

     a. In the "Advanced SFX" options on the general tab set “Path To Extract” as C:\Progra~1\Pharos\temp\.
     b. On the "General" tab set “Run after extraction” as PopupReg.bat.
     c. On the "Modes" tab check the “Hide all radio button” and the “Overwrite all files” radio button.

6. Store the resulting exe file on the principal server in the directory C:\Program Files\Pharos\Bin\Shared\. Delete the original files.

7. In Pharos Administrator create a Custom Module:

     a. For the Filename setting, browse for the exe file you just created and select that.
     b. For the Module Behavior property check these settings:

“Continue install if module fails”
“Module does not write results.txt file”

8. Add the Custom Module to your Popup Packages.

Pharos products support the current set of Windows service packs, hot fixes and updates at time of release unless otherwise specified.

Pharos does not QA each Windows update as they are released and normally only does so during Pharos product releases.

Typically, Windows updates do not cause problems with Pharos applications, however if conflicts are found with an update and a current Pharos product, Pharos will provide a fix where applicable.

Of course, it is always important to test changes to your production environment or to have a thorough roll-back plan should the unforeseen occur.

Possible causes of this problem are:

  • The employee may have printed to a secure queue when they thought they were printing to a non-secure one. They will be waiting for the job to print out, when in fact they need to release it from a terminal.
  • If the terminal has been improperly configured, so that it is associated with a device other than the one it is attached to, then employees will not see the job print out at the device. The job will probably have printed, but at a device somewhere else. Use Blueprint Administrator to check that the terminal the employee is using is associated with the device they are releasing jobs to.
  • If the employee is printing to a Print Group, it may be that the device the job was released to uses a different Printer Description Language (PDL) from the queue that it was initially printed to, meaning that the device cannot print the job. It is a requirement that all devices in a Print Group must use compatible PDLs - check the drivers of the devices in the Print Group that the employee is printing to to ensure that they are all compatible.

Pharos Systems have identified a problem with job arrival that occurs under the following conditions:

  • Jobs are regularly released with Pharos Remote.
  • The 'charge user' box is explicitly unchecked.

When the Job ID for one of these uncharged jobs is "recycled" by the printing subsystem, the Print Server will incorrectly ignore this new job. A fix for this problem has been released and can be downloaded from the 8.1 hotfix page.  The hot fix is now the recommended way to solve this issue.

The following workaround is left for reference.

A workaround is to always leave the "charge user" box checked when releasing jobs with Pharos Remote. However, this can cause problems if the user a) does not exist in the Pharos database, or b) you do not want the user's account to be debited. To get around this issue, a billing script can be applied to the Pharos Remote bank to bypass regular billing. An example script is attached.

Note: This script will bypass ALL billing done through Pharos Remote. Customers who use a mixture of charging and not charging when printing jobs with Pharos Remote should contact Pharos Support for advice.

The following error shows up in the server Application Event Log every few minutes:

Event Type: Error
Event Source: PSDatabaseSvr
Event Category: None
Event ID: 4000
Date: 5/29/2006
Time: 8:22:38 PM
User: N/A
Computer: SERVER_NAME
Description: Caught a general error with message '[PSComDBServer::ComputerSessionInsert] COM -- ADO error: IDispatch error #3119. Description: INSERT statement conflicted with COLUMN CHECK constraint 'CK__transaction__qty__76619304'. The conflict occurred in database 'pharos', table 'transactions', column 'qty'.'

 

 

Cause:

This error occurs when data being sent from the Signup Client(s) does not match the expected format of the database. In this case the 'qty' column in the transactions table.

Solution:

This problem should not occur in Pharos 7.1 and later. If upgrading is not currently an option, this problem can be solved as follows:

  1. Run the SQL Profiler using the default trace. This will log the exact query being run against the database, which should provide more information. The Profiler will need to run until the errors are captured.

    Note: before starting you might want to purge the Event Log so that you can start clean and see only the current errors.
  2. Once errors are seen, what you will need to do in order to locate the machines causing the error is to compare the Event Log times (when the error occurs) against the times in the Profile Log. After matching the times look for entries like the sample below (in the TextData column of the Profile log):

    *** exec computer_session_insert '2252003846245', 'PC_NAME', 2, 'DATE_TIME', -28, 0, 1

    The PC_NAME will be the name of the machine sending the "bad" data.
  3. Once found go to that machine and delete the files:

    SUClientAccessPeriods
    SUClientScheduleReservations
    SUClientSessionData
  4. Restart the machine. This will recreate those files. Check to see if that machine has stopped sending errors.
  5. Verify that the machine(s) are running the current Signup Client software.

For additional information see: The conflict occurred in database 'pharos', table 'computer_transactions'

When multiple users print to a Popups queue using Windows Terminal Services, the Popup Client dialog appears immediately for the first user. However, subsequent users have to wait for the first user to close the dialog before it will appear on their workstations. This is a known limitation of using Popups on Terminal Services. It also means that if a user does not answer the questions and leaves the Popup dialog open, all other users are unable to print and use Popups. This situation can be corrected by creating a new registry key in HKEY_LOCAL_MACHINE\ Software\ Pharos\ Popup Client on the terminal server running the Popup Client:

  • Name: FinishDialogTimeout
  • Type: REG_DWORD
  • Meaning: How long (in seconds) the Popup dialog stays on screen. If this timeout expires, the dialog closes and the print job is not sent. If this key is not present, the dialog remains indefinitely.

Similarly, when multiple users receive user notification relating to their print jobs, from the Informed Print feature or from Scripts, the notification appears immediately to the first user but subsequent users have to wait for that notification to be closed or to time out. This is also a known limitation of using Popups on Terminal Services. Unlike the Popup Client dialog, the notification always does eventually time out. If the notification is sent from a Script, the timeout is set within the Script. Timeouts for Informed Print notifications are set by a registry key in HKEY_LOCAL_MACHINE\ Software\ Pharos\ Print Server on the computer running the Print Server:

  • Name: Informed Print Timeout
  • Type: REG_DWORD
  • Meaning: The amount of time (in seconds) that Informed Print messages will be displayed for. This value must be manually created.
  • Default: 15

 

See attached document.

Some features of Uniprint 8.2 require new versions of terminal or iMFP to utilize the enhanced capabilities. The table below lists the current support for each terminal or iMFP family.

For a description of the Uniprint 8.2 features referenced here, please read the New Features document contained in the Documentation folder of the Uniprint 8.2 download image.

 

Terminal or iMFP family Card Registration Enhanced Grant Support [1]
iMFP for Canon No No
iMFP for HP No No
iMFP for Konica Minolta No No
iMFP for Lexmark No No
iMFP for Ricoh No No
iMFP for Samsung No No
iMFP for Sharp No No
iMFP for Xerox No No
PS60 N/A - no user interface N/A - no user interface
PS150 Yes - as of version 2.2.2 No
PS200 Yes Yes
Virtual Cash/BOSCOP No No

 

 

Last Updated: 9th February 2011

[1] Uniprint 8.2 supports Grants on older versions of terminals or iMFPs, but the user experience is different. Refer to the Uniprint 8.2 New Features document for more information.

This is usually the result of a mismatch between the name of the machine as identified in the WCF config file and the name encoded on the self-signed certificate automatically created on the WCF server. You will need to compare these:

 

1. To review the WCF Config File

 

Open the following file:
\Pharos\Bin\WCF\PS.vNext.SvcHost.WinSvc.exe.config

 

Somewhere close to the bottom of this file you will find a section:  <serviceBehaviors> In there will be the machine name that was recorded on install... in two separate places regarding "serviceCertificate".

 

2. To review the Certificate details:

 

Open an MMC console
File > Add/Remove Snap-in
Click Add, then select Certificates from the list of standalone snap-ins (set it to manage Computer Account, Local computer) Click OK to open the Snap-in

 

Under Trusted Root Certification Authorities > Certificates you should find a certificate entry for the machine name. 

 

The likely scenario is that the certificate details do not match the entry in the config file, specifically that one of these has the FQDN or something similar while the other does not.

 

Edit the config file changing the two entries in the config file to match the certificate detail.

 

3. Open the following file:
\Pharos\Bin\WCF\appSettings.config

Check to make sure this line has the correct name as well and matches what the certificate was generated for and/or the FQDN that the server is using or the common name if it is using this instead:
<add key="serverAddress" value="YourServerNameHere"/>

 

3. Restart WCF and Remote, and try logging in again.

 

**Additional logging of the WCF Service can be done by following the attached text file on how to enable logging on the WCF service and determine further where the problem may be. You should contact Pharos Support with additional error messages and forward to us a copy of this log file that was produced.

I want to remove a printer from Pharos Uniprint because the printer is no longer needed and I need to install a new printer. I still want to keep the transactions from the old printer and so don't want to use the archive option which will remove all my transactions.

 

Is there any way I can keep the printer and transactions?

This is a feature available in Uniprint 8.0. However, older versions (pre-8.0) do not allow you to mark a printer as unused so that you can free up a printer license. A work around (see below) is available so that you can free up a license and continue to review the transactions.

Work-around process for older Pharos versions:

1. Open Pharos Administrator.
2. Select the System > Servers context.
3. Insert a new Server called 'obsolete' with no domain and 0.0.0.0 as the IP address.
4. Select the Printing > Print Services context and click the green insert button.
5. Add a new Print Server called "obsolete" with expired jobs set to default 600 and SNMP Status Refresh of default 60.
6. Set the Bank in the wizard to "Default Bank".
6. Close the wizard.
7. Close Pharos Administrator.
8. On the SQL Database Server run the following command in a command Window replacing the <insert printer name here> and SQL password values with the real SQL password and printer name in Pharos that you wish to remove:

 

osql -S localhost -U pharos -P <pharos SQL password> -q "update printers set server_id = (select server_id from servers where hostname = 'obsolete') where printer_id = (select device_id from devices where device = '<insert printer name here>')"

 

9. Once you have completed this command, the command should indicate that one row has been updated.
10. Restart all Pharos Services.
11. Log on to the Pharos Administrator again.
12. Select the Printing > Print Services context. You should see a new Print server called obsolete.
14. When you select the Printers section of the obsolete server the old printer should be attached to this server and marked offline.
15. You should now be able to report on the old printer and insert a new printer on the working server.

 

*NOTE: the obsolete server will be available using any Pharos Administrator; however it should not be used for anything other than reporting purposes.

 

It is not recommended you complete this workaround unless you have a good understanding of SQL and the Pharos Software Suite. Confirmation screenshots are attached to this answer to verify the steps you are performing are correct.

As of Pharos 8.0, the PrintOp feature has been discontinued. In an upgrade to Pharos 8.0 or later, all PrintOp Stations and PrintOp transactions will be removed from the system. The PrintOp Stations context no longer appears in Pharos Administrator.

As of Pharos 8.0, Standard Charging is no longer available; all Spool Queues must use a Job Cost Method. In an upgrade to Pharos 8.0 or later, Job Cost Methods that duplicate the Standard Charging settings configured for each Spool Queue are created and associated with each queue.

As of Pharos 8.0, BEAR PODs are no longer supported as Copy Control Devices, meaning that Pharos Stations can no longer function as Copy Stations. During an upgrade, any copiers associated with Pharos Stations will be disassociated and the Copy option for the Pharos Station will be removed. Network terminals will need to be added following an upgrade and the copier associated with the new network terminal before it can be used.

As of Pharos 8.0, the Message of the Day feature has been removed.

CAUSE:

Such errors occur because of Signup Clients that are trying to send transaction data that does not match the current database configuration. Note, it's also possible that there is more than one SignUp Client.

Possible reasons for the SignUp client sending invalid data are:

1.  The SignUp client doesn’t match the version of the SignUp Server.
2.  When the SignUp client was upgraded, it had old transaction records that it still needed to upload to the SignUp server.  When the client was upgraded, the old records where not upgraded.
3.  A record in the SignUp client’s transaction log has been corrupted.

SOLUTION:

The first step will be to track down the client that is sending the invalid reservations. The easiest way to do this is to use SQL Profiler to log the computer_session_insert calls made to the SQL Server. Wait until the error occurs again and then examine the SQL profiler log for the offending call (or send it to Pharos). You can check when the error occurs by checking the Alerts, or it may be possible to identify the client directly from SQL profiler.

(You might like to check the Computers context in Administrator (SignUp > Branches > [Branch Name] > Computers to see if any computers have a version number that isn't the latest one.)

NOTES:

1. The frequency of this error in the alerts should indicate roughly how long you will need to wait for it to re-occur.
2. The alert should be logged within a couple of seconds of the faulty computer_session_insert call, so knowing the time the alert is logged at will greatly assist in finding the offending computer_session_insert call in the Profiler's log.
3. As we're only interested in computer_session_insert calls in the Profiler log, we can set the profiler to filter out all calls but these. To do this, when setting up the trace properties, click on the "Filters" tab, open "Text Data" item on the tree, then "Like" under "TextData", then supply the text "%computer_session_insert%" (DON'T include the quotes, but do include the percents.)

Once the PC has been located, the next step will be to check the SignUp Client installed. If it's an older version, then uninstalling it and reinstalling in the new client will resolve the problem.

However, if the client IS up to date, then all that is required is to delete the file holding the transaction data the client is trying to upload.

If it's not an older version, then Pharos would like copies of the SignUp Client's config & session history files, so that we can determine what has gone wrong. These files can be found in the directory given by the registry key HKEY_LOCAL_MACHINE\Software\Pharos\SignUp Client\ConfigFileDir

The specific files are as follows:

SUClientAccessPeriods.bin
SUClientConfiguration.bin
SUClientPrompts.bin
SUClientSessionData.bin
SUClientStartupNotice.bin
SUClientTransactions.bin
SUClientCurrentSession.bin
SUClientScheduledReservations.bin

For the Mac SignUp client the config and session files are stored in the following locations:

/Library/Caches:
com.pharos.signup.SUClientAccessPeriods.bin
com.pharos.signup.SUClientConfiguration.bin
com.pharos.signup.SUClientPrompts.bin
com.pharos.signup.SUClientScheduledReservations.bin
com.pharos.signup.SUClientSessionData.bin
com.pharos.signup.SUClientStartupNotice.bin
com.pharos.signup.SUClientTransactions.bin

 

/Library/Preferences:
com.pharos.signup.shared.plist

Additional information:

KBase article 1051 - The conflict occurred in database 'pharos', table 'transactions', column 'qty'

Supported Canon Devices

 

Visit: Supported Canon Devices for the most up-to-date list of supported devices.

Related: How do I list the MEAP Contents and Controller Version for a Canon device?

Pharos Suite 8.3 and earlier supports Windows Terminal Services and Citrix in the following ways

 

 

Pharos Uniprint Popup clients - Pharos Popups are currently supported on Windows Terminals Services with limitations (please read the following Knowledge Base Article).

Title: Multiple Popup Problem when using Windows Terminal Services
URL: http://pharos.custhelp.com/cgi-bin/pharos.cfg/php/enduser/std_adp.php?p_faqid=915&p_created=1158027162

Pharos Popups are not supported in a Citrix environment.

 

Pharos Signup clients - cannot currently be installed and the product is not supported using Windows Terminal Services or Citrix thin client machines

Full installation and configuration information can be found in the document "Pharos Omega - Installation and Configuration". This document is included with Omega firmware releases, in the docs folder (the document's file name is PharosOmega.pdf). The Installation and Configuration manual is a detailed document that includes step-by-step instructions for setting up an Omega system, details on all configuration options and a description of the Omega SmartPAD user interface.

 

Firmware releases can be downloaded from http://www.pharos.com/support/index.html

 

Information on the configuration options available for Omega terminals in Pharos Administrator is also included in the Pharos Help (search for "Omega").

 

Note: Because Omega firmware updates are released more frequently than the Pharos Solution Suite, it is possible that the information in the Pharos Help may not be fully up-to-date. (The information on these properties in the Installation and Configuration manual will always be up-to-date.)

Installing the Pharos Database on a remote Microsoft SQL Server

 

1) Install MS SQL Server and the Pharos Principal Server (database server) on the machine that is to be used as the production Pharos Principal Server.

 

2) Once the install is complete the Pharos Database can be detached from the Pharos Principal Server and attached to the machine running MS SQL Server.

 

3) Before attaching the Pharos Database to the remote SQL Server you will need to create a login to SQL Server.

 

NOTE: The User name and Password MUST be the same as the pharos logon (dba) created during the installation of Pharos. These can be found in the following Registry location on the Pharos Server:

 

Make the "Database Name" key, "User Name" and "Password" values the same as the existing install on the old machine

 

x86 Architecture:
HKEY_LOCAL_MACHINE\SOFTWARE\Pharos\Database Server\Database

x64 Architecture:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Pharos\Database Server\Database

 


4) In the Registry (see below) you will also need to change the entry for "Server Name". The current entry will be replaced with the name or IP Address of the MS SQL Server machine.

 

x86 Architecture:
HKEY_LOCAL_MACHINE\SOFTWARE\Pharos\Database Server\Database
x64 Architecture:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Pharos\Database Server\Database

 


5) On the Pharos Principal Server you will need to remove the MS SQL Server Dependency in the Registy:

 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PSDatabaseSrv

 


Name: DependOnService

 

Remove the entry related to MSSQLServer.

 

NOTE: If the Microsoft Windows Server version installed on the server displays this information as a "binary value" when "regedit" is used (i.e. Win2000) then use "regedt32," which will display in plain text.

 

6) Attach the Pharos Database to the remote MS SQL Server and assign the Pharos User with Pharos dbo permissions.

 

To make the Pharos User the dbo, open SQL Enterprise Manager, expand the tree to:

 

SQL Server Group > “server name” > Security > Logins

 

Select the Pharos User, right-click and select Properties.

 

Select the Database Access tab and make the Pharos User the dbo (database owner).

 

*************** Note From Developers:***********************************

 

When you attach the database using SQL Enterprise manager, you get to chose the login who will be assigned as owner of the database (dbo)
So add the 'pharos' login to the new server before attaching the database.

 

This is not quite the same as setting a logon to have access to the database with role of database owner (db_owner).

 

You can only have one dbo for a database, but you can have many users (logins assigned to database) that have access as db_owner.
When this site comes to upgrade in the future any objects that are changed or added will be created belonging to that user and not belonging to dbo

The Blueprint Enterprise license key is an XML file called <CUSTCODE><DATETIME>.xml

 

The file may be supplied as a zipped ('.zip') file. This file must be unzipped before the license key can be applied.

 

<CUSTCODE> is your Customer Code: an eight-character alphanumeric code assigned by Pharos Systems, which uniquely identifies your site. Your Customer Code must be quoted in all correspondence. You can view your Customer Code (and other license details) on the License screen in the Dashboard section of Blueprint Administrator.

 

The license file contains encrypted data specifying the license parameters. These parameters control the maximum number of components such as servers, printers and users, as well as the software expiry dates. The data is stored in Blueprint Administrator.

 

Save the file to the local drive of the computer on which the Blueprint Analyst or Collector is installed. Open Blueprint Administrator and navigate to the Dashboard > License screen. Then click the Update License button, browse to the location of your new license file, and click Open to apply the new license.

 

When installing or upgrading Blueprint servers (Analyst or Collector), the license key is installed automatically by the install/upgrade wizard. You will be asked for the location of the XML file. Enter this (or browse to find it) and the license key will be installed.

 

For more information, see the Blueprint Help document "Viewing License Information". You can find this document under System Management in the Blueprint Help file.

In general, the Pharos Uniprint and Blueprint products do not specifically support a printer manufacturer or model over another. Instead, our software has support for various Page Description Languages (PDLs) that are normally encountered in most print environments.

The Pharos Page Counter that is used in Pharos Uniprint & Pharos Blueprint supports any printer that uses one of the following Page Description Languages (PDLs):

  • CAPT
  • CPCA
  • DSC
  • EMF1
  • ESC/P22
  • ESC/Page2
  • HP-GL/2
  • HP-JetReady
  • HP-RTL
  • IBMProPrinter
  • PCL (3,4,5,5c and 5e)
  • PCLXL
  • PDF3
  • PJL
  • PostScript (1,2 and 3)
  • Text
  • HBPL
  • LEMF
  • XJT
  • ZIMF
  • ZjStream
  • Canon UFR II4

If there is a PDL used by a driver not on this list, the data captured by the Pharos product may be different than what was expected based on the job parameters defined. Pharos may, based on cooperation from the driver manufacturer, modify our Page Counter to include a currently-unsupported PDL. Please contact Pharos Systems Technical Support to begin this process.

Notes:

  1. The EMF format has basic support, but prior to a hotfix recently released for Uniprint 8.0, some job attributes would not be transferred with the print job.  This affected certain printing features, such as watermarks or multiple pages per sheet (n-up).  The hotfix addresses this issues, but in some cases colour detection or other features still may not work correctly with the EMF format.
  2. The Stylus Pro line of EPSON printers need to be switched from the native, proprietary language to ESC/P2 to work. This is done by going into Properties > Advanced > Preferences > Utility > Speed and Progress > Processed by Printer ; this is on by default, switch it off to get ESC/P2.
  3. PDF spool files are quite rare, and not fully supported by the page counter.  Basic support exists to determine page size and count, but colour detection does not work.  If possible, it is recommended to use a PostScript driver, or another better supported PDL.
  4. Color detection may not work correctly in all cases. Some embedded monochrome images may be detected as color.  Please follow Canon's recommended load for this driver.  If problems exist, upgrade the iR/iR-Adv to the Multi-PDL Board or imagePASS accessory.

[Important] This procedure cannot be combined with a database upgrade to change versions.  It is only intended to move an existing database to a new server using the same version of Uniprint.  If you need to move and upgrade a server at the same time, either use the database migration tools (for upgrading to 8.0 or later) or install the older version at the destination and then upgrade the system.

Note: The collation order on the target SQL server (machine currently with no Pharos Database) must match the collation order on the current SQLserver. To check the collation orders, run the following query against each database:

select collation from syscolumns where name = 'name' and id = 1

Here are the steps to migrate your database between the two Pharos servers of the same version, using SQL 2000 Enterprise Manager:

  1. On your original server, stop all Pharos Services.
  2. In SQL Enterprise Manager, go to Microsoft SQL Servers > SQL Server Group > [SQL Server] > Databases.
  3. Right Click on the Pharos database, select All Tasks > Detach Database. Click OK when prompted.
  4. On your new Pharos server, repeated steps 1 to 3.
  5. On your new Pharos server, in the SQL data folder ( typically C:\Program Files\Microsoft SQL Server\MSSQL\Data\ ) move the files pharos_data.mdf and pharos_log.ldf out of the directory.
  6. Copy the file pharos_data.mdf from the SQL data folder of the original server to the SQL data folder of the new server.
  7. On the new server within SQL Enterprise Manager go to Microsoft SQL Servers > SQL Server Group > [SQL Server] > Databases.
  8. Right click on Database and select All Tasks > Attach Database.
  9. Click the '...' button and browse for the file pharos_data.mdf in the SQL data folder. Select it and click OK.
  10. Ensure that the field "Attach as" is pharos and the field "Specify database owner" is pharos. Click OK, click Yes, then click OK and the database should be attached.
  11. On your new server start your Pharos services ( or restart the machine ) and it should be up and running. Open Pharos Administrator to confirm everything is as you expect.

How to manually upgrade the Pharos database

On the Pharos Suite install CD, in the directory "..\database\db" there is a collection of SQL scripts. These scripts can be used to manually upgrade the Pharos database.

The names of the scripts show the version build. For instance, "dbug1950.sql" is for version build 1950.

To upgrade the Pharos db, start with the script with the next highest version number of the database build. For example, to upgrade the database from version 1211 to 1632, you will need to apply the following scripts against the database in the following order.

dbughead.sql (puts the database into a state where the upgrade scripts can be applied)
dbug1466.sql (upgrades the tables from 1211 to 1466)
dbug1573.sql (upgrades the tables from 1466 to 1573)
dbug1632.sql (upgrades the tables from 1573 to 1632)
dbugtail.sql (applies the 1632 triggers and stored procedures)

Prior to attempting a manual upgrade of the Pharos database make sure there is a current tested and verified backup.

Copy the contents of each of the scripts into the SAME SQL Server Query Analyzer window, DO NOT OPEN A NEW Query window for each script they must be run one after the other in the same window. After running each script, check the output for any error messages. While none should occur, better to be cautious.

1. To verify the current build. Open the Registry Editor and browse to:

HKEY_LOCAL_MACHINE\Software\Pharos\Installed Components

2. Note down the version (build) number value for the Pharos Database.
3. Start SQL Server Query Analyzer, and log on as the Pharos Database user.
4. Ensure that the Pharos Database is selected as the current database.
5. Open and run the appropriate upgrade files for your version of Pharos.

Upgrading from Pharos 5 or later

a. Open and run the script dbughead.sql.
b. Open and run all dbugXXXX.sql scripts, where XXXX is greater than the current version number (from the registry).
c. Open and run dbugtail.sql.

Upgrading from earlier than Pharos 5

a. Open and run the script XXX-470.sql, where XXX is the version of Pharos installed (the main product version number, not the build number from the registry). Skip this step if you are upgrading from Pharos 4.70.
b. Open and run dbughead.sql, followed by all dbugXXXX.sql scripts in order.
c. Open and run dbugtail.sql.

6. Update the build number for the Pharos Database in the Installed Components registry key.

NOTE: The dbinst.sql script in the directory can create a fresh (current to the CD version) database. You can use this to create a reference pharos database to verify the upgrade. To verify the upgrade: connect to the reference database and load the script Validating Upgrader.sql. Replace 'upg_db' with the name of the database that has just been upgraded and replace 'ref_db' with the name of the reference database. Run the script and then check the results set for any differences between the two databases. Any differences reported by this script will indicate that the upgrade has failed. (Possible exception is name of uniqueness constraints on categories and permission_types tables)

Note: When upgrading a Pharos Uniprint Database for to 8.0 there is no automatic mechanism to upgrade a remotely hosted Pharos Database on a remote SQL Server.

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 authentication gateways. See the attached Pharos TechNote.

To apply default settings on a Popup printer deployed via a distribution package, first configure the desired settings on the printer object corresponding to the Spool Queue for which you will be generating packages. Then select "Yes" for Copy Printer Settings on the Device tab of the Spool Queues context in Pharos Administrator. When a distribution package creates a printer object for this queue on a client PC, it will attempt to give the new printer the same settings as the Spool Queue.

However, the Copy Printer Settings property does not work for all printer drivers, as the mechanism for applying printer settings varies. If default settings are not copied to the printer on client PCs, you will need to create a Custom Module to copy the settings:

  1. Create and configure Spool Queue in Pharos Administrator. Be sure to configure the Popup Printer Name on the Device tab.
  2. Generate the package for this Spool Queue from the Package Definitions context.
  3. Install the package on a client machine and configure it with the settings you want, e.g. default paper size, default color mode.
  4. On a client machine run the following command (replace PopupPrinterName with the name of the Popup printer you just installed - leave the quotes):

    RUNDLL32 PRINTUI.DLL,PrintUIEntry /Ss /n "PopupPrinterName" /a c:\printersettings.dat


  5. Create a batch file called SetPrinter.bat in the same directory as printersettngs.dat, which is C:\. In this batch file add the following command (replace PopupPrinterName with the name of the Popup printer you just installed - leave the quotes):

    RUNDLL32 PRINTUI.DLL,PrintUIEntry /Sr /n "PopupPrinterName" /a c:\Progra~1\pharos\temp\printersettings.dat


  6. Copy these files to a directory on your principal server.
  7. On your principal server, use WinRAR to create a zip file with these two files, giving the zip file the same name as the Popup printer to identify it. Once the zip file is created, open it with WinRAR. Make the zip file self-extracting by clicking the SFX button, configuring the following settings:
    1. In the advanced SFX options on the general tab set “Path To Extract” as C:\Progra~1\Pharos\temp\.
    2. On the General tab set “Run after extraction” as SetPrinter.bat.
    3. On the Modes tab check the “Hide all radio button” and the “Overwrite all files” radio button.
  8. Store the resulting exe file on the principal server in the directory C:\Program Files\Pharos\Bin\Shared\. Delete the original .dat, .bat and .zip files.
  9. In Pharos Administrator create a Custom Module with the same name as the Popup printer.
    1. For the Filename setting, browse for the exe file you just created and select that.
    2. For the Module Behavior property, make sure “Continue install if module fails” and “Module does not write results.txt file” are checked.
  10. Delete the package originally created and recreate it, but do not build the package yet. Add the newly created Custom Module to this package and build the package.
  11. Install the package on your client machines.

Note: In step 4 it may be required to use the PrinterData flag at the end of the command if there is some issue such as user profile information being copied as well. The flag is "d" at the end of the command, resulting in a command that looks like this:

RUNDLL32 PRINTUI.DLL,PrintUIEntry /Ss /n "PopupPrinterName" /a c:\printersettings.dat d

If you are still unable to apply default printer settings for the print driver you are using, you will need to contact the printer manufacturer for advice on how to apply default settings. This functionality has been tested in Windows 2000 and Windows XP. The functions are not available in Windows Vista.

For versions 8.2 and later, please run the Pharos Logsetter from Start > All Programs > Pharos > Pharos Log Setter

  • Log to DebugView: to add Logsetter communications to the Microsoft SysInternals DebugView software
  • Log to File: starts the Log Setter utility.
    • Log File Directory: Enter the full directory path of where the log files will be stored.  The default location is Pharos\Logs directory, which is typically found in “C:\Documents and Settings\All Users\Application Data".
    • Maximum Disk Space specifies the maximum size (in GB) for the total amount of disk space for the log files.  The Maximum Disk Space for Log Files setting controls the total size allocated for all the logs and backup files for the entire machine.  Each log file will continue to grow as information is logged.  When the log files reaches 256MB, all log files will be compressed.  When all files (current and compressed) reach the specified log size limit, the oldest compressed files will be deleted.
    • Include Communications Logging: When this option is checked, the log files will include a more detailed logging including network communication information (PSComm).
  • Roll over log files: Hitting his button encapsulates the current set of logs at that time into a zip file.  This is particularly useful when diagnosing a particular event or set of events where the behavior can be invoked so as to create a smaller zip file to send to Pharos Support.

Please note, Pharos services do not need to be restarted after the <Apply> button is hit on the Log Setter utility for 8.2 + to start logging.

Also, if you'd like to log components like the SignUp client, you may need to install the Logsetter manually.  You can do that from the Pharos installation media from the \tools\utils\LoggingServiceInstaller\LoggingServiceSetup.msi

 

For versions 8.1 and earlier, please follow the below directions

Running the Logsetter

You can run the Logsetter directly from the Pharos Installation CD (..\tools\utils\logsetter ) by doubleclicking the logsetter.exe file, or by coping the three files in this folder (logsetter.exe, config.ini and logset.chm) onto the local machine and running it from there.

Logging Pharos Components

Most Pharos components can be configured to write debug information to a log. This information can be useful when troubleshooting problems. Logs can be collected an sent to Pharos Support.

The Pharos Logsetter (available on the Pharos CD at ... tools\utils\logsetter) allows you to specify log settings for various Pharos components. Log information is stored in the registry under:

HKEY_LOCAL_MACHINE\SOFTWARE\PHAROS\ [Component Name] \Log

The Log Setter creates this key if it does not already exist, and sets the values under it.

Pharos Components that can be logged using the Logsetter

Logging can be activated from the Logsetter for the following Pharos services and applications:

Pharos Database Service
Pharos License Service
Pharos Print Service
Pharos LPD Service
Pharos Popup Service
Pharos SignUp Service
Pharos Distribution Service
Pharos EDI
Pharos Station
Pharos Notify

Setting up the Logsetter

Set the "Debug" level to 5
Check "Types" and select ALL checkboxes
Select the "Advanced" button
Check "Catagories" and select ALL options
Under "Options" select "Show Time," "Show Process ID," "Show Thread."

Starting the Log

Once the logsetter has been run you must restart the Pharos service set to be logged before the log file to be created. This can be done via Windows Service by restarting that specific service, or by rebooting the machine.

Logsetter Help

The Logsetter has its own Help - click the Help button on the main dialog for assistance in configuring application logs.

Note:  Unless otherwise directed by Pharos Support or Development run the Logsetter using the default settings. All that you need to do is to create a name and path for the log file.

NOTE: The EDI Server runs as part of Microsoft Internet Information Services (IIS). For security reasons, IIS runs under a special account that can read and write to only a small number of directories. (This is so that if the IIS server is compromised, the damage can be contained.) It is likely that this account does not have permission to write to the directory you specified. See Knowledge Base Article 1091 for configuration.

** Please see attached document with screen shots of how to configure the Logsetter with all options.

Active Directory LDAP Plug-in

The Pharos Active Directory LDAP Plug-in is a Logon Plug-in that interfaces with a Windows Active Directory system using the Lightweight Directory Access Protocol (LDAP). The plug-in checks all specified servers for a user's authentication details, returning success if the user is found on any server. (The servers and the order they are checked in are specified in the registry - see Configuration below.)

The Pharos Active Directory LDAP Plug-in is compatible with Pharos 5.0 and later.

Note: This plug-in is different from the Pharos LDAP Plug-in, which supports any authentication system that provides a standard LDAP interface, but which requires special configuration to support Active Directory. The Pharos LDAP Plug-in is available on the Pharos CD at \tools\plugins\LDAP. See the Pharos Online Help for more information.

To install the AD LDAP Plug-in, copy the adldaplogon.exe executable to the pharos\bin directory of all Pharos servers.

To configure Pharos to use the AD LDAP Plug-in:

  1. Open Pharos Administrator.
  2. Create a new Bank called "ADLDAP Bank" at Charging > Banks.
  3. Select the new ADLDAP Bank, and click the edit box at the end of the Plug-ins property.
  4. Select the Logon Plug-in event.
  5. Enter the path to the adldaplogon.exe executable and click the < button to set the AD LDAP Plug-in as the Bank's Logon Plug-in. Click OK.
  6. Set Print and/or SignUp Services to use this Bank at Printing > Print Services > General tab and/or SignUp > SignUp Globals > SignUp Services > General tab.
  7. Set any Pharos Stations you wish to authenticate against an LDAP interface to use this Bank at Pharos Stations > PC Pharos Stations > General tab.
  8. Click the Change Control button.
  9. If Pharos Remote is being used, set adldaplogon.exe as the Pharos Remote Bank's Logon Plug-in at Charging > Banks > General tab.

Note: If you are migrating to the AD LDAP Plug-in and wish to avoid affecting existing logon functionality, it is a good idea to set up a test Pharos Station first. Once configuration and testing has been completed on the test Pharos Station, all other Pharos Stations can be changed to use the AD LDAP Bank.

Before the AD LDAP Plug-in can be used, the registry must be edited to contain the configuration details that the plug-in needs to function. You can either edit the registry manually, or set it up from the command line (see below).

The plug-in requires a key called AdLdapLogon under HKEY_LOCAL_MACHINE\Software\Pharos\Plugins\, with a key underneath that called Servers. The Servers key must contain a string value for each server that the plug-in will search for users. The value name is the search priority, and must be a number (lower numbered servers are searched first). The value data contains five fields, separated by colons:

  1. Server name (or domain name)
  2. Username
  3. Password
  4. Port number
  5. SSL

The server name can be either a specific server, or the domain name. If using the domain name, use only the DC (DomainComponent), rather than the fully qualified domain name. However, if SSL is used, the name specified must match the server name as it appears on the server's SSL certificate, i.e. if the fully qualified domain name appears on the certificate, then the fully qualified domain name must be specified; if the server's IP address appears on the certificate, then the IP address must be specified, and so on.

The username and password must belong to a user that the plug-in can use to access the LDAP database; this only needs to be an ordinary user, with no special privileges. The SSL value must be 1 or 0, depending on whether or not SSL is used to encrypt communications (1 = use SSL, 0 = no SSL).

To make configuration easier, the plug-in accepts some command line options to automatically create/update the registry settings. Each option has a long form (e.g. add-server) and a short form (e.g. -a) - either one can be used.

 

Add a server:

adldaplogon --add-server <priority> <server> <user> <password> [<port>] [<ssl>]

adldaplogon -a <priority> <server> <user> <password> [<port>] [<ssl>]

 

Notes:

  • If an existing server has the same priority, it will be overwritten.
  • The port number is optional.
  • <ssl> must be either 1 (= use SSL) or 0 (= no SSL).
  • <ssl> is optional; if it is not specified, SSL will not be used. However, if it is specified, a port must be specified as well (636 is the default port for LDAP with SSL).
  • If SSL is used, <server> must match the server name as it appears on the server's SSL certificate, e.g. if the fully qualified domain name appears on the certificate, then the fully qualified domain name must be specified for <server>.

 

Delete all servers:

adldaplogon --clear-servers

adldaplogon -c

 

Delete a specific server:

adldaplogon --drop-server <server>

adldaplogon -d <server>

 

List all servers currently configured:

Test the plug-in against a user account before using it with Pharos. The user account must already exist in the Active Directory database. If you are using SSL, all relevant SSL certificates should be installed. To test the plug-in, run the following from the command line:

 

adldaplogon.exe [filename] [level] [username] [password]

 

Where:

  • [filename] is the full path of the file that results will be written to
  • [level] is the Pharos access level of the user being tested (this value is not actually used by the plug-in; however, entering "trace" for the level will cause information about the logon process to be output to the screen)
  • [username] is the logon ID of the user being tested
  • [password] is the password in the LDAP database for the user being tested

The results of the test will be written to the specified file. If the test is successful, "OK" will be written to the file. If the test fails, the file will contain "FAIL", and an error message explaining why the test failed.

Note: If trace information is enabled, it may contain error messages even if the test succeeds. This is because different Active Directory systems use different user attributes when doing an LDAP bind for the user. The AD LDAP Plug-in must therefore check all available attributes for the user account, some of which may fail before the bind is successful. As long as "Success!" appears at the end of the trace information, the bind was successful.

 

 

 

Pharos Client Installation Packages created on a 32-bit server OS can be created to include both 32 and 64 bit drivers. In order to do this you will first need to install the 64-bit driver onto the 32-bit operating system.

Once the drivers are installed Pharos can make use of both 32 and 64-bit drivers when creating client  installation packages.

NOTE: While this article specifically describes the addition of a 64-bit driver to a 32-bit Windows server for 64-bit client support, the process for adding a 32-bit driver to a 64-bit Windows server for 32-bit client support is the same. Further, if the client operating systems are a mixed bag of XP, Vista, and Windows 7, utilize the Windows 7 version of the driver, if available.

Provided your server runs at least Windows 2003 Server with Service Pack 2, installing 64-bit printers is a simple process. You must observe the following prerequisites, however:

  1. The 32- and 64-bit drivers must share the same Printer Description Language (PDL). For example, you must use a 64-bit PCL5e driver with a 32-bit PCL5e driver. You cannot mix-and-match PostScript 3 or PCL6 (PCL-XL) with PCL5e.
  2. The 32- and 64-bit drivers must be the same version number. This may require going to the manufacturer's web page and downloading new 32- and 64-bit drivers.
  3. The 32- and 64-bit drivers must have the same name. If the 32-bit driver installs as "Manufacturer Model PCL5e (x86)" and the 64-bit driver installs as "Manufacturer Model PCL5e (x64)" you will not be able to make this work. Contact the manufacturer for further support.
  4. The 64-bit driver must install using the INF file. If the driver can only be installed using SETUP.EXE or other "external to Windows' Add Printer wizard" method, you will not be able to make this work. Contact the manufacturer for further support.

Also, please note that this procedure only needs to be performed once for each printer driver installed on the print server. Any other queues that use the same driver will automatically attach the 64-bit driver.

Once this has been verified, proceed with the following steps. For a visual explanation, you may also review the movie (AVI format) found at the link below.

  1. Verify that the 32-bit printer driver and queue are current and configured for sharing.
  2. Go into Properties for the queue.
  3. Click the Sharing tab.
  4. Click the "Additional Drivers" button.
  5. Check the box next to "x64" and click the "OK" button.
  6. Use the "Browse" button in the resulting Windows dialog box to go to the location where the 64-bit driver was extracted.
  7. Select the INF file and click the "Open" button.
  8. Click "OK" to accept the file location. The files will begin to add to the server.
  9. When the file installation is complete, you will be returned to the Properties page for the printer. If you wish to verify the addition, click the "Additional Drivers" button. You will see a check mark next to both the x64 and x86 options.
  10. Click "Close" to exit Properties.

Now, build or re-build the Pharos Installation Package normally and both 32/64-bit options will be available.

As the Pharos Popup Client is installed, each Mac OS X client machine that is to have the Popup Client must be visited individually. A printer queue must also be set up on each client machine for Popup to use. In a large organization, this can become time-consuming. It is possible, however, to automate the installation of the Popup Client by modifying the Popup Client installer.

 

See the attached Pharos TechNote, TechNotePUPIMac.pdf.

 

This 8.1 package can be used in all versions of Uniprint, including version numbers higher than 8.1.

 

Attached, also, is a sample package that installs two Pharos-controlled print queues configured against a non-existent server.

Do not install the provided package "as is." Rather, use it as a guide in developing your own package(s).


NOTE: The instructions for modifying the 8.3 client installer can be found here: Can I modify the Pharos for Mac Popup client to also install printer queues on the client workstations?

Manual Install of the Pharos Database

 

Installation Overview

 

1. Obtain the database install files
2. Create a Database and Database Login in SQL Server
3. Manually install the Pharos Database
4. Install the other Principal Server components
5. Prepare the services and database
a. Alter the Pharos registry entries
b. Set the Pharos services to start manually
c. Manually configure the Pharos Database
6. Configure Microsoft Server to control the Pharos services
7. Test the configuration
8. Install other Pharos services (optional)

 

Each procedure is detailed below.

 

1. Obtain the database install files

 

A number of files are required for a manual installation of the Pharos Database:

 

• dbinst.sql and p3static.sql – these files are located on the Pharos CD in the database\db directory.
• icons.dat and either bcp7.fmt (for SQL Server 7) or bcp2000.fmt (for SQL Server 2000) – (attached)
• DatabaseRegistryShell.reg – (attached)
• Your license information file – this is the text file supplied with your Pharos license.

 

Copy these files to the Server.

 

2. Create a Database and Database Login in SQL Server

 

To create a database, follow these steps using SQL Server Enterprise Manager:

 

1. Expand a server group, then expand the server.
2. Right-click Databases, then click New Database.
3. On the General tab, enter a name for the new database. This will usually be “pharos”. The default settings on the Data Files tab and Transaction Log tab are correct for a Pharos installation.
4. Click OK to create the new database.

 

**********************************************************************************************************************************************************************************
To add a login for the database, follow these steps using SQL Server Query Analyzer:

 

1. Start SQL Server Query Analyzer.
2. Log on as the 'sa' database user and make sure that the connection is against the master database.
3. Enter the following query into the query window:

 

Where:

 

use master
exec sp_addlogin @loginame = '<loginame>', @passwd = '<pwd>'
go
use <dbname>
exec sp_changedbowner @loginame = '<loginame>'
go
exec sp_defaultdb @loginame = '<loginame>', @defdb = '<dbname>'
go

 

• <dbname> is the name of the database you just created.
• <loginame> and <pwd> are the new login name and password for the database.

 

4. Execute the query.

 

**********************************************************************************************************************************************************************************

 

Before Continuing you need to check the collation SQL setting

 

SQL 2005

 

Run the Query below
select name, collation_name, compatibility_level from sys.databases
select serverproperty('Collation')

 

MSDE / SQL 2000

 

In the command window run the following command:

 

osql -Slocalhost -Usa -P<insert sa password here> -Q"select collation from syscolumns where name = 'name' and id = 1"

 

Query

 

select collation from syscolumns where name = 'name' and id = 1

 

Write down the name of the collation and when you create the Pharos database you need to make sure it has the same collation setting is the same

 

**********************************************************************************************************************************************************************************

 

3. Manually install the Pharos Database

 

1. Start SQL Server Query Analyzer.
2. Log on as the Pharos Database user, using the user name and password you created previously. (If SQL Query Analyzer is still open, select Connect from the File menu to log on with the new details.)
3. Ensure that the Pharos Database is selected as the current database.
4. Open the file dbinst.sql (File menu > Open) and execute it. This file can be found under the \database\db folder on your Pharos CD. This may take a moment to run. Make sure there are no errors (“Query batch completed” should appear in the status bar at the bottom of the window).
5. Insert the Pharos Icons into the database using the bcp command line utility and the icons.dat file provided: Execute the following command from the directory into which you saved the icons.dat and *.fmt file: Where:

 

bcp pharos..icons in icons.dat –S<servername> -U<loginame> -P<pwd> -f<bcpfile> –E

 

• <servername> is the name of the server SQL Server is installed on.
• <loginame> and <pwd> are the login name and password you created earlier.
• <bcpfile> is the name of the file you are using (either bcp7.fmt or bcp2000.fmt).

 

In addition, when installing on SQL Server 2000, check that the collation order in the bcp2000.fmt file (Latin1_General_Cl_AS) is the same as the default collation order for your SQL Server. Check this by looking at the Server Properties of the SQL Server instance using SQL Enterprise Manager.
6. Open and execute the file p3static.sql in SQL Server Query Analyzer.
7. Update the system table in the database with your license details. To do this, execute the following query in SQL Query Analyzer: Replace <sitename> with your site name and <clientcode> with your client code. This information can be found in your license information file (the text file supplied with your Pharos license key). The first two lines of this file contain your site name (after “Licensed to =”) and client code (after “Client code =”). Once the modifications are made, execute the query.

 

update system set licenced_to = '<sitename>', license_quick_key = '<clientcode>'

 

The Pharos Database is now installed.

 

4. Install the other Principal Server components

 

The servers can be installed with the standard setup program on the Pharos CD, but the registry on each node must be modified first so that the Pharos installers are aware that the database has been installed, and can access the name of the Server where database has just been installed.

 

To modify the registry, perform the following steps on each node:

 

1. Copy the registry file DatabaseRegistryShell.reg onto the node.
2. Open this file with a text editor, e.g. Notepad.
3. Make sure that the “Database Name”, “Password” and “User Name” values are the same as the values you created in step 2 above.
4. Replace the value of “Server Name” with the name of the virtual server running SQL Server.
5. Make sure that the “Path” value contains the directory where Pharos components will be installed, and that the “Pharos Database” value contains the build number of your release of Pharos (you can see the build number on the title bar of the first dialog that appears when you run Setup.exe on the Pharos CD).
6. Close the text editor and execute the registry file by double-clicking on it.

 

You can now run the Pharos setup program to install the Principal Server. Choose ‘Principal Server’ on the Select Role screen, then select all components on the Select Components screen (the Pharos Database should not be available for installation). When prompted for the SQL Server Machine Name, type in the name of the server running SQL Server. The installation of the services should proceed normally, with one exception: the second time you install the Distribution Service, an error message will appear, due to the fact that the installers attempt to insert an entry for a second Distribution Service into the Pharos Database, when there can only ever be one. This error message can be safely ignored.

After installing the Mac components you receive the following error message:

Failed to contact the Popup Server

The print job has been aborted because Pharos Popup failed to contact the Popup Server.
If this problem persists, please notify your system administrator.


See attached screen shot.

This error will appear if any of the following issues are present.

Mac Firewall Enabled

If the client workstation firewall is enabled you must disable it or add a port exception. The port used is 28203.

Spaces in the Spool Queue Name

If the Pharos Spool Queue Name has a space in it e.g. "BW Queue" when entering this into the popop:// URI you will need to escape the spaces for the popup to function. "BW Queue" would become "BW%20Queue"

Network Issue

The Mac is not capable of connecting to the server by name. To confirm this you should ping the server via a terminal window on the Mac client and confirm you can ping the server by name. If not you can use the IP address of the server in the popup:// URI. This workaround will function correctly with 7.0 and above. Pharos 6.1 requires the complete server name to function.

Incorrect Queue Name

If the Spool Queue name has changed and/or a change control has not been completed you will receive the error. Check the Pharos Administrator --> System --> Alerts for messages from Mac clients. To resolve this create a new printer on the Mac with the correct Spool Queue Name or rename the Spool Queue on the server to match the client and perform a change control.

How to locate the Uniprint version and Site Code

Uniprint version 8.x

   1. Open Pharos Administrator.
   2. On the Left hand side of the MMC (Microsoft management Console) expand the System Tree.
   3. Select License Limits.
   4. Expand the middle section of License Summary for your Site Code and License Expiry Date.
          (See attached screen shot "Administrator-License2.PNG")

   Product Version

   1. Open Pharos Administrator.
   2. From the Help menu choose "About Pharos Administrator" to view installed Product Version.


   Uniprint version 6.0 - 7.x

   1. Open Pharos Administrator.
   2. From the Help menu choose "About Pharos Administrator".
   3. The installed products and their version numbers are displayed.

   Site Code

   1. Open Pharos Administrator.
   2. From the Help menu choose "Site License" to view the Site Code.


Note: If the Pharos Help menu does not display the Pharos version and Site Code information (pre-version 6.0), follow the steps below:

   Uniprint version

   1. Open SQL Server Query Analyzer.
   2. Select the Pharos Database.
   3. Run the following query.

     select * from system

In the displayed results of the SQL Query, look in the table for columns called "version_major, version_minor and build_number." These three columns combined are the Pharos version.

For instance, if you see:

version_major of 5
version_minor of 2
build_number of 1950

then the Uniprint version is 5.2.1950

   Site Code

   1. Open SQL Servers Query Analyzer.
   2. Select the Pharos Database.
   3. Run the following query.

     select * from system

In the displayed results of the SQL Query, look in the table for the column called "License_quick_key." This is the Site Code.

Pharos Omega 1.5.5 Revision 6399 (Queens Cliff U5)

What's New in this Release

  1. Switching between copying and printing during a session

    Where both printing and copying services are available, logged on users can now switch between the two in a single session without having to log off and log back on. The new Do Copies button on the printing screen and Release Prints button on the copying screen allow users to switch between the printing and copying screens.

    Switching between services is enabled by selecting "Yes" for the Allow User to Change Station Function property on the Session tab of the Network Terminals context in Pharos Administrator.

  2. Offline copying

    If the connection to the Pharos EDI is lost, users can perform copying through the SmartPAD as normal. While in offline mode, the SmartPAD will accept any logon details, and the user balance field on the copying screen displays "Balance $0.00 (offline)" to indicate that they are in offline mode. Once communications resume, details of all offline copy transactions are forwarded to the Pharos Database.

    Three new properties on the Copier tab of the Network Terminals context control offline copying:

    • Allow Offline Copying - enables or disable the offline copying feature
    • Disable Third Party Charging when Offline - determines whether or not users can charge to Cost Centers while offline
    • Default Offline User - specifies a generic User account to record copying against in cases where an offline user supplies unknown logon details
  3. Support for USB card readers

    An external card reader can be plugged into one of the USB ports on the SmartHub and used instead of the SmartPAD's built-in card swipe. Omega supports Human Interface Device (HID) keyboard emulation USB card readers.

  4. Masking logon IDs

    The new Mask Logon Entry property (available in Pharos Administrator at Pharos Stations > Network Terminals > Logon tab) allows the entry of users' logon IDs to be masked with asterisks in the same way that passwords are. This may be useful if passwords are not used, and logon IDs are sensitive.

  5. Per user copy costing

    The new Get Costings Per User property (available in Pharos Administrator at Pharos Stations > Network Terminals > Copier tab) allows copy costs to be loaded from the EDI every time a user starts a copy session. This allows for discount costing on a per user basis.

  6. Changing passwords in Omega Administrator

    It is now possible to change the administrative password (used when logging on to the configuration menu at the SmartPAD) across multiple devices using Omega Administrator. Highlight the desired Omega device(s) and select Push > Omega Logon Password.

  7. Print job sorting

    Print jobs can now be sorted on the printing screen. Pressing any of the column headers (Document Name, Owner or Date & Time) sorts all print jobs by that property.

  8. Changes to logging options

    Options to enable Omega logging are now located on the new Syslog screen on the configuration menu at the SmartPAD. Options determining what information is logged are still configured at Admin > Logging.

  9. Extending timeout on copying screen

    Pressing any of the More > or Change buttons on the copying screen resets the Job Timeout.

  10. New wait icon

    The SmartPAD displays a small rotating icon while it is processing actions like validating a logon or listing print jobs, where previously status messages were displayed in a small window. The new Popup Status Messages (located under Logging in the configuration menu at the SmartPAD) controls whether the icon or the status messages are displayed.

  11. Print and Copy buttons now themeable

    The appearance of the Print and Copy buttons on the main SmartPAD menu can now be altered as part of a theme.

  12. Changes to Screen Suspend functionality

    Outside of the available hours defined by their Access Time schedules, Omega SmartPADs automatically enter screen suspend mode as soon as the Screensaver Time expires. SmartPADs automatically come out of screen suspend mode at the start of the available hours.

    The maximum value for the Screen Suspend Time property has been increased to 12 hours (up from 1 hour in previous versions).

  13. Changes to card swipe processing Introduced in Queens Cliff update 1

    Omega now treats all control characters in serial proximity card swipes that are less than 20Hex (i.e. <CR>, <LF> etc.) as end of card swipe characters and strips them. This allows Omega to support Impro prox reader OMS-900-1-0-FG-XX Omni Scan 125kHz passive tag readers.

    Omega also now treats ';E?' as a bad card swipe (this string is returned from known mag strip card readers and the SmartPAD internal card reader).

  14. Bug fixes

    This release includes the following bug fixes:

    Fixed in Queens Cliff update 2:

    • Fixes a bug where, in a certain configuration, users could swipe their card and log on outside Access Times.
    • Omega now copes with the syslog IP being set to an invalid address without hanging for several minutes.
    • Fixes a bug where SmartNode upgrade failures were not being logged.
    • SmartNode upgrades will re-try after a failure.

    Fixed in Queens Cliff update 4:

    • The Omega.exe utility was broken in Queens Cliff update 3. It now functions correctly.
    • Fixes bugs relating to broken pipe errors when using SSL: Errors recover gracefully, and the possibility of an error putting Omega into offline mode (allowing users to perform copying for free) has been removed.
    • Fixes a bug in the Learn Copier function, where the "Detect copier disable" test would not complete in certain circumstances.

    Fixed in Queens Cliff update 5:

    • If a Billing plug-in is used and it fails a getUserDetails call, the user account in question would be locked and unable to log on at Omega terminals. This no longer occurs.
    • Fixes a bug where, if the connection timeout to the EDI Server was set to a small time, a communication failure would result in all subsequent communication attempts failing.
  15. Learn Copier function supports Pharos 7.1 Introduced in Queens Cliff update 3

    Prior to this release, the Learn Copier function could not be used with Pharos 7.1. (This function, available on the Station > Copier screen at the SmartPAD, allows you to automatically determine configuration values for a copier and send them to the Pharos Database.) The Learn Copier function now supports Pharos 6.1 - 7.1.

  16. Learn Copier function support for paper sizes Introduced in Queens Cliff update 4

    Prior to this release, the Learn Copier function did not work with Pharos 7.1 when using Letter paper size with Color, nor for any paper size whose names started with letters greater than "Color". The Learn Copier function now works correctly for all paper sizes with Pharos 7.1.

  17. Support for new Magtek card reader Introduced in Queens Cliff update 5

    Omega now supports a new variant of the Magtek swipe card reader built in to the SmartPAD. The new variant is the MagTek P/N 21047008 Rev - C.

Known Issues

  1. Pharos 6.0 Change Control not actioned immediately

    When using Omega terminals with Pharos 6.0, any change to the Pharos system that requires a Change Control will not be implemented at Omega terminals straight away. Instead, configuration changes are actioned when the Omega SmartPAD's screensaver is activated. On high use terminals, this may mean that changes are not actioned until the end of the day.

  2. Downgrading from post-Kingston firmware

    If Omega firmware is downgraded from a version later than 1.2.4 (Kingston) to 1.2.4 or earlier, the device will be left in an inoperable state. In this case, contact Pharos Support for assistance in restoring the device.

  3. 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.

  4. Offline jobs recorded with time of forwarding

    When using Omega with Pharos 7.0, offline copy jobs are recorded with the time that they were forwarded to the Pharos Database, rather than the time that the copy was actually made. A Pharos Alert (code 29054) is logged for each offline transaction - this Alert will contain the actual copy time.

  5. 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.

Install Notes

  1. Apply ini_schemas.sql script

    Run the ini_schemas.sql script supplied in the Database directory of this firmware release against the Pharos Database before upgrading firmware. This ensures that all new properties featured in this firmware release will be available in Pharos Administrator. If you are using SQL Server, run this script against the 'pharos' database using SQL Query Analyzer. If your site uses MSDE, run the script by entering the following from a command prompt, where [password] is your SQL administrator password:

    osql -U sa -P [password] -d pharos -i ini_schemas.sql

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

  2. Omega requires SQL Server 2000

    While Pharos 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.

  3. Custom themes no longer supplied by Pharos

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

    Note: The new theme format is no longer 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. Omega Administrator no longer displays the Theme Version property, as this is no longer relevant. Themes in the old .th format (pre-Pencarrow) will not work with Pencarrow and above firmware, however.

How to Submit a Support Request

You have a number of options:


The remainder of this document describes the information that we need from you when you submit a support request. Pharos Technical Support wants nothing more than to resolve your issue quickly and to your complete satisfaction. The more information you supply at the outset, the better our ability to do that.


Contact Information

Please provide the following information so that it's as easy as possible for us to get in touch with you:

  • Your full name
  • Name of your organization
  • Your e-mail address
  • Your phone number


Problem Description

Describe the problem you are experiencing in as much detail as possible. If possible give a step-by-step example of what happened.

  • When did the problem start (date and time)?
  • How often does it occur?
  • Where does the problem occur (Pharos components, physical locations)?
  • Before the problem occurred, were any changes made to:
    • Pharos components (configuration, hot fixes, additions)
    • Operating systems (service packs, etc.)
    • Hardware (computers, printers, etc.)
    • Network (domain changes, firewalls, routers, etc.)
  • Hardware-Specific Information:
    • Type of component involved
    • Fault description
    • If Omega PS terminal, provide serial number


Gathering information about related errors

Look in the following locations for any errors related to the problem you are experiencing:

 

 


Site Information

Here is a list of additional information that would be very helpful to us:

  • Your Site Code (see below for help in finding this information)
  • Pharos software installed (Uniprint, Signup, Off-the-Glass, Blueprint Enterprise)
  • Pharos software version
  • Pharos Server operating systems
  • Client operating systems
  • SQL Server version
  • Other relevant components (e.g. Pharos Scripts, Gateways)


Site Code and Version Information

This article gives instructions for updating your Pharos Uniprint license key. For versions 8.0 and above and prior to 5.3, the procedure is quite straightforward. However, for versions 5.3 to 7.2 inclusive, a License Upgrader Hot Fix needs to be applied.

 

Applying a license key to a Uniprint 8.x, or higher, system

If you are currently running Uniprint 8.x (or higher) and have received a new license key, the steps for installing the key would be:

  1. Stop all Pharos services including remote Pharos Print server services
    1. click Start --> Run
    2. type services.msc and hit Enter
    3. Find the Pharos License Server Service, right click, and select Stop
    4. A confirmation window will appear confirming you'd like to stop all other dependent services; click Yes
  2. Apply the license registry key to the Principal server by double clicking the License Registry (.reg) file
  3. Start all Pharos services up again on all servers
  4. Verify license limits and exipry date
    • Pharos Administrator - System - License Limits on the left-hand side context tree.

 

 

Applying a license key to a Uniprint 5.3 - 7.2 system

Note: If you are installing Uniprint 7.2 for the first time, install the Principal Server, run the Pharos License Upgrader Hot Fix as per the instructions below, and only then install other Pharos components.

Note: If you have previously applied this License Server update you will not need to re-apply it. Simply follow the steps above under Uniprint 8.x to apply the license registry file.

  1. Save the sitecode.rename_to_zip file you received from Pharos Licensing and change the filename to end in .zip.
  2. Download the two files attached to this article:
    • Pharos License Upgrader (PharosLicenseUpgrader.exe)
    • WindowsInstaller-KB893803-v2-x86.exe (Microsoft Windows Installer)
  3. Place all files to the same file location on the License Server PC (e.g. c:\temp)
    • Pharos License Upgrader (PharosLicenseUpgrader.exe)
    • WindowsInstaller-KB893803-v2-x86.exe (Microsoft Windows Installer)
    • Pharos License Key (sitecode.reg, sitecode.txt)
  4. Run the WindowsInstaller-KB893803-v2-x86.exe (Windows Installer) file
  5. Reboot the computer
  6. Run the PharosLicenseUpgrader.exe executable

Note: This applies the new license information to the registry, and applies the Hot Fix if a Uniprint version between 5.3 and 7.2 is detected.

 

Applying a license key to a Uniprint pre-5.3 system

As above for version 8.x. There is no need to apply the License Server upgrade.

Once the Hot Fix is correctly applied, the version number of the License Server executable will be updated to 7.2.4281

 

Manual installation of Hot Fix in the event the License Key was applied prior to this fix, or the fix fails

To install the License Server update manually:

  1. Download the attached lserver.zip package
  2. Extract the three files contained in the zip to the desktop
  3. Run the WindowsInstaller-KB893803-v2-x86.exe (Windows Installer 3.1)
  4. Run the vcredist_x86.exe installer
  5. Stop all Pharos Services
  6. Replace the lserver.exe located in C:\program files\pharos\bin with the one extract
  7. Restart all Pharos Services

Once the Hot Fix is applied, the version number of the License Server executable will be updated to 7.2.4281.

The application of this Hot Fix constitutes acceptance of the conditions specified in your license agreement. To view the license agreement, please refer to the file 'license.rtf' on your Pharos CD.

The theory behind having the files locally and on the network are the same. We need to designate the locations where we want the files to be stored in the registry (albeit in the network location scenario all machines must have a separate folder configured only for them).

This registry key is located at:

HKEY_LOCAL_MACHINE\Software\Pharos\SignUp Client\ConfigFileDir

The key for network however is security. As we have to retrieve the file from the network before any authentication is possible, we need to allow that machine to provide access to null session shares.

Below is a link to Microsoft's Knowledge Base article 289655 on how to enable null session shares below:

http://support.microsoft.com/default.aspx?scid=kb;en-us;289655

Once again, enabling null session shares is a security risk and so we highly recommend that you do this only one a machine which you will not mind if security is compromised.

It's a deprecated command. Microsoft removed the "truncate_only" option from SQL Server.

Microsoft recommends changing the recovery model to SIMPLE instead of using "no_log" or "truncate_only."

Attached to this KB Article are 2 SQL Queries. These will create 2 backup jobs, one for the Database and one for the Transaction Log file. These two backup jobs will be run at 1am each evening every day.

Run each query against the master database. This will create the backup jobs. You will need to insure that the SQL Agent is running for these scheduled jobs to run.

 

Note: These scripts will perform a NOINIT when backing up which translates to "Append to the existing backup set".

Note: If these procedures do not meet your organizations needs then you can create on your own a backup job using SQL Management Studio that better suits your needs. These are merely work arounds until this is corrected.

Check the attached Sequence.log and screen shot to verify the error. This is a known issue in Blueprint 4.2. Below follows two workarounds. Blueprint 5.0 and later accommodate the Spanish language name of the Spooler service in the installation code.

Workaround #1. Rename the Spooler service.

1. Launch Windows Registry Editor (regedit.exe) as an Administrator.
2. Open HKEY_Local_Machine > SYSTEM > CurrentControlSet > Services.
3. Locate Spooler and select it.
4. Double-click the "DisplayName" value to open/edit it.
5. Change "Cola de impresion" to "Print Spooler" (no quotes).
6. Click "OK" to accept and close out of Registry Editor.
7. Reboot the server to apply the change.
8. Install the Blueprint 4.2 server software.

Workaround #2. Install and use the English language pack. Use this workaround if Workaround #1, above, does not resolve the issue. Windows 2003 Server does not have a downloadable Language Pack, only Service Packs for the Language Pack. The core Language Pack must be purchased from a Microsoft reseller.

1.Install the Microsoft English Language pack. Windows Server 2008 R2 Multilingual User Interface Language Packs
2.Create a local user account on the PC and make member of the Admin on PC.
3.Log in as the new user.
4.Go to Regional and Language options -> Keyboards and Languages tab
5.Select English (Ingles) from list. Click Apply.  Agree to logout.
6.Log in again (as the new user)
7.Go to Regional and Language options -> Administrative tab.
8.Click on the “Copy Settings” button
9.Check the “Welcome screen and system accounts” check box.  Click OK
10.Click “Restart Now”
11.Login with new account, and do install.
12.Logout, and log in with normal account, UI will be in Spanish.  (Don’t need to use the new user again.)

The latest XP_Encrypt dll's are attached. One for 32 bit and one for 64 bit OSs.

Re-Designed Secure Release Here

  • Increased performance: 4x previous versions
  • Easier deployment
    • SQL Server not required for Collector
    • FTP service not required

  • Simplified configuration
    • Reduced number of Secure Release Here concepts
    • Easy to create terminal (e.g. device not required)
    • Queues are secured real-time on the print server
    • Print jobs are sent from the print server controliing the target device
    • Terminals can manage their own schema version

  • Enhanced robustness and availability
    • Workstation Release: the new Workstation Release user interface is installed with the Workstation Tracker. By default, it allows users to delete their secure jobs from their workstation. When Workstation Release is enabled (e.g. the authentication system is having issues), users can also release their secure jobs from their workstation.
    • New event logging system

Changes to Policy Print

  • True application-based trigger condition: allows you to create rules within your print policies that are based on the application that submitted the print job (e.g., outlook.exe).
  • User interface now uses Silverlight version 3
  • Report group name changed from “Policy Print” to “Secure Release Here & Policy Print”

This error suggests that the device has the wrong EDI password.

Configure the device with the correct password to connect to the EDI Server. This password is specified when the EDI Server is first installed.

Note: In some cases, upgrading the firmware may inadvertently erase the password.

Connection to the EDI Server:

Port 80
Port 443

Connection to Syslog Application:

Port 514

Connection to the Omega Administrator:

Port 21/tcp open ftp
Port 23/tcp open telnet

The MEAP Contents of the engine firmware is critical to proper application operation. Note that this is different from the controller version (although the two numbers are formatted in a similar manner). The MEAP Contents consists of a pair of two digit numbers separated by a dot (for example 34.01).

 

To determine the MEAP Contents of a device:

  • On the front panel press Counter Check.
  • Press the MEAP Counter button.
  • Press the Version Information button.
  • Record the MEAP Contents value.

To determine the Controller version:

  • On the front panel press Counter Check.
  • Press device configuration button
  • Record the controller version.

Note: MEAP Contents are not available using these instructions on Canon imageRunner Advance C2020/C2030 MFPs.

Related: iMFP for Canon - Supported Devices and Firmware


Pharos 8.1

 

Supported:

 

SQL Server 2000, SQL Server 2005, SQL 2005 Express Edition (SQL Express), SQL Server 2008 (Express Edition or better) with the latest Service Packs applied.

 

Not Supported:

 

SQL Server 7.0, MSDE and MSDE 2000.

 

Notes:

 

When installing SQL, be sure to install the TCP/IP network option, because Uniprint sets this as the default connection to SQL.

 

On SQL 2005 Express, TCP/IP must be manually enabled before installing Uniprint. Enable TCP/IP from the SQL Server Surface Area Configuration tool.

 

For SQL 2000 users, Uniprint supports only SQL Server 2000 Standard with Service Pack 4. While other editions of SQL 2000 (Personal, Desktop Engine, Enterprise and Developer) may be possible platforms, Pharos Systems has not tested them.

 


Pharos 8.0

 

Supported:

 

SQL Server 2000, SQL Server 2005 and SQL 2005 Express Edition (SQL Express) with the latest Service Packs applied.

 

Not Supported:

 

SQL Server 7.0, MSDE and MSDE 2000.

 

Notes:

 

When installing SQL, be sure to install the TCP/IP network option, because Pharos sets this as the default connection to SQL.

 

On SQL 2005 Express, TCP/IP must be manually enabled before installing Pharos. Enable TCP/IP from the SQL Server Surface Area Configuration tool.

 

For SQL 2000 users, Pharos supports only SQL Server 2000 Standard with Service Pack 4. While other editions of SQL 2000 (Personal, Desktop Engine, Enterprise and Developer) may be possible platforms, Pharos Systems has not tested them.

 


Pharos 7.2

 

Supported:

 

SQL Server 7.0, MSDE 2000, SQL Server 2000, SQL Server 2005 and SQL 2005 Express Edition (SQL Express) with the latest Service Packs applied.

 

Not Supported:

 

MSDE


Debugview is an application for capturing Debug output from code to a live real-time window. You can find a wealth of information just using the standard World Wide Web search engines to find further information, and the application can be downloaded from Microsoft.

Debugview is currently a popular debug output capturing tool used by Pharos Support. It can capture the logging information for many of our products if not all of them. this additional debug information is very useful in helping to analyze a challenge you may be experiencing with your Pharos Solution.

We have attached a simple document to this article that should provide some basic information on it's use. Please use Microsoft or the internet to find additional technical specification on the application.

 

If you have any additional questions please contact support@pharos.com.

The ports Omega uses in version 2.1.0 and later are:

8022 for SSH
8080 for HTTP
8443 for HTTPS
59000 for VNC (remote control application in Omega Administrator)

In "firewall" mode, the above ports are captured by the Omega while all the other ports are redirected to the PRINT Ethernet port (USB-Eth adapter).

In "hub" mode the omega also exposes:

6000 - X11 server
30450 - picogui server

These ports are the internal servers used by the station application on the Omega and do not need to be accessed by other network clients.

Cause:

If the Pharos Server was built on a Non-English OS, and then changed to English US, this will occur.

The reason is that Services running on the server will use the Local System Account to run by default. This includes Pharos. As such, they are still using the Non-English settings. This is occurs due to the way that Microsoft Windows works, and can not be changed once built this way.

Solution:

  • Create an Administrator account on the Pharos Server.(a local Administrator account may be ok, but the Domain Account is a better choice)
  • Log on to the server as a Domain Administrator - to ensure FULL rights and control. 
  • Set all conditions to English US - including currency and the number of decimal places, etc. to standard.
  • Set all Pharos Services to run under this account (Logon) along with a proper password in the service properties. Again , Do this for ALL Pharos Services.
  • Stop and restart the Pharos Services and test.

Pharos MUST run in this manner once a system has been built on an OS other than English US.

Upgrading Secure Release Here

Special upgrade steps are performed when upgrading previous versions of Secure Release Here (Blueprint Enterprise 3.5 SP1/R2, 4.1) to Blueprint Enterprise 4.2. The Secure Release Here queues and configuration are upgraded by the Blueprint Server Configuration Tool after the main server upgrade has completed.

As always, the Analyst should be upgraded before attempting to upgrade any Collectors if present. A special upgrade data file is generated during the Analyst upgrade which is needed during the Collector upgrades.

The sections below document what happens when the Apply button is clicked on the Blueprint Server Configuration Tool that runs immediately after the completion of the main server upgrade.

Analyst

An upgrade data file is produced which contains information required to upgrade the secure queues on every server being used for Secure Release Here. This file is in CSV format and is a simple mapping between the names of the secure print queues on each server and the print group to assign to each queue (in Blueprint Enterprise 4.2 a secure print queue must be associated with a single print group).

The following rules are applied during the Analyst upgrade for all queues on all servers:

  • Virtual queues retain the print group they had prior to the upgrade.
  • Non-virtual secure queues are assigned the print group that their connected device belongs to. If the device belongs to multiple print groups, then the group with the most devices is chosen. In this case the user is informed that they should review the configuration changes applied.
  • If no print group can be determined then a new one is created and assigned.

The Blueprint Server Configuration Tool will show a message box explaining what actions have been taken and where the upgrade data file can be found. The upgrade data file is called SecureReleaseUpgradeData.csv and is created in the Blueprint application data directory PharosSystems\Blueprint\SecureRelease.

  1. Please review the upgrade data file to ensure the contents are as expected:
  2. Check that there are entries for each server that hosts secure queues.
  3. Check that all secure queues are listed.
  4. Check that each secure queue has the expected print group assigned.
  5. Review any assignment which is marked as ‘true’ in the RequiresReview column.These indicate that a choice had to be made between multiple print groups, and that the print group with the most devices in it was chosen.

The contents of the file can be altered as needed prior to Collector servers being upgraded. In most cases this should not be necessary.

Collector

The upgrade data file produced at the Analyst is required at the Collector for Secure Release Here to be upgraded successfully. There are two ways in which this file can be provided:

  1. By placing it in the application data directory PharosSystems\Blueprint\SecureRelease prior to clicking the Apply button on the Blueprint Server Configuration Tool.
  2. The Blueprint Server Configuration Tool will prompt to browse for the file which can be stored anywhere, such as a network share, a USB stick, etc.

The Blueprint Server Configuration Tool will then upgrade all secure queues and stored jobs on the Collector. A message box explaining what actions have been taken will be shown at the conclusion of the upgrade.

Secure Queue Upgrade

The Blueprint Secure Queue Configuration Tool should be run to inspect the changes that have been made to the secure queues. This tool can also be used to change a secure queue’s assigned print group, or secure new queues.

It is not mandatory to perform the Secure Release Here upgrade at the Collectors immediately after the main Collector upgrade. The Secure Release Here upgrade can be canceled and resumed at a later date by re-running the Blueprint Secure Queue Configuration Tool. However, the Collector will not be working for the purposes of Secure Release Here until this procedure is complete.

Detailed logs for the Secure Release Here upgrade can be found in the application data directory PharosSystems\Blueprint\Logs, in the ServerConfig.log file.

This error occurs on the iMFP and is a result of only a portion of the card swipe being sent through to the online system (e.g. Blackboard, CBORD, Diebold etc..)

 

If the iMFP units were previously working then it may be a bad card reader and you should look at replacing it or swapping it with another working unit.

 

If this error occurs on setup then the likely cause is that the card data contains a special character such as a "=" or ' sign in it. To resolve this and pass all the card data. To do this

 

1. Open the Pharos Administrator
2. Select the Pharos Stations --- Terminals --- Terminal Name
3. Select the advanced tab and change the "Ignore Sentinels When Parsing Tracks" = No
4. Change control and retest

 

If you continue to recieve this error then you may also need to add an additional card type in the online Gateway configuration.

In recent versions of Uniprint, print jobs are divided into sections based on page attributes.  For example, a 6 page duplex job with three mono pages and three color pages will have two sections:

  • 3 pages, Color, Duplex
  • 3 pages, Mono, Duplex

In order to match physical expectations, if a duplex job has an odd number of pages, the last page is charged as a simplex page.  Due to prior limitations, a job with multiple sections would have each section processed individually.  This meant the last page of any section with an odd page total was charged as simplex.  As a result, the above example was actually charged as 2 mono duplex pages, plus 1 mono simplex page, plus 2 color duplex pages, plus 1 color simplex page.  When a job like this printed out on only three sheets, the charges could be difficult to explain.

This issue was addressed in Uniprint 8.2 by making the Page Counter responsible for indicating when a final page should be charged as simplex.  This now only applies to the final page of a job, rather than each section.

This change has been included as of revision 103.  However, the Page Counter adjusts its behaviour depending on which product version you are using, and the default 8.1 behaviour is not appropriate for these changes.  Therefore, applying one of these fixes means you must install a recent version of the Page Counter (any page counter more recent than the version bundled with the hot fix is fine), and create a registry value to indicate which behaviour you want.

The registry value is a DWORD called Last Page Simplex, under the appropriate key:

  • 32-bit systems: HKEY_LOCAL_MACHINE\Software\Pharos\Page Counter
  • 64-bit systems: HKEY_LOCAL_MACHINE\Software\Wow6432Node\Pharos\Page Counter

A registry file is included with the hot fix to create these values, and default to charging the last page as simplex.  The value should be set as follows:

  1. Set to 1 for the final page to be charged as simplex.
  2. Set to 2 for the final page to be charged as duplex.

Note: if this value is not set, charging may be unpredictable.

The Copier Adaptor Cable that connects the Omega CopyLink to the Copier's Foreign Device Interface (FDI) is designed and manufactured for each make and model of copier. There are a large number of copier FDI's to cater for and new models of copiers are arriving all the time so matching the Copier Adaptor Cable to your copier may require confirmation. The Copier Learner Mode on the Omega is designed to help the installer confirm that the Copier Adaptor Cable is wired correctly and then match up the Copier Price lines to the signals produced by the Copier's FDI.

 

Pharos supplies 2 class of Copier Adaptor Cables:

 

1. Simple cable that enables/disables the copier and counts one type of copy attribute. e.g. US Letter.
2. Advance cable that enables/disables the copiers and counts many types of copy attributes e.g. paper size, color or black&white, simplex or duplex. The copier's FDI dictates what attributes can be detected by the Omega CopyLink.

 

The first step in the Copier Learner "Configuring the copier interface" confirms that the Omega CopyLink can enable the copier and count at least 1 pulse.

Confirm that the copier is enabled by:

 

1. Checking that the CopyLink is showing a green light and a orange power light.
2. Checking that the copier allows you to make a copy.

 

If the copier does not allow you to make a copy then:

 

1. Confirm that the FDI is configured correctly. You may need help from the copier technician.
2. Confirm that the cable is correct by presenting the Copier Adaptor Cable number and make and model of the copier to Pharos support.

 

Once the copier is enabled you can make a test copy in step 1.

 

"Configuring the copier interface". You must see at least 1 pulse before proceeding. If you do not have at least 1 pulse then:

 

1. Confirm that the FDI is configured correctly. You may need help from the copier technician.
2. Confirm that the cable is correct by presenting the Copier Adaptor Cable number and make and model of the copier to Pharos support.

 

If you still cannot get pass step 1 then:

 

1. Your Omega Copier Adaptor Cable may have a manufacturing fault. Ask Pharos support for help to confirm the pin outs of the cable.
2. The cable needs redesigning. Ask Pharos Support to arrange another cable design.

 

Once you have passed Step 1 you can proceed to the advance testing page to find what copy attributes the Omega CopyLink can determine from the copiers FDI.

 

The Copier Learner can detect double pulse attributes and level changing attributes on the FDI. Sometimes the installer may try to detect different attributes but the Copier Learner does not detect different attributes. You may view the signals the are detected at each copier training steps by clicking the view button. If there are no signal differences between each of the Copier Learner steps then:

 

1. You may need an advance Omega Copier Adapter Cable.
2. Or the copier FDI does not present the attribute you are trying to detect.

 

The Copier Learner is design to detect most copier types of FDI signals. Sometimes it fails but the Omega Copier configuration can still be set up to detect the copy attributes by careful examination of the copier training step signals. You can send the measured signals to Pharos support for evaluation by:

 

1. Browse to Omega Web Admin > System > Files  context
2. Download files /etc/station/training.spec and /etc/station/copierTraining.sets
3. Send files to Pharos support.
4. Pharos support can upload these files into an Omega and view the signals detected directly for evaluation and recommend configuration values"

The Pharos CA certificate is a file located on the Omega SmartHub at:

/etc/station/PharosCACertificate.crt

This file can be replaced with a new certificate of the same name. Rename the CA certificate you want to use to "PharosCACertificate.crt" and upload it to the SmartHub, either via SCP on port 8022, or using the Files screen in Omega Administrator (this screen is available in 2.1.0 firmware or later). The replacement file must be Base64 encoded.  This is not the default export method from the Microsoft Certificate management snap-in.

Note: You may need the root CA certificate and Intermediate CA certificates (depending on what certificate the EDI server has installed). You should be able to include both in the PharosCACertificate.crt file.
The Microsoft Certificate management snap-in does not allow you to export multiple certificates in Base64 encoding, so you must export them separately, and then concatenate the files (e.g. by opening both files in Notepad, copying the contents of one and pasting at the end of the other).  The order of the certificates in the combined file is not important.

By default some local accounts disable popup and printing proxy controls. Enable the popup and printing proxy for the effected user accounts under preferences -- parental controls -- enable

- Popup

- Printing Proxy

This should resolve the problem.

Steps to fix issue:

  • Go to IIS / Applications Pools
  • Right-click DefaultAppPool / Advanced Settings
  • In the Process Model section, click Identity
  • Change it to a Local Service Account, Network Service Account, or a Local System Account. If none of those work the security messures in your environment might be preventing the usage. One final option is to set a Configurable account with the use of a Local Admin.

Windows Defender (formerly Microsoft AntiSpyware) reports a file used by the Pharos Popup Client as the Rivarts.A trojan.

 

The registry key:

 

HKLM\System\CurrentControlSet\Services\mchInjDrv

 

Has been detected as malware by Defender.

 

Microsoft is aware of this problem. Other third party applications use the same hook. So far, however, Microsoft has not whitelisted the application, madCodeHook by Madshi.

 

Madshi, the developers of madCodeHook (the file in question) is also aware of this issue.

 

For more information on Madshi, and madCodeHook see: http://www.madshi.net

 

This is a required file needed for the Pharos Popup Client to function and does not pose a threat to the system.

This can occur when Informed Print is being used, but the Mac system does not have Pharos Notify installed, and/or communication from the server to the client Mac is not open on port 28201.

One can verify Pharos Notify is installed by going to /Library/Application Support/Pharos/ and looking for Notify.  You can further verify that it's running by opening the Activity Monitor under /Applications/Utilities and looking for "Notify".  Please note "notify" without the capital N is an Apple process, and not the Pharos software.

To verify the server is able to communicate to the Mac over port 28201, you may run a telnet test on the server using a Command Prompt:

C:/> telnet MacClientIPAddress 28201

Substitue "MacClientIPAddress" with the IP address the Mac is using.  If you get anything other than a failure message return from the server in that command prompt, you've likely established a good connection to the Mac over port 28201, and in this case, port blocking is likely not the reason for the Notify failure.

While each new version of Uniprint brings new features to meet the growing and changing needs of customers, some features have been changed or deprecated to make way for new functionality. Following are a list of significant Database changes and altered or deprecated Uniprint features from version 7.2 onwards. It is recommended that customers planning an upgrade review the changes between the versions they are upgrading from and to for any possible impact on current behaviour before proceeding with their upgrade.

Uniprint 7.2

Removed features

  • The people table in the Pharos Database, which contained all data for Users and User Groups, has been split into a users table and a groups table. If your site uses scripts that reference the people table, these scripts must be updated to refer to the users and/or groups tables.
  • Due to changes to the structure of Job Cost Methods in Pharos 7.1, certain information is lost in an upgrade from a version of Pharos prior to 7.1. Any per job costs are not retained in an upgrade, you will need to re-enter any per job costs into the new Base Job Cost and/or Per Job Attribute Costs properties. Per page costs are migrated in an upgrade.
  • User-level permissions are no longer available; permissions can be set on a per-User Group basis only. In an upgrade, any User-level permissions that may be configured are removed from the database.

Uniprint 8.0

Enhancements

  • Area Costing is now based on a Per Square Inch Cost, rather than a linear Per Inch Cost. In an upgrade, all Per Inch Costs become Per Square Inch Costs, meaning that all Job Cost Methods that use Area Costing will need to be re-configured to ensure that jobs are costed correctly.

Removed features

  • The IP Address property for servers has been removed. Servers are now identified solely by their hostname, allowing Pharos to support servers with multiple network cards (correctly functioning DNS is required to support this).
  • Standard charging is no longer an option for Queues, and the Queue properties relating to Standard charging (Per Use Cost, Per Sheet Cost) have been removed. All Queues now use a Job Cost Method for charging. In an upgrade, Job Cost Methods that duplicate the Standard charging settings configured for each Queue are created and associated with the respective Queues.
  • The PrintOp feature of Pharos Uniprint is no longer available. The PrintOp Station application is no longer available in the Pharos installers and the PrintOp Stations context has been removed from Pharos Administrator. In an upgrade, all PrintOp Station records and PrintOp transactions are archived.
  • The BEAR POD is no longer available as a copy control device, meaning that PC Pharos Stations can no longer be used as Copy Stations to control photocopiers. All copiers must be controlled by a Network Terminal. All properties relating to Copy Stations and BEAR POD copy control device settings have been removed from Pharos Administrator.

Uniprint 8.1

Removed features

  • Per-use discount rates have been removed. When upgrading, any per-use discount settings will be removed, while per-unit settings will be retained.
  • The SQL List Popup Question Type has been deprecated in Uniprint 8.1. SQL List Questions will continue to work when upgrading from Uniprint 8.0 or earlier, but there is no interface in the Administrator to configure them. Cost Center Question Type or the List Question feature of Notify can be used in place of the SQL List Popup Question Type.
  • Web Remote is no longer available in Uniprint 8.1 and replaced by an MMC application.

Uniprint 8.2

Enhancements

  • Uniprint database and services have been updated to fully support Unicode. There is no noticeable impact on the existing system.
  • When costing a Duplex job with an odd number of pages, the final page is now costed as Simplex. This means that you must always configure Duplex/Simplex costs, even if Duplex printing is mandatory—if no Simplex cost is configured, the final page of odd-numbered jobs will be costed using the Default per Page Cost.

    • You can now add a registry key value (Last Page Simplex) to the Page Counter to determine how to charge the final page of any odd-numbered Duplex job.
    • The Page Counter registry entry "No Blank Pages" has been extended. Previously this could be set to charge for blank pages in a job, or to ignore blank pages (as many applications add a blank page to the end of an odd-numbered Duplex job). A third option is now available to charge for blank pages in the middle of a job, but ignore blank pages at the end.
  • When upgrading to Uniprint 8.2, new Banks may be added to your system depending on how the network terminals have been configured. After an upgrade, there will be a new Bank called Default Bank [CSO] in addition to the Default Bank. Uniprint automatically associates the Bank to the correct terminal.
  • User-Based Charging has been introduced to replace Discount Rate Schedules. If already defined before upgrade, Discount Rate Schedules will still be visible and useable, but cannot be altered or added to.
  • The Upgrader can now support upgrading the Database on a remote SQL server. The Upgrade or Migration should be run from the Principal Services machine.

Removed features

  • The Uniprint-specific SNMP functionality has been removed. Settings including SNMP Settings on the Devices context and SNMP Refresh Interval setting on the Uniprint Global Settings context have been removed from Pharos Administrator. You can continue to use SNMP status checking for a device using the settings available on the Microsoft TCP/IP print port.
  • The log file-related command line options for the User Batch Loader and Cost Center Importer have been removed. These utilities still create log files, but generate logs using the new Pharos Logging Service.

Uniprint 8.3

Enhancements

  • Support for the new Pharos MobilePrint solution, which enables users to print from any mobile device to any Pharos managed printer within the campus.
  • Modified Print Engine. The new Print Server job management engine has introduced the following changes:

        
    • The new Print Groups concept streamlines the configuration of large groups of printers, particularly in multiple server environments. It removes the need for “Compatible Queues”.
    •   
    • Improved performance and stability by reducing the dependency on the Windows spooler and its driver management.
    •   
    • While Windows queues are still used as a mechanism to receive print jobs from users, output devices no longer require a Windows printer object.
    •   
    • Jobs waiting to be released by the user are no longer held in the Windows printer object. They are transferred from the Windows spooler to the Uniprint Secure Release Service.
    •   
    • Maximum Job holding time has been increased from 2 days to 7 days.
  • Revised Administrative Permissions. While a Uniprint Print Server component still exists and is still installed on each print server, the “Print Server” concept plays a less central role in the configuration of the Uniprint system (e.g. the server is only important to Queues and Terminals, but not to Print Groups or Devices). Given this, Administrative Permissions now introduces the concept of a Management Zone. Each object in Uniprint belongs to a zone; you simply create administrative roles that have different levels of permissions to view, modify, create, or delete objects in the different zones.  The Zone functionality allows you to easily delegate administrative duties to different departments (e.g. to manage their own devices) even when they are sharing the same server resource.
  • Improved Security. You can now enforce strong passwords for User Accounts. A new section in the Security tab under System > System Settings allows you to select whether to enforce strong passwords, and whether to allow blank passwords.
  • Added a mechanism to check the status of a device before sending jobs to it.
  • Allows saving the spool files of specific print jobs from Pharos Administrator.
  • Automatic retrieval of the Make and Model properties of devices using Simple Network Management Protocol (SNMP). A new action called “Retrieve Make/Model” has also been added to retrieve these properties manually.
  • The introduction of the Secure Release Service has prompted many changes to plug-ins/scripts.  Please see this article for more details.

Removed features

  • Removes the need for Compatible Queues with the introduction of Print Groups.
  • Removed the relationship between Queues and Devices as well as the relationship between Devices and Servers.
  • Removes the need for a “ServerManager“ template in Permissions with the introduction of Management Zones.
  • The PageCountJob plug-in point is removed during the upgrade. It is no longer possible to specify a non-Pharos Page Counter. In addition, the Page Counter is now owned by the Secure Release Service.  As a result it is now found under the Pharos\SecureRelease directory.

If you are working with a Pharos Authorized Reseller, please contact the reseller for a license key.

If you are a direct customer of Pharos, you may e-mail or call us:

  • E-mail: licensing@pharos.com
  • Phone: 888-864-7768 (toll free US/Canada/Caribbean) or 585-360-1010, extension 5

If you have misplaced your license key and it's an emergency situation, call Pharos technical support:

  • from USA, Canada, and the Caribbean: 877-848-0397 (toll free) or 585-360-1099
  • from Asia-Pacific countries: +64 (9) 523-0737
  • from other countries: +1 (585) 360-1099

 

Analyst

  • Removed support for Microsoft SQL Server 2000

Server Tracker

  • Removed support for Microsoft Windows 2000

Workstation Tracker

  • Removed support for Microsoft Windows 2000

The EDI verification is failing.

 

Error related to: Edi verification tool fails unable to initialise session. Returns Access Violation error.

 

Example:

 

Server:

 

Windows 2003 SP1 running IIS 6.0
SQL 2000 SP4
Pharos 6.1+ (OTG)

 

What may be seen seen:

 

The PS20 terminals and the monitor translator work if the IIS_USER is in the local admin group. No other user groups work (ie. power users, etc). The Edi verification tool still fails although the translator is working correctly when the IIS_User is in the local admin group.
Solution:

 

Placing the IIS_USER into the Admin Group may work (does create a significant security issue, generally not accepted by the customer).

 

Alternate Solution:

 

- Run Component Services Administrative Tool
- Expand and go to: Console Root/Component Services/Computers/My Computer/DCOM Config/EdiServer
- Select and then Right Click on EdiServer, choose "Properties"
- Go to "Security" Tab
- Select in "Launch and Activation Permissions"
- "Customize" and press "Edit"
- Add local userid iuser(computername) and give that account Activation rights (Local should be sufficient).

 

Now the IIS_USER can be removed from the Admin Group.

Logging is configured using the Blueprint Server Configuration Tool.

1. Start up Blueprint Server Configuration located by navigating to the Start Menu -> Programs -> Pharos Blueprint Enterprise -> Blueprint Server Configuration. In Blueprint 5.0 there is a Tools folder in the Pharos Blueprint Enterprise folder.

2. Select the Logging Tab where you can set the Blueprint Service components logging level individually.

3. Please set the following components with Debuglevel of 10 and make sure you un-tick Log only errors to file:
     a. TaskMaster Service
     b. Administrator
     c. Tracker Web Service
     d. EDI Web Service
Note: For Blueprint 4.2 and above you will need to enable logging for the Job Service and Event Log Service as well.

4. Once enabled just click the Apply button on the Blueprint Server Configuration for the changes to take effect.

 

5. Take note of the file path on the Logging TAB as this is where the log files will be written to.

6. Once the logs are enabled then please reproduce the problem situation while logging is enabled and this should allow the particular problem to be captured in the log files that you can now send to Pharos Support for review.

There is only one way to install the Pharos Omega PS150 Schema:

For all versions of Pharos, the SQL script ini_schemas.sql must be run against the Pharos Database to add the “Omega PS150” Network Terminal type and its associated configurable properties. This script is installed with the Firmware, and is applied from the configuration menu at the Omega SmartPAD:

1. With the Omega attached to the network, open the configuration menu by tapping the top left corner of the SmartPAD’s touch screen five times. When asked for administrator logon details, use the default logon details.
2. Go to the PEDI screen.
3. Click Push Schema to Pharos Database.

Pharos Technical Support hours over Christmas and New Year period are as follows:

 

Christmas Holiday Hours of Operation

 

Monday 24th December – Closed 
Tuesday 25th December – Closed

 

New Years Hours of Operation

Tuesday 1st January – Closed 

 

From all the staff at Pharos Systems we wish you a very Merry Christmas!

The Uniprint Suite provides for several applications that may be installed onto a computer running MacOS 10.7.  These include:

Pharos Uniprint PopUp Client.  This software can be installed and used successfully on MacOS 10.7.  The latest version of the PopUp client currently available is from Uniprint 8.1 and is available here: Pharos Uniprint MacOS Components.

Pharos Uniprint Notify.  This software can be installed and used successfully on MacOS 10.7.  The latest version of the Notify client currently available is from Uniprint 8.1 and is available here: Pharos Uniprint MacOS Components.

Pharos SignUp.  The SignUp client that ships as packaged with Uniprint Suite 8.2 image and lower will not support MacOS 10.7. The version that is supplied with Uniprint Suite 8.3 (release date expected Summer 2012) will support MacOS 10.7.  Upon the release of Uniprint Suite 8.3, an updated SignUp client for Uniprint Suite 8.2 will also be made available on the Pharos Systems website: Pharos Uniprint MacOS Components.

Support for future releases of the MacOS operating system can only be determined after it is available publicly. Any update required for future MacOS releases will be posted to the website listed above.

For a detailed list of supported Windows platforms, please refer to the attached chart.

The "aspnet_wp.exe" process takes up to 90% of theCPU Resources all the time. I am seeing tremendous amounts of lines in the log looking like:

First-chance exception at 0x77e4bee7 in aspnet_wp.exe: 0xE0434F4D: 0xe0434f4d.

Additionally, many references to "No Symbols Loaded" as in the line below:

'aspnet_wp.exe': Loaded 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_wp.exe', No symbols loaded.

Lastly:

[2008/01/02 11:38:38 P1500 T00D i PEDI] Pedi.Application_EndRequest.

or:

[2008/01/02 11:38:38 P1500 T00D i PEDI] InitializeSession site_code=SITECODE
[2008/01/02 11:38:38 P1500 T012 i PEDI] InitializeSession site_code=SITECODE
[2008/01/02 11:38:38 P1500 T00D i PEDI] InitializeSession OK, UTCTime=01/02/2008 11:38:38
[2008/01/02 11:38:38 P1500 T012 i PEDI] InitializeSession OK, UTCTime=01/02/2008 11:38:38
[2008/01/02 11:38:38 P1500 T00D i PEDI] Pedi.Application_EndRequest.
First-chance exception at 0x77e4bee7 in aspnet_wp.exe: 0xE0434F4D: 0xe0434f4d.
[2008/01/02 11:38:38 P1500 T00E i PEDI] InitializeSession site_code=SITECODE
[2008/01/02 11:38:38 P1500 T012 i PEDI] Pedi.Application_EndRequest.
[2008/01/02 11:38:38 P1500 T00E i PEDI] InitializeSession OK, UTCTime=01/02/2008 11:38:38
First-chance exception at 0x77e4bee7 in aspnet_wp.exe: 0xE0434F4D: 0xe0434f4d.
First-chance exception at 0x77e4bee7 in aspnet_wp.exe: 0xE0434F4D: 0xe0434f4d.
[2008/01/02 11:38:38 P1500 T011 i PEDI] InitializeSession site_code=SITECODE
[2008/01/02 11:38:38 P1500 T011 i PEDI] InitializeSession OK, UTCTime=01/02/2008 11:38:38
[2008/01/02 11:38:38 P1500 T00E i PEDI] Pedi.Application_EndRequest.
[2008/01/02 11:38:38 P1500 T011 i PEDI] Pedi.Application_EndRequest.


Is found in the log file. Attatched a copy of a sample log file output.

Pharos recommend uninstalling and re-installing several components:

- .NET Services
- Pharos EDI

Clients that have Pharos Omega Terminals are recommended to update to the latest firmware revision, which is available on the Pharos website:

http://www.pharos.com/support/terminals/index.html

There are also several known viruses that attack this process. We recommend running an updated virus utility on the effected server.

1.

 

1) Open up the 'IIS Management Console'.

2) Select the 'Default Web Site'.

3) Select 'Bindings...' in the Actions pane.

4) Select 'Add...'.

5) Select 'https' and then the SSL certificate you desire from the drop-downs.

6) Click 'Ok/Close' through all the various dialogs.

7) Done.

The User Namespace is designed to replace the DB Namespace as the method for loading user accounts from the Pharos database for purposes such as adding new users, editing user accounts and authentication & billing. This provides a standard interface which will preclude the requirement to upgrade scripts in the situation that the internal Pharos database changes between versions.

The User Namespace has been designed to be executed within a Try/Catch block. This means all potential errors that could be thrown during a User command can handled without having to manage every call.

Only one user can be loaded at a time, loading a subsequent user will replace the existing user within the script context. If a User.GetUser function results in the return of multiple users an error will be throw, as is the case if no users are returned. As you can only search for a user based on a single column in the user table, using the DB Namespace may still be required in some circumstances.

The Pharos Script Primer with Pharos Help includes detailed information on the User Namespace.

Several example scripts are included with this article that show various functions. These scripts are complete, functional scripts, however they are provided "as-is" and no additional support is provided for these specific scripts. If you have custom requirements, please contact Pharos Professional Services:

+1 (585) 249 8889 option 2
pps@pharos.com

The error is produced because Crystal Reports failed to install.

As we do not control the Crystal Reports Installer there is a limit as to what we can do. However here is the command line that is used to initiate the install. This can be run from a command line after running the Pharos Reports installer.

We believe this gets extracted to the %TEMP%

%TEMP%\CrystalReports11_NET_EmbeddedInstall.msi /qn /l*v "%TEMP%\CrystalInstallLog.log"

In the command line statement above the last portion is where it writes a log file. So you should be able to find this on the failed machine in the %TEMP% Directory on the machine having an issue.

In cases where have seen this issue the Crystal Reports is trying to install to the C-drive and there is not enough space to install it.

The EDI URL changed in Uniprint 8.1.  Previously it was in this form:

http://server/PharosEdi/Pedi.asmx

The new form is:

http://server/PharosEdi/EdiService.asmx

Additionally, the pedi.wsdl file no longer exists.  The WSDL description of the service can be viewed through this URL:

http://server/PharosEdi/EdiService.asmx?wsdl

If your IMFP software does not allow you to specify an EDI URL, you may need to contact Pharos Support to obtain a newer version of the software.

The most current lists of supported MFPs are located on the Pharos website. Click here to go to the page. At the bottom of this page you will find links for each printer vendor that has MFPs that can be integrated with Blueprint.

To confirm compatibility between a particular Blueprint version and a particular iMFP version, contact support@pharos.com.

This error will appear when permissions tighter than the default ActiveX DLL security permissions are applied to the .NET framework. These can be adjusted in Internet Explorer or the .NET framework configuration screen in:

Control Panel > Administrative Tools > Microsoft .NET Framework 1.1 Configuration.

To adjust these settings:

1. Open Control Panel > Administrative Tools > Microsoft .NET Framework 1.1 Configuration
2. Click on Configure Code Access Security Policy
3. Click on Adjust Zone Security
4. Click on Make changes to this computer
5. Select My Computer and set the level to Full Trust
6. Click Next and Finish
7. Restart the Pharos Blueprint Installation

Note: you may need to remove the created c:\program files\pharosblueprint directory that was created during the failed installation.


This can be easily checked by looking at the Pharos key in the Windows Registry.

Run regedit and find the entry:

HKEY_LOCAL_MACHINE\SOFTWARE\Pharos\Installed Components

The Data field, for each entry, lists the build number for each component (which can be checked against the version).

Compare the build numbers listed in the Data field to the list below:

  • Pharos version 7.2 is build 4273
  • Pharos version 7.1 is build 4003
  • Pharos version 7.0 is build 2909
  • Pharos version 6.1 is build 2371


For example, if Pharos 7.2 is installed the Data field should show 4273 (or higher if any hot fixes were applied) for each entry.

If the numbers shown in the Data field are not at least as high as the current version build number (above), then that component needs to be upgraded.

NOTE: All Pharos Servers and Pharos Stations need to be at the same Pharos version.

When running an upgrade of the Pharos Database the following error appeared after starting the upgrade process “Pharos is not the database owner”. The SQL login 'pharos' is the db_owner.

 

Inside the pharos database, the objects are owned by a user role other than db_owner. For our upgrade scripts to work the objects must all be owned by the user role db_owner, and this role should be assigned to the SQL login 'pharos'. The following SQL query will update the user role ownership of the objects in the Pharos Database. Steps on setting the SQL login as db_owner can be found in a separate FAQ.

 

USE master
EXEC sp_configure N'allow updates', '1'
RECONFIGURE WITH OVERRIDE

 

USE pharos
update sysobjects set uid = 1

 

USE master
EXEC sp_configure N'allow updates', '0'
RECONFIGURE WITH OVERRIDE

The server IP Address in Pharos Administrator does not match the IP Address of the server's network card. To fix this:

   1. Run Ipconfig from a DOS command prompt to find your current IP Address.
   2. Open Pharos Administrator.
   3. Scroll down to System and select Servers.
   4. Change the IP Address to the current IP Address assigned to the Nic card.
   5. Click on Change Control.

The Signup Clients should pick up the correct settings and the users should be able to log on.

1. Create a text file with something in it on the server this machine is configured against.
2. Use the LPR command line to submit this job to the device.
3. So in your case you could use the below command.

 

lpr -S <ip of printer> -P raw test.txt
(there is a space after the -S and a space after the -P)

 

this will verify that the device is able to receive print jobs via LPR.

 

You could also use the LPQ command. Notice that this command has NO space between the -S and the IP Address of the device or the value of server in the example.

 

Displays the state of a remote lpd queue.

 

Usage: lpq  -Sserver -Pprinter [-l]

 

Options:
     -S server    Name or ipaddress of the host providing lpd service
     -P printer   Name of the print queue
     -l           verbose output

 

If you are not able to LPR a print job to the device then Uniprint or Blueprint will fail as well when trying to do the same thing.

If Standard Charging is used rather than a Job Cost Method when setting up charging for a given Spool Queue, Discount Rates are not correctly calculated.

This is a known problem in Pharos versions 7.1 and 7.2. Customers can workaround the problem by setting up a Job Cost Method.

Article:
How do I set up Job Cost Methods?

 

7.2 will be updated with a hot fix to resolve the issue. Please check the Pharos downloads web site for hot fix information.

 

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

Pharos Omega PS60 1.1.0 Firmware

This document contains the release notes for this firmware release of the Pharos Omega PS60 solution. If you encounter any problems or require further assistance, contact your Pharos Authorized Reseller.

This Omega release supports Pharos Uniprint 7.2 and later and Pharos Blueprint Enterprise 3.5 and later

Known Issues

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:

  1. 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.

  2. Omega requires Pharos certificates for SSL

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

  3. Server name restrictions when using SSL

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

  4. 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.
    • Using the web browser's Refresh button or F5 is not recommended while using Omega Administrator. Refresh pages by clicking menu link on left navigation panel.
  5. 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 Learn Copier wizard usually results in the correct number of copy lines.

  6. 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 Pharos EDI screen of Omega Administrator.

  7. Passwords not supported

    As there is no way for a user to enter passwords on the PS60, Logon IDs with a password are not supported and protected print jobs with a password cannot be released.

Installation Notes

  1. IMPORTANT : Connect the site's network to the WAN port!

    Make sure that the site's network is connected to the WAN port otherwise the site's network may malfunction because a DHCP server is running on all the other ports.

  2. Adding Omega-PS-60 Terminal Types to Pharos Servers

    The Omega-PS-60 Network Terminal type is added automatically when the first PS60 is connected to a Pharos Uniprint EDI server. For Uniprint 8.0 and above create your first PS60 as type Generic 1.0.0, it will be automatically upgraded to a Omega-PS-60 type when the PS60 connects.

    Note: You must apply Hot Fix 15 to Pharos 7.2 before installing a PS60. These Hot Fixes contain an update to the EDI Server that allows the configuration schema to be installed. Hot Fixes can be downloaded from the Pharos web site.

    If you are using Omega with Pharos Blueprint Enterprise 3.5, the configuration schema must be updated manually. Copy the files included in the firmware package directory \Blueprint into the Blueprint\bin directory of the Analyst server. Run the batch file InstallPS60TerminalType.bat

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

  3. Servers allowed to access the printer

    If the PS60's print server is not on the Pharos EDI Server it must be added to the Servers allowed to access the printer list in the Omega Administrator > Settings > Network > Advance Settings context.

  4. Omega requires Uniprint to run against 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) or later. 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.

  5. Omega Administrator browser support

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

    The timing diagrams that appear in the Copier Learning wizard are displayed using the Scalable Vector Graphics (SVG) specification, which is not supported natively by Internet Explorer. In order to view timing diagrams in Internet Explorer, you must install the Adobe SVG Viewer plug-in.

    Javascript must be enabled.

Custom Modules

Pharos install packages can run custom user-created modules to add custom functionality to install packages, such as installing additional applications along with the Pharos software, or modifying printer settings. A custom module can be an executable, a batch file or a self-extracting zip file, for example.

To add a new Custom module, click the Insert button on the Custom Modules context toolbar. This opens the Custom Module Insert Wizard, which collects the necessary information and creates a new definition entry with it.

Use the Custom Module Insert Wizard to create a new Custom module

     1. Enter a name for the module and click Next.
     2. Click Finish.

The new module is inserted into the Pharos Database. The Custom Module entry appears in the List Window of Pharos Administrator. All properties appear below in the Properties Window, where all further modifications to the module are made.

Install Order

When an install package is run, it runs each module in a set order. Pharos-supplied modules and Spool Queue modules are run first, then any custom modules. This property specifies the module's place in the order relative to all other custom modules.

The change the module's install order, enter a new value into this field. Values must be between 1000 and 20000 - the lower the number, the earlier the module is placed in the install order.

To check what numerical value is assigned other modules, open SQL Query Analyzer and run the following query:

     select * from modules

For additional information on how to use Custom Modules see Pharos Help. Search using the term: "Using Custom Modules "

The wait times specified for reservations are estimates only. These estimates are based on average session lengths to try to give the most likely wait possible. Essentially, SignUp calculates the average session time based on past sessions, and uses this value to guess at which current session will end next. The predicted end time for this session is then used to inform users when the next computer will be free. However, if the session that is predicted to end first actually goes on for longer than average, the calculation will be performed again - this often results in the wait time increasing. On there other hand, if another session ends early, the wait time immediately drops.

Pharos considered options such as simply displaying the wait time based on the assumption that patrons will use their full sessions; however this is not always the case, as sessions can end early. If patrons were only presented with a specific session start time, and someone were to end a session early, then their session could start considerably earlier, but it's likely that the user would have seen the later start time and walked off, missing their session start.

Solution:

Some control on how the estimation engine determines these 'estimated times' can be obtained by modifying the Signup registry key (see below). By increasing or decreasing this value you can affect the accuracy of the estimated wait times. Times will still vary due to session end time differences, but decreasing this amount should reduce the amount of that variance.

The key is [HKEY_LOCAL_MACHINE\SOFTWARE\Pharos\SignUp Server\Minimum Sample Duration Percentage]

NOTE: Additional information regarding this key can be found in Pharos Help by searching for "SignUp Registry Entries."

As in previous versions of the Mac package, our most current offering allows for customization of the package for mass deployment.  This will allow users to install shared Pharos Uniprint Print Server queues at the same time that the Popup and Notify client are installed.

Please download the "TechNote Automatic Popup and Print Queue Configuration for Mac OS X" below for those instructions.

In order to use Omega Terminals with a Pharos Billing Gateway and not have user accounts in the Pharos Database. The following script must be created and attached to the Bank's Logon event:

PlugIn.Result = true;

For additional information on scripts, see Pharos Help and search for the following phrases:

  • Adding, Editing and Deleting Scripts
  • Pharos Scripting Language Primer
  • Plug-in and Scripts on the Pharos CD


The MAC OS 10.5 platform is supported by the Pharos SignUp Client, which can be obtained from the Pharos website:

 

Macintosh Downloads

The package creator produces debug logs using standard Pharos logging. Use the Log Setter utility (available on the Pharos CD at tools\utilities\logsetter) to configure and activate logging for the package creator.

 

The package creator can also run in debug mode (see below).

 

When packages are run, they produce a log file called pslog.txt in the system Temp directory of the client PC, e.g. Documents and Settings\[username]\Local Settings\Temp. If the package install failed, this file will contain an error message.

 

Package Creator Command Line Options

 

The following command line options are available for the PackageCreator.exe executable:

 

/d = Debug mode – this enables a Step button on the progress bar dialog, which allows you to step slowly through each part of the process, so you can see where problems arise.

 

/q = Quiet mode – specifying this option means that the progress bar dialog is not displayed. If debug mode is also activated, this option has no effect.

If you are working with a Pharos Authorized Reseller, please contact the reseller to renew your license key.

If you are a direct customer of Pharos, you may e-mail or call us:

  • E-mail: licensing@pharos.com
  • Phone: 888-864-7768 (toll free US/Canada/Caribbean) or 585-360-1010, extension 5

Pharos Technical Support operating hours are:

 

Monday through Thursday: 7am - 9pm Eastern Time
Friday: 7am - 5pm Eastern Time

 

Customers can log an Incident with Pharos Technical Support 24 hours a day.

 

Email  support@pharos.com

 

Phone:
    -  from USA, Canada, Caribbean   877-848-0397 (toll free) or 585-939-7099
    -  from New Zealand    0800-452-556
    -  from Australia    1800-635-099
    -  from China N    10800-713-1595
    -  from China S    10800-1301-557
    -  from Japan    0066-33-821591
    -  from Singapore    800-1301-888
    -  from other countries    +1 (585) 939-7099

 

Incidents logged outside of normal operating hours will receive a response the following business day.

Before you begin the upgrade, you should complete the following tasks:

  • Read the “Blueprint Installation Guide” in the Documentation folder on the Blueprint disk image and ensure that your current installation meets the requirements for the version to which you are upgrading. These planning steps are just as critical for the upgrade as for a new installation.
  • Read the “Readme.htm” document. There may be additional release notes related to your upgrade.
  • Back up the Blueprint Analyst database.
  • Back up all configuration files. This is most easily done by running the Installation Configuration Collector tool, PharosSystems.Core.InstallConfigCollector.exe. This is installed in the PharosSystems\Blueprint\bin directory. Run the tool by double-clicking on it. All files are written to a zip file called InstallationDetails.zip, which is created in the local Temp directory of the logged on account.
  • Obtain versions of all custom integrations suitable for the version to which you are upgrading. Custom integrations must be upgraded separately from the main product. Contact Pharos Professional Services about upgrading custom integrations.

Note:

  • If your Blueprint Analyst is running SQL Server 2000, either upgrade to SQL Server 2005 or migrate the databases to an existing SQL Server 2005 instance. In the latter case, the SQL Server must not be hosting Blueprint databases for another Blueprint server.
  • The Blueprint Enterprise 4.2 installer will upgrade an existing installation. The installer supports upgrading from Blueprint Enterprise 3.1 and higher. However, it will not upgrade the original Blueprint Enterprise 3.5 release. You must have the Blueprint Enterprise 3.5 service pack 1 and/or Blueprint Enterprise 3.5 hot-fixes installed. Blueprint Enterprise 4.2 will directly upgrade Blueprint Enterprise 3.5 R2.
  • When upgrading Blueprint Enterprise, all Blueprint components should be upgraded to the same version. Click to see the order in which you should upgrade the components.

Cause:
Mixed mode authentication for SQL was not set up.

 

Solution:
Set up Mixed mode authentication.

Introduction

This document describes in detail the changes in Print Server plug-ins introduced in Uniprint 8.3. Prior to Uniprint 8.3, all print jobs were kept in the spool queues. In Uniprint 8.3, print jobs will be managed by the Pharos Secure Release Service (SRS) which replaces the dependence on the Windows spooler for print job management. The interaction with the Secure Release Service has introduced some changes to the print server plug-ins.

Removed Plug-In Point

  • PageCountJob

    This plug-in point has been completely removed. In Uniprint 8.3, page counting is no longer handled by the Print Server; it is managed by the Secure Release Service.

General Property Changes

Some of the properties exposed by the PlugIn interface have been changed since print jobs are now managed by the SRS, not the windows spool queues.

  • PlugIn.JobID

    JobID used to match the spool file name in the windows spooler, for example a JobID of 1 matched the 00001.spl file in the Windows spool directory. Now, the Job ID should be treated only as an abstract token representing the job.

  • PlugIn.Queue

    This used to give the windows spool queue that held the print job. Now this is the source queue name that originally received the print job. It could also be empty if the job came directly from other source, like MobilePrint.

  • PlugIn.JobPath

    This used to give the absolute path to the local spool file, like C:\Windows\System32\spool\PRINTERS\0001.spl. Now it will contain a path relative to the SRS job store, for example:

    user1\00000001-0000-0000-0000-000000000001.spl

    Since the job could be kept in a remote server in a customized location, the job path is provided for informational and backward compatibility purposes.

  • PlugIn.JobType

    New in 8.3. Used to determine the type of a print job (whether “Native” or “MobilePrint”). Notify functions such as QuestionBox and MessageBox which expect a user response and do not get one may cause a job to be deleted. If you install the new Pharos MobilePrint application and you have scripts in place that rely on user interaction (such as using Notify to confirm user acceptance), you may need to exclude MobilePrint jobs to ensure they are not cancelled.

    Checks which can be used within the scripting interface to exclude MobilePrint jobs from Notify interactions:

    1. A check for Native jobs, to only perform actions for native jobs and bypass MobilePrint jobs, ie: if (PlugIn.JobType == "Native")
    2. A check for the existence of Popup data - this is used in the sample scripts on the Pharos CD, ie: if (not String.IsEmpty(host))
    3. A check for Direct Queue, to only show notify dialogs for Direct printing (MobilePrint jobs are Secure Printing), ie: if (PlugIn.Direct)

Plug-In Interface Change

  • MoveJob

    This plug-in was called whenever an administrator moved a job between queues. In 8.3, a job does not physically belong to a spool queue, but is owned logically by a print group. So now a print job can be moved between print groups rather than queues. In the script interface, PlugIn.QueueFrom and PlugIn.QueueTo have been replaced with PlugIn.PrintGroupFrom and PlugIn.PrintGroupTo. In the executable interface, the 5th and 6th arguments will become source print group and target print group accordingly.

  • CostJob

    In earlier versions, the Job Cost Method used to be defined at the queue level. In 8.3, the Job Cost Method is defined at the print group level. For the script interface the PlugIn.PrintGroup property has been added, and for the executable interface a new argument <printgroup> has been added to the existing argument list. Please note the PlugIn.Queue property and <queue> argument will remain, but they refer to the source queue that originally received the print job.

Namespace Function Changes

  • Win32.GetJob

    Due to the change in print job storage, some job information items will no longer be supported. For example, the PrintProcessor(7), DriverName(9), Priority(14), Position(15) etc. The following list contains the fields (and IDs) that will be supported.

    Read-only properties

    • JobId (0)
    • PrinterName (1)
    • MachineName (2)
    • NotifyName (5)
    • Status (11)
    • TotalPages (18)
    • Size (19)
    • PagesPrinted (22)

    Read-write properties

    • UserName (3)
    • Document (4)

    Not supported

    • Submitted (20)
    • Time (21)
  • Win32.SetJob Command

    Only two fields, marked as read-write, can be set. Note: In Rev 257 (Print Server/Secure Release Service), Win32.SetJob (...) will return an error instead of throwing an exception for an invalid field.

    • UserName (3) read-write

    • Document (4) read-write

  • PrintJob.Copy

    The function will still duplicate a job to the Secure Release Job Store. With the Uniprint 8.3 General Release, the last optional argument [offset_int] is not used. The job will always be duplicated with popup data, if any, stripped off.

    Rev 257 (Print Server/Secure Release Service) or later: The function has been updated to use the last argument [offset_int]. By default, the function removes any popup data. It will retain the popup data when [offset_int] is less than or equal to Zero, a value greater than Zero will remove the popup data.

    Warning: the duplicated job will be scheduled as a new job to the system and will trigger a series of plug-in points. Extra care is needed here as unconditional copying could result in an infinite loop.

  • PrintJob.SaveTo

    This function is new in 8.3 to save a copy of the print job to a local path. In 8.2 and prior the script had direct access to the spool file via the PlugIn.JobPath. In 8.3 the job could reside on a remote server or could even be encrypted. PrintJob.SaveTo can be used instead to create a local copy of the job. The caller is responsible for cleaning up the resulting file. The function signature is:

    PrintJob.SaveTo(id_int, filepath_string) returns boolean

Available resources

Please refer to these Pharos Help topics for detailed information on scripting and Plug-In interfaces.

  • About Plug-ins: How plug-ins are called and in what order.
  • Plug-in interfaces: detailed interfaces for both executable plugins and script plugins.
  • Pharos Script Primer: scripting and namespace functions.

When using the command line tool, do not use any of the Action Switches (-PS or -PU). The default is to Insert Only.

 

example:
userload --logfile c:\my_log.txt --server VarsityDC --cashier admin --purse 25.00

Possible causes of this problem are:

  • An error at the employee’s workstation may have meant that the job was not submitted. The employee may click Print, then immediately walk to the printer to release their job, not noticing that a printing error has occurred, or a window has popped up that they need to OK before the job is submitted.
  • The employee may have mistakenly printed their job to a non-secure queue on the device, meaning the job would have already printed (but they might not notice, since they are expecting to have to release it first). Check whether or not printing to the device is optional, and if so whether or not the queue the employee printed to is secure.
  • If the employee has printed to a Print Group, it may be that the device they are trying to release their job at is not a member of the correct group. Check Print Groups in Blueprint Administrator to make sure that the device that the employee has logged on to is a member of the group that they printed to.
  • If configuration changes that affect the Secure Release Here system have been made recently, they may not have been replicated to the relevant Collectors yet, which could cause problems. You can force Collectors to update their cached information by clicking the Clear Cached Data button on the Server Health screen in Blueprint Administrator.
  • Server communication issues may mean that the list of the employee’s print jobs cannot be retrieved. This can happen if the server that the employee printed to is not contactable, or if the server the printed to cannot contact the Analyst. Check network connectivity to make sure that all servers are online.