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

PS150 v2.1.2 and v2.1.3 do not support the "Showing Others"  feature against Uniprint 8.0. As of PS150 version 2.2.0 there will be full support with Uniprint 8.0.

 

Please check the web site for details.

When I click keys on the Pharos Kiosk sometimes the key isn't selected correctly. How do I align the software touch pad on the screen?

 

or

 

How do I align the touch pad on the Pharos Kiosk? Customers should regularly align the touch pad on the Pharos Kiosk.

 

To align the touch pad of the Kiosk perform the following actions:

 

1. Click on the “Elo” icon located on the system try of the Kiosk desktop.
2. Select the button on the screen that comes up for touch alignment.
3. Follow the alignment instructions

The Pharos IR Control provides screen sound control and this should be used to turn panel sounds off - firmware versions 2.1.0 or above produce sounds on the SmartPAD Panel. The Omega hub also produces system sounds, however a tool is not provided to turn this off at the moment.

Customers can use the following 3rd party tool to log onto the terminal and adjust the sound control file.

You can download the 3rd party tool (putty) using the following link:

http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

Instructions

1. Download and extract putty
2. Run putty from the start menu
3. In the hostname field put the host name or IP of the Omega PS150 unit.
4. Set the port to 8022.
5. click open and when prompted login using the root user
6. edit the following file using a vi command in the putty terminal window

vi /etc/pgserver.conf

7. Set value by arrowing cursor over char and press 'r' then number.

The line to change is: default sound=-70

8. Set to your desired level. The range is -100 to 100 percent inclusive.

sound=0 or sound=-100 turns sound off.

9. Save the file by typing 'ZZ'

10. Exit putty and reboot the Omega PS150

The Pharos Omega PS150 supports the below RFIdeas models of HID Prox card readers. For other devices please contact Pharos Support for compatability

 

** They are keyboard emulation devices so, to the PS150, they all look the same.

 


RFIDeas - 13.56 MHZ
-----------------------------------
HID - RDR-7081AKU - (13.56)
Mifare - RDR-7581AKU - (13.56)

 


RFIDeas - 125 Khz
------------------------------
HID - RDR-6081AKU - (125kHz)

When installing Pharos Blueprint and completing the step within the Server Configuration utility, the following message appears (see example error message below):

Blueprint Install Configuration Error - IIS in 32-bit mode

 

"There was an error while configuring the Pharos Blueprint Enterprise Service. Start registering ASP.NET scriptmap (2.0.50727) at w3svc/1/Root/PharosSystems/. Error when validating the IIS path (w3svc/1/Root/PharosSystems/). Error code = 0x80040154 The error indicates that IIS is in 64 bit mode, while application is a 32 bit application and thus not compatible."

Further, when clicking OK in the error dialog box, the Blueprint test fails for both the Tracker and EDI Web Services.

The problem is due to the PharosSystemsAppPool not running in the 32-bit address space on a 64-bit system. Microsoft Windows IIS Server 7 running on a 64-bit platform will allow both 32- and 64-bit application pools (Windows 2003 64-bit only allows one or the other, not both). By default, however, the 32-bit function is not enabled.

 

In order to allow a 32-bit application pool, run the following in an administrative command prompt (as one line; your browser window may break the line):

 

%windir%\system32\inetsrv\appcmd set config -section:applicationPools -applicationPoolDefaults.enable32BitAppOnWin64:true

 

and then follow up with:

 

%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -i

 

which reinstalls ASP.NET in 32-bit mode as well. You should not have to issue a reset of iis (iisreset), but it won't hurt if you do.

Attached is the Customer Services Kiosk - Users Manual

Pharos only limits printer port restrictions (515, 9100) so that network administrators can still configure the printer itself. Most printers can restrict network access to the web configuration and printing pages of the printer. Pharos encourages all network administrators to make sure that printer web pages are restricted to administrative access only.

Occasionally Pharos Omega terminals may restart unexpectedly. If this occurs please ensure you have applied the latest firmware, available from the Pharos web site:

 

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

 

Contact Pharos Technical Support if the updated firmware does not resolve the issue.

 

Please revisit this knowledge base article or the Pharos web site for updates on this issue.

I recieve the following error when installing the Pharos Database and Database services on Windows 2008 R2 after installing SQL

"Corrupt Installation Files"

You recieve this message because you have not yet rebooted the server after installing SQL. Reboot the server and you should then be able to install Pharos Uniprint 8.1

The Pharos Client Tray is removed by deleting the Registry REG_SZ value 'Pharos Systems Blueprint Client Tray' from the following key:

 

32-bit Windows: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
64-bit Windows: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Run

 

Removing this will not have a negative impact on the Tracker performance. However, a user will not be able to see currently-assigned Print Policies, nor will he or she be able to release Secure Release Here jobs from the desktop (when enabled through the Blueprint Administrator).

When using the Blueprint Administrator application, it may produce an error dialog box stating "Error: Control does not support transparent background colors" and then quits. This only happens in Windows Vista, Windows 7, and Windows 2008 Server. How can I fix it?

Cause

This error occurs because some functions of the Blueprint Administrator for the versions specified below do not support the transparency function in the Microsoft Aqua interface.

Resolution

Right-click PharosSystems.Blueprint.Administrator.exe (found in \Program Files (x86)\PharosSystems\Blueprint\Bin in a 64-bit operating system) and choose Properties. From there, click the Compatibility tab and then check the box next to "Disable visual themes." Click OK to set and then relaunch the Administrator application.

Affected Versions

This affects:

  • Blueprint Administrator 3.5.x
  • Blueprint Administrator 4.1.x
  • Blueprint Administrator 4.2.x
  • Blueprint Administrator 5.0.x

Please note that Blueprint Administrator 5.1 and higher have been modified to support Aqua transparency effects.

For an image of the dialog box generated, or a visual example of the Compatibility setting, please click on any of the image links below.

How can I reset the Grant back to its initial value and the user quotas?

We have a Cost Center set up as a grant that has a "budget" of x dollars and each user that is assigned to be able to use that CC has a quota. The new fiscal year is starting so we need to reset the grant's budget pool back to the default budget value of x dollars and also reset each user's "spent amount" back to zero. I have looked in the Help section in Pharos Administrator but do not find a way to do this.

In order to reset the dollar values of the Grant and the Quota value for each user follow the information below.
Note: You can reset this property back to zero using the "Reset Grant" action from the Charging Models action pane.
1. Open the Pharos Administrator
2. Navigate on the left hand side to Third Party Charging > Charging Models > select your Charging Model > Expand to a Category where the Grant exists > select the Grant.
3. On the right hand side in the Actions Pane of the MMC click on the link to "Reset Grant".
See attached screen shot for reference.

Pharos Blueprint Administrator can be installed on a remote workstation to run reports. During the installation process you need to select "Administrator Install Only" which will install only the administrative components required to administer the system and run reports.

 

There is no separate reporting application.

The PS60 can be configured to display status and error messages on the printer display using a PJL command instead of printing them. However, not all printers support the PJL message command.

A customer can easily test if the printer supports PJL messages by the following procedure:

Here are the instructions to run on windows:
1. telnet printerIP 9100
2. paste in:
@PJL RDYMSG DISPLAY="This is the message"
3. press enter
4. press Ctl+]
5. type quit
6. press enter

If the message "This is the message" is displayed on the printer display then this would indicate that this device supports this feature, if not then there is nothing we can do to make it display the information as it is not supported by this device.

Customers that upgraded to Uniprint 8.0 and then upgraded there Pharos Omega terminals will recieve this error as the Pharos Omega PS150 terminals are not capable of pushing a current schema to a Uniprint 8.0 installation that was upgraded.

This is a known issue and customers should apply the attached SQL schema ini object to manually update the database. Customers should only use this update if:

  • You are now on Uniprint 8.0 or later.
  • You performed an upgrade from a previous product version (i.e. did not do a fresh install).
  • You uses PS150 (PS60 is not affected).
  • The terminal software is more recent than the ini_schema in the Pharos database.
  • The ini_schema currently in the database is older than 2.1.1.
  • The terminal software is older than 2.2.0

To install this schema update do the following

1. On the Pharos Database Server (SQL) open a query window

2. Copy the attached contents of the update_ps150_schema.sql file into the query window

3. Execute this against the Pharos database

4. Complete a change control in the Pharos Administrator to complete the process

On a Cluster server, failing over to the other node does not preserve the Workstation Release setting on a Blueprint 4.2. What do I do now?

 

When Workstation Release is enabled on a Cluster Server, moving the resource group to the other node does not preserve the Workstation Release setting. Hence, failing over to the other node disables the Workstation Release. When users send a print job to a secure queue, they will not be able to release the Print jobs using the Workstation Release window (Blueprint Console dialog) on their workstations.

If you want users to continue using the Workstation Release to release their print jobs, you can re-enable the Workstation Release on the failover node.

 

To re-enable the Workstation Release, open the Blueprint Secure Release Here Troubleshooter from Programs > Pharos Blueprint Enterprise > Tools.