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

Knowledge Base & Downloads

August 2013 Previous month Next month

Close your browser and re-open the status page for the HP 4345 printer. Alternatively, cycle power to the HP 4345 printer.

How do I retain my theme when updating from an older Pharos Omega firmware version (pre-Pencarrow)?

 

The latest Pharos OmegaAdmin tool will not allow me to download the current theme from the Omega Terminals. If the OmegaAdmin tool will not allow you to retrieve the current theme from a Pharos Omega unit, the current Omega firmware is too old - a new theme system was introduced in firmware release 1.4.4 (Pencarrow).

 

In order to restore the theme you must have copies of the existing bmp files that were originally uploaded with the current firmware version. You must then upgrade one unit to the latest firmware and retrieve the default theme using the OmegaAdmin tool included in the latest firmware package.

 

Upon retrieving the latest firmware version you need to the edit the default theme and modify the background etc with the original images.

 

You should then push the new theme using the OmegaAdmin.

 

Detailed instructions on editing, retrieving and pushing themes are included in the latest PharosOmega.pdf file that can be downloaded with the firmware from the Pharos Website:

 

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

In working with Mike P and HP we found that the HP Devices are able to provide us with better logging of issues even after reboots through a Stack Dump.

 

To access those files you would need to browse to the HP devices webpage at http://Device_IP/hp/device/svcErr.log.

 

Mike suggest that issues where you receive 49.xxxx error to gather the file that is produced and name it as the model of the device and serial number of the device if possible before transitioning to him.

By default, a Pharos terminal (any iMFP, an Omega PS-150, or Omega PS-200) attached to Pharos Blueprint for Secure Release Here (SRH) does not display the name of the user (also known as "owner") who submitted the print job. However, if utilizing the "delegate printing" ability through the authentication script, the ability to see who owns the print job is necessary. To enable the display of the owner when listing jobs, use the following procedure. This procedure assumes the use of Pharos Blueprint 4.2.

  1. Set up the terminal as you normally would in Blueprint Administrator.
  2. On the Collector or Analyst (whichever is hosting the EDI service), locate the terminal's ".terminal.config" file. In Windows 2003, this would be in C:\Documents and Settings\All Users\Application Data\PharosSystems\Blueprint\TerminalPlugins. In Windows 2008, this would be in C:\Program Data\PharosSystems\Blueprint\TerminalPlugins. For this example, the Omega PS200.1.0.1.terminal.config file will be used.
  3. Move this file to the Blueprint \Bin directory (C:\Program Files\PharosSystems\Blueprint\Bin; on 64-bit systems, start in C:\Program Files (x86)).
  4. In NotePad or other text editor, look for this section:

              <Property ReadOnly="false" Clonable="true" Advanced="false" Hidden="false" Type="boolean">
                   <IniSection>uniprint</IniSection>
                   <IniLabel>show print job owner</IniLabel>
                   <Name>Show Print Job Owner</Name>
                   <Tab>Printer</Tab>
                   <HelpId>120001</HelpId>
                   <Default>false</Default>
                   <Override ProductName="Blueprint">
                        <Property Hidden="true">
                             <Default>false</Default>
                        </Property>
                   </Override>
              </Property>
  5. Edit this section to remove the <Override> group. An edited example is shown below:

              <Property ReadOnly="false" Clonable="true" Advanced="false" Hidden="false" Type="boolean">
                   <IniSection>uniprint</IniSection>
                   <IniLabel>show print job owner</IniLabel>
                   <Name>Show Print Job Owner</Name>
                   <Tab>Printer</Tab>
                   <HelpId>120001</HelpId>
                   <Default>false</Default>
              </Property>
  6. Save this change and exit the text editor.
  7. In a Command Prompt window that is running as an Administrator, navigate to the Pharos Blueprint \Bin directory.
  8. Execute the following command:

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

    Note that this example assumes that Microsoft Windows is installed to the Windows directory. Also, replace the file name (shown in blue) with the .terminal.config file that has been moved and edited.
  9. Back in Blueprint Administrator, go to Devices > Terminals and select the terminal.
  10. Click its terminal schema tab (in this example, the "Omega PS200 Configuration" tab was clicked).
  11. Find the "Printer" section and enable (check the box for) "Show Print Job Owner" and then click "Apply" to set the change.

It will be a few moments before the terminal gets a refreshed download from the EDI service. However, once it is pushed, the list of jobs displayed after logging in will list the print job's owner.

Note: This knowledge base article mentions a function called "delegate printing." Delegate printing allows a user to print another's job(s). For example, an administrative assistant can be authorized to print his jobs as well as those of the people he supports. This function is enabled through modification of an authentication script along with user modifications in the database. Please contact Pharos Systems Technical Support for a list of prerequisites and how to implement the function should you wish to implement delegate printing.

When I browse to the Pharos Omega PS150 devices web pages, I notice that the CopyLink has an older version than the SmartHub version.

How can I upgrade the Pharos PS150 CopyLink version?
The Pharos PS150 CopyLink is not always updated during a standard firmware upgrade. This is normal, and clients should expect their PS150 CopyLink firmware to remain at a different firmware revision than that of the PS150 SmartHub.

We've noticed this problem when the SQL 2K8 doesn't have the latest SP. To work around the problem please apply the latest Service Pack to it and it should resolve the problem.

You get the following error in DebugView on the TaskMaster thread which contains the same error seen in the log file mentioned in the Administrator when looking at the failure log for why this fails.

[3076] [2011/04/29 13:10:15 PC04 T007 i TaskMaster] [PeriodEndLogger.LogInternal] Period End Close Progress = (34) Adding Daily Summaries Data.
[3076] [2011/04/29 13:10:16 PC04 T007 e TaskMaster] Exception...
[3076]
[3076] 1) Exception Information
[3076] =============================================
[3076] Exception Type: System.Data.SqlClient.SqlException
[3076] Errors: System.Data.SqlClient.SqlErrorCollection
[3076] Class: 16
[3076] LineNumber: 1
[3076] Number: 515
[3076] Procedure:
[3076] Server: AB-2K2008-BP4-2
[3076] State: 2
[3076] Source: .Net SqlClient Data Provider
[3076] ErrorCode: -2146232060
[3076] Message: Cannot insert the value NULL into column 'DeviceId', table 'psjobs2.dbo.DailyJobSummary'; column does not allow nulls. INSERT fails.
[3076] The statement has been terminated.
[3076] HelpLink: NULL
[3076]
[3076] StackTrace Information
[3076] =============================================
[3076] at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
[3076] at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
[3076] at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
[3076] at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
[3076] at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
[3076] at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
[3076] at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
[3076] at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
[3076] at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
[3076] at PharosSystems.Library.DataLayer.ExecuteNonQuery(DbCommand command, Int32 commandTimeout)
[3076] at PharosSystems.Library.StoredProc.ExecuteNonQuery(Int32 commandTimeout)
[3076] at PharosSystems.OutputManagement.PeriodEndDataLayer.ExecutePeriodEndClose(PeriodEnd periodEnd, Boolean fullClose, PeriodEndSettings periodEndSettings, SetPeriodEndCloseProgressCallback SetProgress)
[3076] at PharosSystems.OutputManagement.PeriodEndManager.ExecutePeriodEndClose(PeriodEnd& periodEnd, Boolean fullClose, IPeriodEndPlugins periodEndPlugins)
[3076] at PharosSystems.OutputManagement.PeriodEndManager.CloseWorker(Object state)
[3076]
[3076] [2011/04/29 13:10:16 PC04 T007 e TaskMaster] [PeriodEndLogger.LogInternal] An exception occurred: Cannot insert the value NULL into column 'DeviceId', table 'psjobs2.dbo.DailyJobSummary'; column does not allow nulls. INSERT fails.

The recommended image size for background images in themes is 640 x 480 for PS100 Omegas and 800 x 600 for PS150 Omegas.

The attached document details the use and limitations of extended characters in banner template files.

Windows may have blocked the replacement file importer executable from running.

Right click on PharosSystems.Core.FileImporter.exe (found in \Program Files\PharosSystems\Blueprint\bin) and select Properties. If it is blocked, there will be an 'Unblock' button displayed (see attached screenshot).

After unblocking the executable, restart the Pharos Systems ComTaskMaster service & Pharos Systems TaskMaster service.

Can I run the WCF on another port?

NOTE: McAfee has a service that was running called "FrameworkService.exe" which uses the same port as the WCF.

It is possible to run WCF on another port.  Here is what you need to get a working WCF/Remote to run on port 8082:

 

WCF:

 

Change all 8081 -> 8082 in Pharos\Bin\WCF\PS.vNext.SvcHost.WinSvc.exe.config
Restart WCF, confirm listening on 8082 via netstat.

 

Web remote:

 

Change 8081 -> 8082 in wwwroot\Pharos\appSettings.config (only one entry)
Restart IIS, test remote

 

Web Remote does not need EDI to run.  
The WCF service is conceptually like a specialized EDI that is exclusive to Web Remote.

This error message will be displayed if you have accidentally plugged the LAN network cable into the port marked PRINTER on the Omega SmartHub. Remove the LAN network cable from the PRINTER port and plug it into the port marked LAN.

1. Make sure the FTP user has read and write permissions on the upload folder that is located in the Pharos Blueprint directory

2. In other cases, Lexmark software can cause the problem. Run file monitor to find out where the error is occurring. The error will be related to "Inetinfo.exe could not find PCinfo.dll" and it will also look into a strange directory - if possible, delete that directory.

See attached screenshot.

When printing to a Canon Print Queue we recieve the following printing error - “Cannot print because the version of the device controller function is old.  Contact the administrator for details”.

How can I resolve this error?

This was most recently seen when using a Canon imageRUNNER C4080; however, please note that it is not limited in scope to this particular Canon model. This can be resolved by making a change to the Printer Driver configuration, see below for details.

Note: This is an error message produced from an interaction between Windows and the Print Driver and not Pharos. The problem is with the configuration of a setting called "Function" being set to 1.0.

 

1. Go to Printer Properties->Device Settings and click on Function.
2. Set it to 2.0 or later.
3. Click OK to commit the change and close the Properties dialog box.

 

The Omega PS150 and the iMFP series devices do not support Stored Value Card readers.The provided DLL's from our website work only with the Pharos PC Release Station.

Occasionally, the following error message appears during an install:

 

"1603: Error installing Windows Installer engine. A file which needs to be replaced may be held in use. Close all applications and try again."

 

This message is generated by Windows, and can be safely disregarded. Simply click OK to proceed. Blueprint will install successfully.

I recieve the error when trying to Import HR Data or add a new ImportConfig file to the Blueprint Enterprise system.

The message being seen is: Error: "Unable to create an instance of the PharosSystems.Core.EntryInstaller installer type."

The below KB Article is a first place to look at a few settings.
https://pharos.custhelp.com/app/answers/detail/a_id/912/kw/912


Below is a link from a web site to obtain there tool that can be used for Windows Server 2008. From an MSDN Blog below is a lot of information on configuration/setup of the "Details about setup for the .NET Framework 2.0 configuration tool".
http://blogs.msdn.com/b/astebner/archive/2006/01/23/516671.aspx


This msdn blog has a lot of good info in it although I have not gone through the whole thing as I did not need the whole SDK to be installed on my server but hopefully this will help sort out the permissions issue that causes the error.

Please see the attached PDF.

Alphabetical sorting in Blueprint Administrator is not supported for any lists containing Chinese characters.

Problem

When attempting to log into the Konica-Minolta iMFP for Blueprint, users will sometimes get this error:

KM iMFP initialization error

and it will persist until the "Pharos for Konica Minolta" service is restarted on the affected Blueprint server.

Cause

This issue occurs because the "Pharos for Konica Minolta" service starts up before the "Pharos Systems TaskMaster" service, which manages the BniService.svc process referenced in the error message. This usually happens during a restart of the server hosting the services. This will affect all Konica Minolta iMFP versions up through, and including, 1.3.0.

Resolution

To permenantly resolve this problem, the Pharos Konica Minolta service must be configured to depend on the Pharos Systems TaskMaster service.

DISCLAIMER: The following instructions require the use of the Windows Registry Editor. While the instructions have been tested and do not result in any loss of function, editing the Registry has the potential to cause system issues. Please ensure that the Registry key referenced has been backed up prior to making any changes. Pharos Systems International, Inc. and its affiliates may not be held responsible for loss of service caused by any procedure described below.

1. Launch the Windows Registry Editor as an administrator.

2. Browse to HKEY_LOCAL_MACHINE\System\CurrentControlSet\services and then find the PharosforKonicaMinolta key. Select it.

3. Right-click within the right-hand pane of the PharosforKonicaMinolta key and choose New > Multi-String Value.

Editing the Registry - Step 1

4. Name it DependOnService and press the ENTER key on the keyboard.

Editing the Registry - Step 2

5. Double-click this new string value entry to edit it.

6. Type Pharos Systems TaskMaster in the Value data field and click OK.

Edit Registry - Step 3

7. Exit the Registry Editor and restart the Pharos for Konica Minolta service for it to take effect.

BONUS: Users familiar with the command-line "sc.exe" utility may perform this in one quick step. Just make sure that the command prompt is in administrative mode and type:

sc config "PharosforKonicaMinolta" depend = "Pharos Systems TaskMaster"

Testing the Change

To test the change, restart the Blueprint server and attempt a login on a Konica-Minolta device. The login will proceed normally.

To find a specific file on the Omega you need to do the following

 

1. Open a command line prompt on your workstation
2. Telnet to the Omega using the following command "telnet <omega ip address>
3. Logon as root and pharos when prompted
4. Type the following command to find the file "find / -name {<filename>} -print
5. Found files will be displayed on screen.

In the registry, under HKEY_LOCAL_MACHINE\Software\PharosSystems, there are a number of subkeys. If you expand all these out you will find Log subkeys associated with a number of keys. Each of these Log subkeys has a value called TraceLog, which is set to 1 by default. Set each of these to 0 and there will be no more logging from Blueprint. This does not affect the operation of the Tracker in any way.

The recovery mechanism failed to automatically reboot the Omega to fix this failed upgrade. Manually reboot and retry the upgrade - this should fix the problem.

 

To check that the upgrade was successful check that the SmartPAD and CopyLink both have correct version info after an upgrade as shown in Omega Administrator. If they don't then reboot the Omega and retry the firmware upgrade.

Answer:

You get this error message if the Cluster isn't prepared correctly, please follow instructions below to fix it:

1. Remove all resources via the Cluster Manager if any.

2. Create a "Print Spooler" Resource

3. In the "Print Spooler Service" add the 'Message Queuing' resource

4. Open the Properties window of the 'Message Queuing' and add following dependencies:

Physical Disk, Network Name

5. Install Blueprint 4.2 on all nodes and once that is completed bring the Resource offline and add following Generic Service to the resources:

A. Blueprint TaskMaster

1. Dependencies: Physical Disk, Network Name, MSMQ, Spooler, SQL (where appropriate if installed on cluster)

2. Service Name: Pharos Systems TaskMaster

3. Use Network Name: True8

 

B. Blueprint ComTaskMaster

1. Dependencies: Blueprint TaskMaster, Physical Disk, Network Name, Spooler

2. Service Name: Pharos Systems ComTaskMaster

3. Use Network Name: True

 

C. Blueprint Event Log Service

1. Dependencies: Physical Disk, Network Name

2. Service Name: Pharos Systems Event Log Service

3. Use Network Name: True

 

D. Blueprint Job Service

1. Dependencies: Blueprint Event Log Service, Physical Disk, Network Name, Spooler

2. Service Name: Pharos Systems Job Service

3. Use Network Name: True

 

IIS Preparation for Windows Server 20008 Cluster

 

1. Open Internet Information Services (IIS) Manager on the physical node that currently owns the resource group created in the "Cluster Preparation" section on page 57. This will be the node on which the service or application is running.

NOTE: If the Default Website is already in use, create a new website that will be used to host the Blueprint web services.

2. Bind this website to the IP Address that was created in the 'Cluster Preparation' section on page 57 of the Install guide. Please do not bind it to the Node 1 / 2's IP Address. This is the IP Address of the Client Access Point configured when creating the service or application.

Known issue with the Job Service

 

If the Collector is installed in the cluster enviroment, you may get the following error in the Event Viewer for Applications when you start the 'Job Service' service:

 

Service cannot be started. System.Configuration.ConfigurationErrorsException: Invalid element in configuration. The extension name 'webHttp' is not registered in the collection at system.serviceModel/extensions/behaviorExtensions. (c:\program files (x86)\pharossystems\blueprint\bin\pharossystems.blueprint.securerelease.jobservice.exe.Config line 17) at System.Configuration.BaseConfigurationRecord.EvaluateOne(String[] keys, SectionInput input, Boolean isTrusted, FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult) at System.Configuration.BaseConfigurationRecord.Evaluate(FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult, Boolean getLkg, Boolean getRuntimeObject, Object& result, Object& resultRuntimeObject) at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject) at System.Configuration.BaseConfigurationR... "

 

The solution is:

 

1. Open Command prompt as an Admin

2. Go to C:\WINDOWS\Microsoft.NET\Framework\v3.5

3. Run WFServicesReg.exe /c

-------------------------------------------------------------------------------------

 

Please check the attached log file for further details.

The PS60 does not support DDNS so if the printer is configured with DDNS the PS60 will pass it thru to the DDNS server. This can cause confusion as the printers name will be mapped to the PS60 Printer IP Address (default: 192.0.2.2) rather than the LAN IP address that the PS160 has.

The printer must have its DDNS client turned OFF!

This happens when the person collecting the cash logs on using a system administrator account that is not in the Pharos Database as a 'cash collector.'

To rename a Blueprint Collector installed on Microsoft Windows Cluster Services, do the following:

1.     Rename the Cluster Network Name resource to the desired name. Ensure that DNS and Kerberos options are enabled. The resource must be disconnected prior to performing this change.
2.     Bring the Network Name resource back online. Also bring the rest of the dependent services online with the exception of the Pharos services.
3.     Engage a remote desktop session, connecting to the new Network Name specified in Step 1.
4.     Launch the Pharos Blueprint Server Configuration utility. Change the name of the server and Apply. You will get an information message about saving the configuration, but requiring effort on the Cluster Manager side. Continue through this, and close the Configuration utility.
5.     Navigate to the location of the Pharos Blueprint data files (it may be either on the quorum drive or other shared cluster volume). Within the root of the folder, find GlobalConfig.xml and open in Notepad.
6.     Perform a Replace operation, replacing the previous server name with the new server name. Save and close the file.
7.     It may be necessary to recreate the Microsoft Message Queue queues (Blueprint 4.2 and lower). If so, add them as Public Queues.
8.     Connect the Pharos services through Cluster Manager. To test, you may move the group to the other node. All services should start normally.

 

NOTE: If you have Blueprint Tracker clients (workstation-based and/or print server-based) installed as children to the Collector, they will need to be reinstalled to reflect the new server name.

Symptoms

Viewing EDI logs show the same user attempting to login every 5 minutes.

Viewing the on-device debugging logs shows the transaction reaper start then interrupted by an automatic logout.

Viewing the on-device transaction logs shows transactions in the log.

 

Cause
A too frequent auto clear timer setting on a Canon MFP can interfere with the off-line transaction reaper thread causing it to exit prematurely.  This happens before the retry count is incremented so the retry count is always 1.
__________________________________________________________________

How to reproduce:
1.     Set the auto clear timer on the Canon MFP to 20 seconds. (this is for illustration only, other values may also cause the issue)
2.     Login
3.     Start a copy job
4.     Unplug the network cable
5.     Let the job complete.
6.     Wait 15 seconds or so
7.     Plug the network cable in
8.     Logout
9.     Wait about 5 minutes
10.     View the on-device logs and note when the transaction reaper runs and if it completes.
11.     View the on-device transaction cache and determine if off-line transactions still exist
12.     View the EDI logs and not if the user is attempted to login at 5 minute intervals
13.     Repeat 9-12  three more times to ensure the transaction reaper ran at least 15 minutes
14.     If transactions remain, the issue is exhibiting.

 

Note that in step 4, any error could cause the job to fail to commit to Pharos.  Edi server is down, etc.
____________________________________________________________________________


Work Around
1.     Change the auto clear timer to a larger value
2.     Clear the on-device transaction cache.
______________________________________


How to change the auto-clear timer:
1.     You should not need to uninstall the Pharos solution to do this, but you will have to login.  If you find that you can’t change the auto clear timer with Pharos installed perform the following steps
         a.     Login to SMS
         b.     Disable the Pharos Login Service
         c.     Reboot
         d.     Change the auto clear timer
         e.     Login to SMS
         f.     Enable the Pharos Login Service
         g.     Reboot
_______________________________________________


How to Clear the error
1.     Clear the on-device transaction cache
        a.     Browse to http://device.ip:8000/Pharos/Transactions
        b.     CTRL-A
        c.     CTRL-C
        d.     Paste the information for later use
        e.     Press the Clear Transactions button

It is most likely that you have you have used an incorrect user logon or password when updating the HP firmware/software. At present the Pharos HP 4345 software has no way to determine if those details are valid or not.

 

Check that the password and logon name is correct (must be an administrative logon for the HP 4345 printer).

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.

The error "The certficate chain could not be built to a trusted root authority (HRESULT 0x800B010A)" is due to the lack of an authority in the Trusted Root Certification Authorities store for the local computer (in this case, the server upon which the Pharos server software will be installed). An example of this error is found below:

 

 

You may also get this error if attempting to use the certificate as a "Bind" to HTTPS:

 

To resolve this condition, the Pharos Systems root certificate must first be installed on the server. Download the attached "Pharos.cer" certificate to the server and:

  1. Click Start > Run and type "certmgr.msc" (without the quotes).
  2. Expand the Trusted Root Certification Authorities node and select the Certfiicates node underneath.
  3. Right-click the Certificates node and choose All Tasks > Import. Click Next.
  4. Browse the location of the Pharos.cer file. Select it and then click Next.
  5. Select the "Place all certificates in the following store" option and then click the Browse button.
  6. Click in the "Show physical stores" box to check it and expand "Trusted Root Certification Authorities."
  7. Select the "Local Computer" option under Trusted Root Certification Authorities and click OK.
  8. Click Next and continue the import.

 

This should end successfully. At this point, you may start the import of the certificate supplied by Pharos for your installation.

The following Magtek part numbers are associated with Pharos devices and software solutions:

HP - Magtek P/N 21040140 USB Sure Swipe 3 track HID black
Canon - Magtek P/N 21040146 USB Sure Swipe 3 track HID white
PS150 - Magtek P/N 21040145 USB Sure Swipe 3 track Keyboard Emulation black

Attached two text documents to guide the user to migrate the database to another machine.

Notes

IMPORTANT:
1. If the fresh install file directories do not match those on old server then you may need to update FileImporters table to get imports working.
2. If existing Analyst is being used as a Analyst/Collector then some printjob data will be probably be lost during Tracker Uninstall/Reinstall.
3. The supplied directions also work in Blueprint 4.2 (all builds, including the published Hot Fix).

All error messages produced by Omega software are written in plain English. The only exception is when an error occurs in the underlying code, generating a message like:

 

PC9 exception fault.
segmentation fault (client). For firmware versions prior to 1.4.4 (Pencarrow), this error can occur if the Omega terminal's theme version does not match its firmware version. (You can check the version number of themes and firmware using Omega Administrator.)

 

If the theme and firmware version numbers match, then this error may indicate a low-level bug in the Omega terminal. Contact Pharos Support.

If the copier is attached to the Omega SmartHub via a bear EPSV kit through a D15 connector, then the EPSV needs to have dip switch 2 turned on to enable "US Mode". The dip switch is located inside the EPSV kit.

Answer:

Delete the contents of the following directory C:\windows\temp

Please check the attached screen shot for further info.

I am getting an error while configuring the Omega Terminal's PEDI settings

 

After Logging in as Root.. and setting the PEDI configuration, I receive the following error

 

“Invalid Site Code Error”

 

The site code and license information is correct.

 

Why am I receiving this?

 

This error is misleading and has nothing to do with the Customer Site Code. This error will occur if the EDI  Server password is incorrect.

 

The EDI Server password is listed in the Registry at HKEY_LOCAL_MACHINE\SOFTWARE\Pharos\Edi

 

NOTE: This password is case-sensitive

 

To resolve:
Log on to the Omega as root, and set the PEDI password to match exactly the EDI password.
Press the Test Conductivity button again to verify

Brief Overview of Debugging the Blueprint/Uniprint Tracker

 

Main Components

 

The ComTaskMaster is the controlling process. It uses the config file CTskMstr.exe.config. This specifies the list of sub components it should load.
The components lists depend on the type of install. Full Blueprint, Minimal install for Uniprint Popups, or both Blueprint and Uniprint installed.

 

The ProfilerControlTask creates 4 threads.
Page Count, Forward, Update and Network Resolution.
Only the Update thread is used by the Uniprint installation

 

The Update thread scans the list of printers every so often, looking for changes, adds and removals.

 

Uniprint Popups requires the spool files generated by the Profiler. To avoid issues regarding who is responsible for the deletion of the spool files, the Profiler generates two copies of the spool file. One for the ProfilerControlTask/PageCounter the other for the Popup client.
The Profiler handles the renaming of the JobFileName within the PrintJob xml.
The Popup client is responsible for deleting its copy of the spool file, and the Profiler Control Task will either pass the file onto the PageCounter, or will delete the file if it is running a minimal install.
The Profiler places the Uniprint Popups copy of the spool file in the Temp directory under the Uniprint root directory.

 


What to look for in the logs:

 

The ComTaskMaster.log will show the successful loading and starting of all tasks.
For a Uniprint install this is the AppTrackerTask and ProfilerControlTask
For Blueprint this is the ProfilerControlTask, SettingsTask, DistributionTask and StoreNForwardTask.

 

The PrintProfiler shows the enumerating of the installed printers, and whether they have been successfully hooked or unhooked.

 

The ProfilerControlTask will show the starting of its threads. (only the CUpdateThread for a minimal install)
For a Uniprint only install, the line:

 

“Blueprint components not installed, running in Minimal Uniprint Installation mode”

 

should appear in the ProfilerControlTask log

 


On printing a job:

 

The PrintProfiler will make calls such as PP::StartDocPrinter and PP::StartDocPrinterHdlrB. The exact calls will depend on the print path, but should indicate that the profiler has begun the capture of the document.

 

There will be a call to SPrintInfo::LogJobStart. This will retrieve a handle to the ProfilerControlTask, via the ComTaskMaster. The RetrieveTask lines should appear in the ComTaskMaster log

 

The ProfilerControlTask will call CXmlLogger::LogPrintJobStart.  At this point the Popup client is called, and it talks to the popup server to find out if there are any questions to ask the patron.  It then asks the questions, collects the answers, and stores them until the print job is completed.

 

You should see the xml of the PrintJob, and the LogicalPrinter. The information is not complete at this stage.

 

The print job will be printed, and the profiler will capture it. You may see various PM::WritePort calls being made here.

 

You will see the Profiler make calls such as PP::EndDocPrinterHdlrA and PP::EndDocPrinterHdlrB, again depending on the print path.
Then again via the ComTaskMaster to the ProfilerControlTask, you will see CXmlLogger::LogPrintJobEnd, and the Xml for the PrintJob

 

The ProfilerControlTask receives the xml, validates it, processes logical printer information, resolves printer GUIDs, network info, persists the logical printer in the logical printer store, and delivers the printjob to the PageCount store.

 

For a Uniprint install, the following lines should appear in the Profiler log.
“Calling PopupLogger LogPrintJobEnd”. 
“Copying spool file to 'C:\Program Files\Pharos\Temp\PSP00839.SPL' for Popups Logger”
“Logged job end”

 

This makes the call to the Popups client. The spool file should be at the location indicated. At this point, the Uniprint popup contacts the LPD server and sends the answers that were collected at the LogPrintJobStart event and the spool file to the print server.

 

The PageCounter (if running) picks up the print job from its store, processes the spool file, and posts the print job into the Outbound Jobs store.

 

The StoreNForward task (if running) sends jobs in batches from the Outbound Jobs store to the Blueprint Collector, or Analyst.

It is most likely that the EDI settings you entered during installation are incorrect. You need to make sure these are correct and update the machine.

 

It is also possible that the EDI is not currently started. You need to make sure that the Pharos EDI Service on the Pharos server is started.

The "...no more endpoints available for the endpoint mapper" error indicates either a name resolution or other networking problem. Frequently, this is caused by inappropriate management of the Windows Firewall in the operating system. In many cases, it is not an issue to have the Windows Firewall enabled as long as the necessary Pharos ports are "white listed" or enabled. If the Windows Firewall is to be disabled, however, it is best to accomplish this using Group Policy (see the Microsoft TechNet article at http://technet.microsoft.com/en-us/library/bb490626.aspx) when in a domain environment. Alternately, use the most appropriate method available within another Microsoft TechNet article, found at http://technet.microsoft.com/en-us/library/cc766337(WS.10).aspx.

Again, in previous versions of the Windows Server operating system (notably Windows Server 2003), one could simply disable the Windows Firewall service. This is not the supported method in Windows Server 2008. This, from "I Need to Disable Windows Firewall" (http://technet.microsoft.com/en-us/library/cc766337(WS.10).aspx):

 

CautionCaution
Do not disable Windows Firewall by stopping the service. Instead, use one of the preceding procedures (or an equivalent Group Policy setting) to turn the firewall off. If you turn off the Windows Firewall with Advanced Security service, you lose other benefits provided by the service, such as the ability to use Internet Protocol security (IPsec) connection security rules, Windows Service Hardening, and network protection from attacks that employ network fingerprinting. For more information about Windows Service Hardening, see http://go.microsoft.com/fwlink/?linkid=104976http://go.microsoft.com/fwlink/?linkid=104976. Non-Microsoft firewall software that is compatible with Windows Vista and Windows Server 2008 can programmatically disable only the parts of Windows Firewall with Advanced Security that need to be disabled for compatibility. You should not disable the firewall yourself for this purpose. Stopping the service associated with Windows Firewall with Advanced Security is not supported by Microsoft.

Pharos does not provide sample EULA documents for distribution with the packages as this is a legal document that is between the site and the end user.

The Pharos services by default run as LocalSystem. This account uses the Default User profile, so changes made while logged in as another user will not affect the services. The Default User profile can be adjusted by following these steps in the Regional and Language Options control panel applet, after you have made the required changes:

  • For Windows 2003 Server:
    1. Select the Adminstrative tab.
    2. Enable the 'Apply all settings...' checkbox and click OK.
    3. Restart the Pharos Print Server service.
  • For Windows 2008 Server:
    1. Select the Administrative tab.
    2. Click 'Copy to Reserved Accounts'.
    3. Enable the checkbox for System Accounts and click OK.
    4. Restart the Pharos Print Server service.

Since the Magtek Reader is working on the PC Release Station that would mean it is set up for Keyboard Emulation.

In order for it to work properly with the HP iMFP it would need to be set up for HID Mode.

You can change the configuration by plugging the card reader into a computer, and navigating to this webpage:

Magtek Online Card Reader Configuration

  1. Create the SharpAppPool as described in the Sharp iMFP documentation
  2. Right click on the new application pool and select "Advanced Settings"
  3. Scroll down to Process Model\Idle Time-out (minutes) and set it to 0
  4. Scroll down to Recycling\Regular Time Interval (minutes) and set that to 0
  5. Click OK

Sharp App Pool for IIS 7

When I try to print to our Pharos Server, from the client's computer I can't print, it says it can't talk to the server.  If I add our domain to their DNS Suffix, it works.  What steps can I take to resolve this issue by either configuring the Pharos Popup Package to use FQDN of the server or the servers IP Address?

The Pharos Popup Package gets built from whatever server name is used in the Pharos Administrator > System > Server Configuration > Host Name.  More than likely, you have the simple name there, and also in the Pharos database.  You can confirm this by going into SQL Server Management Studio and executing the below SQL query.

use pharos
select * from servers

 

Take the information you find in the database, and create a REG_SZ key in the registry named MachineName under 'HKEY_LOCAL_MACHINE\SOFTWARE\Pharos' and add the value you found from the DB query, which is more than likely the short name.

NOTE: On a 64-bit server, use the Registry path 'HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Pharos' or the edit will not work.

 

You can then go into Pharos Administrator and change the Host Name value to the FQDN.  From this point on, all installed packages will use the FQDN rather than the short name for resolution.

Banner page will not print as intended, fails at _UNP_JOBNAME_.

No further variables are showing after _UNP_JOBNAME_.

PROBLEM:

If a single parenthesis is present in the filename of a print job, the banner page will not print as intended. This happens if you are using a single open or closed parenthesis in the filename of the job. It will process the job but will not output the remainder of the banner page after the _UNP_JOBNAME_ variable. This is due to postscript rendering of the raw postscript file as it encounters a single parenthesis in the filename while it then looks for a closing argument or closing parenthesis. When this closing argument is not found the parsing of the raw job fails to finish rendering the remainder of the banner template variables correctly.

RESOLUTION:

There is currently no known solution for this problem. It will be addressed in a later version. The method to work around this would be to omit any single parentheses in the filename of the print job or include open and closed parentheses in pairs.


Filename Examples:

test(doc.txt or test)doc(.txt = will fail the remainder of the banner page template

test()doc.txt or test(doc).txt = will not fail

*ColorDevice: False
*DefaultColorSpace: Gray
*VariablePaperSize: True
*LandscapeOrientation: Plus90

 

updfate 2 lines as follows:

 

*ColorDevice: True
*DefaultColorSpace: CMYK

 


*CloseUI: *FXOutputMode
*OpenUI *FXColorMode/Output Color:PickOne
*OrderDependency: 20.0 AnySetup *FXColorMode
*DefaultFXColorMode: Color
*FXColorMode Color/Color: "
  1 dict dup /ProcessColorModel /DeviceCMYK put setpagedevice
"

 

Update 3 lines as follows:

 

*DefaultFXColorMode: Black
*FXColorMode Black/Black: "
  1 dict dup /ProcessColorModel /DeviceGray put setpagedevice
"

 


Some PPD Files the Black and White option may be called MONO, not GRAY as shown in the example

 

By making this adjustments users won't be able to print in color to the BW printer queue.
(two queue setup required)

Attached is a document explaining the process

PS200 terminal:

The cables are 1.5 m (3.28 ft) long
The outside dim of 7 inch display is 200 mm (7.87 inches) x 150 mm (5.91 inches)
Typical desktop footprint is 200 mm (7.87 inches) by 130 mm(5.12 inches)
The actual terminal weight on desktop: 850 g (1.9 lbs)

The HP 4345 can hang if using cost centers that have more then one level with cost center constraints enabled. If one of the cost centers from the first level doesn’t have cost centers selected in the “Relation to next category” field, when the user selects that cost center on the HP4345 it will hang.

 

To solve this problem please make sure that the “Relation to next category” field is populated, if cost center constraints are used.

How do I serial flash a Pharos Omega PS100?

 

NOTE: Internal information only, by sending this information to any customer they have automatically consented to void their warranty. The following instructions detail the setup and commands needed to serial re-flash a Pharos Omega PS100 unit.

 

1. Un-screw the four silver screws that hold the top of the Pharos PS100 Smart Hub on using a philips screwdriver.
2. On top of the main PS100 Smarthub you should see a serial port
3. Using a serial nullmodem cable attach the cable to the serial port on the smarthub and the other end into a serial port on the laptop or computer
4. Attach a cross over cable between the computer/laptop ethernet port and the first ethernet port on the Smarthub
5. Open a command window and type the following command

 

omega reflash --mac 0014fc COM4 firmware.img

 

Where the --mac option is the last 6 values from the side of the Omega Hub (0014fc in this example).

 

6. The unit should begin the re-flash process, when complete the command line will read "1" and complete
7. Dettach the unit and replace the top
8. Restart the unit

Solution:

Re-install the IPBiller and the error should stop.

1. Rename the attached txt file to .reg.
2. Copy the .reg file to the Pharos Print Server.
3. Double click on the registry file to insert on the server.
4. Restart the Pharos Print Service.
5. Logging will begin on the server for the Print Service. As soon as the service fails capture the logs and send them directly to support.

Using a non-supported PDL, hence the Page Counter fails.

 

Found the driver information here: http://www.usa.canon.com/html/download/imageclassc2500.html. Canon don't seem to be supplying anything other than the CAPT drivers. Request the latest Page Counter from Pharos Support.

Request the latest Page Counter from Pharos Support.

Steps for manually upgrading Blueprint Analyst databases from 3.5 to 3.5 SP1
============================================================================
The following instructions explain how to manually upgrade the Blueprint Analyst databases.

 

A manual upgrade of the Blueprint Analyst databases will be required if the original install was to a remote database, with the databases hosted on SQL Server running on a separate machine from the other Blueprint components. The remote database will typically have been installed manually when Blueprint was originally installed.

 

These instructions apply to the manual upgrade of the Blueprint Analyst databases from 3.5 to 3.5 SP1
All the files required to carry out a manual upgrade of the databases are available in the 3.5 SP1 under ".\Program Files\PharosSystems\Blueprint\Database\MSSQL"

 

Preparation
-----------
1. In the Services Control Manager, stop the Pharos Systems TaskMaster and Pharos Systems TaskMaster Watchdog services.
2. Close all copies of the Blueprint Administrator connected to the Blueprint Analyst databases.
3. Backup the Blueprint Analyst databases, by executing the "Pharos Blueprint Database Backup" SQL Server Agent job through SQL Server Management Studio. Copy the resulting backup files to a secure location.

 

Database Upgrade
----------------
1. Upgrade psbprocs database.
This step detaches and then re-attaches a new copy of the psbprocs database and will require either the "sa" or a Windows Administrator account

 

Using SQL Management Studio open and execute contents of the file .\Common\UpgradeDetachProcsDB.sql against the master database. This detaches the existing psbprocs database from the SQL Server.

 

Copy the new psbprocs.mdf and psbprocs.ldf files from CD to the server.
The files should be copied from the CD from either .\Analyst\SQL2000 or .\Analyst\SQL2005, depending on the SQL Server version and should be copied to the same location as the old psbprocs database files, first copying the old files to the same secure location as the database backup files.

 

The Database files are located under the following directory in BluePrint 3.5
C:\Program Files\PharosSystems\Blueprint\Data

 

Using SQL Management Studio open the file .\Common\UpgradeAttachProcsDB.sql and connect to the master database.
Edit this file replacing the parameter placeholders with the Blueprint SQL logon and the location of the psbprocs database files.
For example
    set @Logon                            = N'||SQLLogonName||'
    set @MainDataFileFolder    = N'||MainDatabaseDataFileFolder||'
    set @MainLogFileFolder      = N'||MainDatabaseLogFileFolder||'

 

would updated as follows, if the SQL logon was "psbprint" and the file location was  "C:\Program Files\PharosSystems\Blueprint\Data "
    set @Logon                           = N'psbprint'
    set @MainDataFileFolder   = N' C:\Program Files\PharosSystems\Blueprint\Data’
    set @MainLogFileFolder     = N' C:\Program Files\PharosSystems\Blueprint\Data'

 

Execute this script to attach the new psbprocs database.

 

2. Upgrade the partition databases psjobs[1..N]
This step updates the schema in each of the psjobs databases and can be carried out using the Blueprint SQL logon account, the "sa" or a Windows Administrator account.

 

Using SQL Management Studio open and execute contents of the file .\Analyst\UpgradePartitionHead.sql against the psjobs1 database.

 

Depending on the volume of data in the database this script may take a few minutes to run.

 

Using SQL Management Studio open and execute contents of the file .\Analyst\UpgradePartitionTail.sql against the psjobs1 database.

 

Repeat the above steps for each of the partition databases psjobs[1..N].

 


3. Upgrade the main psbprint database
This step updates the schema in the main psbprint database and can be carried out using the Blueprint SQL logon account, the "sa" or a Windows Administrator account.

 

Using SQL Management Studio open and execute contents of the file .\Analyst\UpgradeAnalystHead.sql against the psbprint database.

 

Using SQL Management Studio open and execute contents of the file .\Analyst\UpgradeAnalyst4685.sql against the psbprint database.

 

Depending on the volume of data in the database this script may take a few minutes to run.

 

Using SQL Management Studio open and execute contents of the file .\Analyst\UpgradeAnalystTail.sql against the psbprint database.
This completes the manual upgrade of the database.

 


The Blueprint Analyst components can now be upgraded using the 3.5 SP1 Installers.
The Pharos Systems TaskMaster service will not restart cleanly until it has been upgraded.

 

To check if the database has been upgraded successfully run the following query:
select * from databaseversion against psbprint it should return 4685 as the BuildNumber.

When I run the uninstaller I get an error message about being unable to find a file called "osql.exe", similar to this: "Windows cannot find 'C:\PROGRA~1\Pharos\Bin\osql.exe'. Make sure you typed the name correctly, and then try again."

After this, another error is produced, and the uninstaller reports a failure. Some components may be removed, but the database still exists.

CAUSE

This error occurs because of a defect in the uninstaller program.  osql.exe is a program used for connecting to databases, and comes with Microsoft SQL Server.  Depending on your configuration, the Uniprint Installer may or may not install a copy of osql.exe within the Pharos installation directory.  The uninstaller checks the configuration to determine whether to expect to find osql.exe in the Pharos installation directory; but due to a defect it does so incorrectly, and consequently incorrectly expects to find the file there.  This error generally occurs if any letters in the computer's name are in lower case.

SOLUTION

The solution to this problem depends on whether Pharos Database Server was been uninstalled at the time when the problem is discovered.  To discover whether it is still present, dismiss any message boxes the uninstaller raises; restart the computer if the uninstaller requests a restart; and start the uninstaller again and check whether Pharos Database Server is in the list of components that can be uninstalled.

If Pharos Database Server is still present after the problem is encountered (or is still present because you already know about the problem and haven't started uninstalling), find the file osql.exe on the computer's hard drive.  This will generally be located in the directory where Microsoft SQL Server is installed.  Copy this file into the "bin" directory within the Pharos installation directory, then run the uninstaller, and it will uninstall the Pharos Database without encountering the error.

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

The Blueprint Enterprise Collector cannot communicate with the Analyst. It is not retrieving the license file or other configuration information. In the Taskmaster log file on the Collector, this message is found:

"The requested upgrade is not supported by 'net.tcp://servername.domain.com/PharosSystems/Blueprint/Services/HealthMonitoringService.svc'. This could be due to mismatched bindings (for example security enabled on the client and not on the server).

The file global.serviceModel.bindings.config, found in the Program Files\PharosSystems\Blueprint\bin, maintains the communications structure for all inter-process WCF (Windows Communication Foundation) events in Pharos Blueprint. This includes communications between Pharos services on the same server, communications between Pharos servers, and communications between client tools (like Pharos Blueprint Administrator) and servers.

Opening the global.serviceModel.bindings.config file will show several XML tags for <security mode= .../>. Each communications binding has its own security mode setting, and if there is a mismatch between end-points, it will fail. One way to maintain parity is to copy the contents of the file (not the actual file, but the data inside; Notepad will open the file just fine) from one server and then paste it into the file (replacing everything already there) of the other server. Save it, reset IIS (iisreset in an administrative command prompt), ad then restart all Pharos services.

If this continues to fail, check DNS to make sure that the <servername> specified in the message can be PINGed, reached via UNC (a file share, for example), or otherwise accessed by the name of the server.

This is a currently bug in the system that when a device has more than 500 Transactions it fails to Archive it and it's associated Transactions.

 

You can try to run it until it finally Archives the device as it will Archive 500 Transactions at a time so if the device has 4,000 Transactions then you would have to run it 9 times and either the 9th or 10th it will purge the device.

 

Once a fix has been released we will update this KB Article.

Steps for manually upgrading Blueprint Analyst databases from 4.1 to 4.2 ============================================================================
The following instructions explain how to manually upgrade the Blueprint Analyst databases.

 

A manual upgrade of the Blueprint Analyst databases will be required if the original install was to a remote database, with the databases hosted on SQL Server running on a separate machine from the other Blueprint components. The remote database will typically have been installed manually when Blueprint was originally installed.

 

These instructions apply to the manual upgrade of the Blueprint Analyst databases from 4.1 to 4.2

All the files required to carry out a manual upgrade of the databases are available in the 4.2 under ".\Program Files\PharosSystems\Blueprint\Database\MSSQL"

 

Preparation
-----------
1. In the Services Control Manager, stop the Pharos Systems TaskMaster and Pharos Systems TaskMaster Watchdog services.
2. Close all copies of the Blueprint Administrator connected to the Blueprint Analyst databases.
3. Backup the Blueprint Analyst databases, by executing the "Pharos Blueprint Database Backup" SQL Server Agent job through SQL Server Management Studio. Copy the resulting backup files to a secure location.

 

Database Upgrade
----------------
1. Upgrade the partition databases psjobs[1..N]
This step updates the schema in each of the psjobs databases and can be carried out using the Blueprint SQL logon account, the "sa" or a Windows Administrator account.

 

Using SQL Management Studio open and execute contents of the file .\Analyst\UpgradePartitionHead.sql against the psjobs1 database.

 

Depending on the volume of data in the database this script may take a few minutes to run.

 

Using SQL Management Studio open and execute contents of the file .\Analyst\ UpgradePartition5586.sql against the psjobs1 database.

 

Using SQL Management Studio open and execute contents of the file .\Analyst\UpgradePartitionTail.sql against the psjobs1 database.

 

Repeat the above steps for each of the partition databases psjobs[1..N].

 


2. Upgrade the main psbprint database
This step updates the schema in the main psbprint database and can be carried out using the Blueprint SQL logon account, the "sa" or a Windows Administrator account.

 

Using SQL Management Studio open and execute contents of the file .\Analyst\UpgradeAnalystHead.sql against the psbprint database.

 

Using SQL Management Studio open and execute contents of the file .\Analyst\UpgradeAnalyst5586.sql against the psbprint database.

 

Depending on the volume of data in the database this script may take a few minutes to run.

 

Using SQL Management Studio open and execute contents of the file .\Analyst\UpgradeAnalystTail.sql against the psbprint database.
This completes the manual upgrade of the database.

 


The Blueprint Analyst components can now be upgraded using the 4.2 Installers.
The Pharos Systems TaskMaster service will not restart cleanly until it has been upgraded.

 

To check if the database has been upgraded successfully run the following query:
select * from databaseversion against psbprint it should return 5586 as the BuildNumber.

The Copy Line Configuration for the Device has not been configured is most likely the root cause.
Open the Pharos Administrator and navigate to the Devices context, Output Management > Devices. Select the Device in question, and expand the "Copier" section below. Configure the "Copy Line Configuration" with needed copy lines. Typically these start at 0 and increment upwards, see attached screen shot 'CopyLines-v2'.


Platform: Ricoh iMFP
When I swipe my card at our MP C4500 I get the following error:  “VAS handle get err”.


Solution:

 

The Ricohg iMFP does not have the proper system firmware installed on the device. Some models of Ricoh iMFP's require customized system firmware to be loaded on the device for the Pharos iMFP solution to function.

Install the proper system firmware for your device as outlined in the Pharos iMFP for Ricoh Installation and Configuration Guide.

There are bugs in the PS150 2.0.1 network linkup code and the Xerox MFP (286 and DC320 in the PHAROS NZ office)

 

If the Xerox MFD starts up on a dead LAN port the Xerox auto-negotiate link up creates a default of 10 Mbit half-duplex. If the PS150 is then powered up, the PS150 Ethernet port links up into a bad state that floods the LAN with lots of packets. Set Xerox MFD LAN to 100 Mbit half-duplex.

 

Future 2.1 release stops flooding network but still links up to a slow speed of 10 half-duplex. We will still recommend configuring Xerox LAN to 100 Mbit half-duplex.

The Canon iMFP has the ability, if it loses communications with its specified Pharos EDI server, to store transactions locally until such time as the connection is re-established. This will cause the device to refuse any other activity (copy, scan, fax or secure print) until this has finished. If the software is unable to do so (for example, if using Pharos Blueprint Enterprise), this can cause the MFP to be completely unavailable. This was particularly a problem in earlier versions (previous to firmware version 2.5.1) of the Canon iMFP software. Below follows some steps to resolve the situation. All utilities mentioned can be found in the attached "txGrabber.rar" file.

 

1.     Manually check each engine for transactions
     a.     Browse to http://ip.address.of.device:8000/Pharos/Transactions
     b.     If there are transactions
          i.     Wait 5 minutes then view again
          ii.     If the transactions remain, these could be “stuck”
          iii.     Clear the transactions by pressing the Clear transactions button.

 

2.     Automatically check each engine for transactions
     a.     The attached curl_test.bat and curl.exe utility will do this for you.
     b.     You’ll need to modify the script to handle each IP address
     c.     Note that the line that actually clears the transaction is commented out
          i.     This is on purpose to allow all the devices to be queried but not modified.
     d.     Make sure to put each set of transactions in a separate XML file.
     e.     Check the file contents
          i.     If it’s empty, no transactions

 

3.     Automatically purge the transactions from the engine.
     a.     You need Java installed to do this.
     b.     Use the files ip_XXX.txt, process_ip_addresses, get_log_for_ip.bat, and TransactionCollector.jar
          i.     Modify ip_xxx.txt to include all the ip addresses you want to check
          ii.     Call process_ip_addresses ip_xxx.txt to get the process started.
          iii.     Note the line that actually clears the transactions is commented out
               1.     This is on purpose for testing before committing to destroying data

 

4.     Update the Pharos iMFP for Canon software on the devices.
     a.     Verify the version of Canon software running on the MFPs.
     b.     Contact Pharos Technical Support for the latest Canon iMFP firmware.

This warning occurs when a user runs out of money while copying, and the HP had to debit the user in “offline mode”. This is just a warning - the transaction will be posted correctly in Uniprint and the user will be debited.

 

Make sure current release of the HP 4345 Pharos software is installed.

Manually remove the 9x Popups for Uniprint 6.0 using the following commands:

 

1. Open the registry and locate the following key:

 

HKEY_LOCAL_MACHINE\Software\Pharos

 

2. Delete the entire registry key entry.

 

3. In the registry locate the following key:

 

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Environments\Windows 4.0\Print Processors

 

Remove the Uniprint Print Processor entry in the list.

 

4. In the registry locate each of the printer entries and change the print processor to "WinPrint".

 

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Printers

 

Change the Print Processor to "WinPrint".

 

5. Exit the registry and reboot the machine.

 

6. Upon restart access remove the following file:

 

\windows\system\unpcp95.dll

 

7. Reboot the machine and reinstall the Popup Client application.

Notes on the behavior of the SmartHub LEDs
---

 

Red/Green LEDs: the boot process
~~~

 

As early as possible in the boot process, the strap turns the red led
on to indicate that the SmartHub is successfully executing
instructions from flash.  This won't be visible to normal life forms,
because it is almost immediately turned off when the kernel loader
begins executing.  However, if for some reason the loader is not
started (e.g. because of an infinite loop or bad branch instruction in
the strap), the red led will stay lit indefinitely.

 

If the strap fails to find a valid kernel at the start or end of
SmartHub flash, it will signal the error by pulsing the red led as per
the description below.

 

As already noted, when the loader starts executing, the first thing it
does is turn the red led off.  At this point it also turns the green
led on to indicate that loader code is being executed from flash.  The
green led will then 'dip' (switch off briefly) up to 3 times to
indicate loader progress.  The number of dips indicates the following
boot-phase milestones:

 

    [1]  RAM initialization succeeded
    [2]  RAM-targeted loader launched successfully
    [3]  About to launch the executable Linux kernel image

 

The green led subsequently stays lit until the Omega is rebooted.

 

Startup error states are signaled by pulsing the red led a number of
times equal to the error code number, pausing, then repeating ad
infinitum.  For example, a generic kernel loader error (code 2) will
look something like (where '!' = red led pulse):

 

        ! !  (pause)  ! !  (pause)  ! !  (pause)  ! !  ....

 

The error code numbers are:

 

    [1]  Strap failed to find a valid kernel.
    [2]  Generic kernel loader error (view the serial log for more detail).
    [3]  Serial transmit failed.

 


Ethernet LEDs
~~~

 

The yellow led is controlled autonomously by the AX88796 ethernet
chip.  It is lit when the chip detects a network layer link, and it
toggles periodically to indicate network activity.

 

The green led is controlled by software running on the SmartHub.  The
code to control the green ethernet leds has not yet been written, so
they can be ignored for the moment.
Notes on the behavior of the SmartHub LEDs
---

 

Red/Green LEDs: the boot process
~~~

 

As early as possible in the boot process, the strap turns the red led
on to indicate that the SmartHub is successfully executing
instructions from flash.  This won't be visible to normal life forms,
because it is almost immediately turned off when the kernel loader
begins executing.  However, if for some reason the loader is not
started (e.g. because of an infinite loop or bad branch instruction in
the strap), the red led will stay lit indefinitely.

 

If the strap fails to find a valid kernel at the start or end of
SmartHub flash, it will signal the error by pulsing the red led as per
the description below.

 

As already noted, when the loader starts executing, the first thing it
does is turn the red led off.  At this point it also turns the green
led on to indicate that loader code is being executed from flash.  The
green led will then 'dip' (switch off briefly) up to 3 times to
indicate loader progress.  The number of dips indicates the following
boot-phase milestones:

 

    [1]  RAM initialization succeeded
    [2]  RAM-targeted loader launched successfully
    [3]  About to launch the executable Linux kernel image

 

The green led subsequently stays lit until the Omega is rebooted.

 

Startup error states are signaled by pulsing the red led a number of
times equal to the error code number, pausing, then repeating ad
infinitum.  For example, a generic kernel loader error (code 2) will
look something like (where '!' = red led pulse):

 

        ! !  (pause)  ! !  (pause)  ! !  (pause)  ! !  ....

 

The error code numbers are:

 

    [1]  Strap failed to find a valid kernel.
    [2]  Generic kernel loader error (view the serial log for more detail).
    [3]  Serial transmit failed.

 


Ethernet LEDs
~~~

 

The yellow led is controlled autonomously by the AX88796 ethernet
chip.  It is lit when the chip detects a network layer link, and it
toggles periodically to indicate network activity.

 

The green led is controlled by software running on the SmartHub.  The
code to control the green ethernet leds has not yet been written, so
they can be ignored for the moment.


When trying to make more than one copy, user is 'Advance' in the Pharos Databse and has plenty of funds for the copy job we see the following error "No Job to cancel, User has run out of money terminating session." and the job stops after a single copy. Users with accounts set to 'Arrears' in the Pharos Database work fine.

 

 


The "Letter" page attribute is not defined as a page attribute for copying in the Job Cost Method. Once you add this as an attribute to the JCM (Job Cost Method), adjust copy control lines are not set to N/A for the device and re-test copying.

If this does not resolve the issue please contact support@pharos.com

Issue:

When attempting to reinstall BPE 5.0 Analyst on a server and both the operational and data warehouse databases exist, the installers will display an Invalid Install Settings dialogue, after the SQL Server hosting the data warehouse has been configured, indicating that "The operational database is already installed."

Scenario:

The server hosting the BPE 5.0 Analyst services suffers a failure or the services need to be migrated to new hardware, requiring the BPE 5.0 Analyst components to be re-installed. The operational and data warehouse databases are either hosted on a remote SQL server not affected by the change to the Analyst server or have been restored from backup to a local SQL Server instance.

The existence of the data warehouse database will prevent the BPE 5.0 installers from re-installing the Analyst services.

To work around this issue it is necessary to temporarily re-name the data warehouse database and remove the existing data warehouse backup job created during the original install. This is to allow a fresh copy of the data warehouse database to be created by the installers, which is removed once the re-install has completed successfully.

Using SQL Management Studio

  • Connect to the SQL Server hosting the data warehouse database and expand the Databases context to display the list of hosted databases. Right click on the data warehouse database "psreports" and temporarily rename it "tmp_psreports"
  • Expand the SQL Server Agent -> Jobs context to display the list jobs configured on the server. Right click on the job named "Pharos Blueprint Data Warehouse Backup" and delete it.

The installers can now be run to re-install the BPE 5.0 Analyst, selecting "Install on an existing database" for the operational database as before. When configuring the SQL Server for the data warehouse database:

  • Select whether the SQL Server hosting the data warehouse is local or remote.
  • If the data warehouse was originally installed on a remote SQL Server, select remote and then enter the name of the SQL Server where it was installed, together with credentials that have permission to create the database.
  • When asked for the location of the data warehouse database files, enter a temporary file location, different to the location where original data warehouse database files were installed.
  • Lastly, when asked for the details of database user to access the data warehouse database, enter the same User ID and Password details that were entered during original install.

The re-install should now proceed successfully, but will create a fresh copy of the data warehouse database. After the re-install has completed, use SQL Management Studio to restore the original data warehouse database:

  • Connect to the SQL Server hosting the data warehouse. Right click on the newly created data warehouse database "psreports" and delete it, checking the "Close existing connections" option.
  • Right click on the original data warehouse database "tmp_psreports" and rename it back to "psreports".

Re-run the Blueprint Server Configuration tool, checking that the database connection tests for both the operational and data warehouse databases pass successfully.

OS:

Windows Server 2008, Windows Server 2008 x64

Symptom:

The 'Tracker Web Service' and/or 'EDI Web Service' health tests fail with a '403: Forbidden' error. Trackers can fail to send job data and terminals can fail to login due to this error. Re-applying the Server Configuration settings does not fix the problem.

 

Possible Cause:

This can be caused by certain permission settings being modified manually using the IIS 7 management console. Specifically, changing the 'Feature Permissions' of the 'Handler Mappings' for a Blueprint virtual directory and removing either the 'Read' or 'Script' permissions will cause this.

If the relevant 'web.config' file (located in the Blueprint 'Services\BediService' and 'Services\TrackerService' subdirectories) contains the following section:

<system.webServer>

...

</system.webServer>

Then this indicates manual configuration changes have been made.

 

 

 

Fix:

Either:

1) Reverse the manual changes made.

2) Remove the entire <system.webServer> section from the relevant 'web.config' file.

The Blueprint Tracker Diagnostics tool, DiagTool.exe is located in the PharosSystems\Blueprint\bin directory. The tool must be run from the command line. The following options can be specified:

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

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

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

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

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

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

Report Tracker Status
DiagTool /Status
This command line option will output the current status of the Print Tracker, displaying the following:

  • Application installation path
  • Application Data path
  • Tracker component version number
  • Profiler Installed registry key
  • Profiler Enabled registry key
  • Profiler Faulted registry key
  • Counts of the number of files in each of the file Stores

Diagnostic Start Menu Shortcuts

When the tracker is installed on a server, four links are created in the Start Menu under Pharos Blueprint Emterprise > Tracker:

  • Enable Tracker
  • Disable Tracker
  • Enable Tracker Debug Logging
  • Disable Tracker Debug Logging

These links duplicate the function of the /InstallProfiler, /UninstallProfiler, /LoggingOn and /LoggingOff options respectively.

Problem

When installing the Pharos Analyst software, installation progresses well, but I get an "Assembly install Error" dialog (see "AssemblyInstallError.jpg" below) just when the install wizard is in the "Updating data" status.

Assembly install error

When I go to the C:\ProgramData\PharosSystems\Blueprint\Logs directory, the CreateAnalystDatabase.sql.log file shows this error:

"Msg 50000, Level 16, State 127, Server BPE50, Line 206

Error creating database: The CREATE DATABASE statement failed. The primary file must be at least "X" MB to accommodate a copy of the model database." ("X" is any number, and indicates file size, in megabytes).

And the installation rolls back. Why? And how can I fix it?

Cause

The "initial size" of the databases created during installation are less than the initial size required by the SQL Server hosting the database.

Background

Blueprint Analyst installer utilizes information collected during the wizard and from within the license file to determine the "initial size" of the various databases that are created during installation. From a SQL Server standpoint, the initial size of any database is usually equal to the minimum hard disk space required to support the database and its application without requiring immediate growth.

Resolution

The minimum initial size of any newly-created database is controlled by the initial size of the SQL Server-built "model" database's data file. In SQL Server 2005, 2008, and 2008 R2, the initial size of the "model" database is around 1.3MB, which usually ends up rounding to 2MB. However, this can be changed very easily to a higher (although not lower) number, and can cause our installation to fail with the error message above. The value for "MB" in the message will reflect the initial size of the "model" database file.

The problem can be resolved by temporarily (or permanently, depending on the site's requirements) reducing the initial size of the "model" data file to something smaller, like 10 MB. To do this:

1. Launch the Microsoft SQL Server Management Studio application, connect to the database server, and log in as an account that has SYSADMIN permissions.

2. Expand Databases > System Databases.

3. Right-click the "model" database and choose Properties (see "InitSizeStep1.jpg" below).

Properties of Model database

4. Click the "Files" page. Note that the Initial Size specified for the "modeldev" file will equal the value shown in the Create Analyst error message (see "InitSizeStep2.jpg" below).

Viewing the data file initial size

5. Click inside the Initial Size field and change it to 10 (see "InitSizeStep3.jpg" below).

Changed initial size

6. Click the OK button.

After a brief pause, the main Microsoft SQL Server Management Studio interface will be returned. At this point, it is safe to exit this application and re-install Pharos Blueprint Analyst. In most cases, the initial size of the Blueprint databases is 100 MB, which will exceed the 10 specified for the "model" database.

User cannot get the Blueprint Administrator or Blueprint Server Configuration utility to launch and/or operate correctly. There are also several messages about the Health Check not completing in the Taskmaster log. Tasks that rely on TCP port sharing (such as Health Check) may also fail.
The problem stems from an error with the SMSvcHost 3.0.0.0 module. This module is responsible for the Microsoft WCF TCP port sharing function used by the Blueprint services. In looking in the System Event Log, the system error thrown by SMSvcHost 3.0.0.0 is listed as the following:

 

An error occurred while dispatching a duplicated socket: this handle is now leaked in the process.
Log Name:     System
Source:       SMSvcHost 3.0.0.0
Date:         2/3/2010 3:18:25 PM
Event ID:     8
Task Category: Sharing Service
Level:        Error
Keywords:     Classic
User:         LOCAL SERVICE
Computer:     Server1.Contoso.com
Description: An error occurred while dispatching a duplicated socket: this handle is now leaked in the process.
ID: 6408
Source: System.ServiceModel.Activation.TcpWorkerProcess/54166759
Exception: System.TimeoutException: This request operation sent to http://schemas.microsoft.com/2005/12/ServiceModel/Addressing/Anonymous did not receive a reply within the configured timeout (00:01:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.
Server stack trace:
  at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)
  at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
  at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
  at System.ServiceModel.Channels.ServiceChannelProxy.InvokeEndService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
  at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
  at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)
  at System.ServiceModel.Activation.WorkerProcess.EndDispatchSession(IAsyncResult result)
Process Name: SMSvcHost

Process ID: 4056

 

Here is the Microsoft article regarding the SMSvcHost.exe Error 8 problem experienced:

 

SMSvcHost Error Causing Leak In The Process

There's also a Microsoft KB Article on this. This article also lists the affected environments and prerequisites. This also details how to obtain the hot fix. Please note that, despite the lack of statement in the Microsoft KB, it is necessary to have .NET 4 installed in order to successful run the hot fix.

Option 2. Edit the SMSvcHost.exe.config file.

By default, the SMSvcHost.exe.config file looks like this:

<configuration>   <system.serviceModel.activation>       <net.tcp listenBacklog="10"           maxPendingAccepts="2"           maxPendingConnections="10"           receiveTimeout="00:00:10"           teredoEnabled="false">          <allowAccounts>             // LocalSystem account              <add securityIdentifier="S-1-5-18"/>             // LocalService account              <add securityIdentifier="S-1-5-19"/>             // Administrators account              <add securityIdentifier="S-1-5-20"/>             // Network Service account              <add securityIdentifier="S-1-5-32-544" />             // IIS_IUSRS account (Vista only)              <add securityIdentifier="S-1-5-32-568"/>           </allowAccounts>       </net.tcp></configuration>

 

You may need to increase the listenBacklog, maxPendingConnections, maxPendingAccepts, and maxPendingConnections to something higher to accommodate requests on the server. There is no exact science to this, but increasing all by a factor of 10 will definitely be more than sufficient. You may also wish to increase the timeout value.

Uninstalling Pharos iMFP for Samsung


1. Using a web browser, navigate to the device's SyncThru webserver located at http://<ipaddress>.
2. Press the "Login" link at the top of the page. This pops up a window prompting you for logon credentials.
3. You must log in as the machine Administrator. After entering the System Manager credentials, press the "LOGIN" button.
4. On A4 devices, select the "Network/Security/Maintenance" button. (Skip this step on A3 devices.)
5. On the left menu, select Maintenance->Application Management->Application

6. Select the "Pharos" application.
7. Click the "Delete" button. And confirm.
8. After uninstallation the administrator credentials will revert to platform default

See Attachment

A Collector is reporting as faulty in the Blueprint Administrator.  The Test Results indicate the following error:

"The WCF HTTP Server Communication test failed. The request channel timed out attempting to send after 00:00:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout."

Observed Symptoms:

  1. Blueprint Administrator reports one or more Collectors as faulty with WCF communication errors.
  2. Blueprint Collector passes self checks when using the Blueprint Server Configuration utility but shortly afterward generates a popup error stating that health status reporting to the Analyst has failed.

Cause:

Microsoft.NET - the managed code library around which much of the Blueprint software is developed - is attempting proxy communication using Web Proxy Autodiscovery Protocol (WPAD). This behavior causes the Blueprint services (namely, the Pharos Systems Taskmaster service) to also attempt communication via WPAD, resulting in a timeout.  WCF HTTP communication subsequently fails.

 

Resolution:

Edit the failing Analyst's and / or Collector's .NET library machine.config file to explicitly disable automatic proxy discovery.

The machine.config file can be found within the
%windir%\Microsoft.NET\Framework\v2.0.50727\CONFIG folder.

Add the following text within the <Configuration> section.

 

<system.net>
   <defaultProxy >
     <!-- Disable Autoproxy-->
     <proxy autoDetect="false"/>
   </defaultProxy>
</system.net>

 

An edited machine.config file can be found below as a reference.

Make sure to retain a copy of the original machine.config file as a backup.

 

After making the edit and saving the file, the Pharos services will need to be restarted.  Use the Blueprint Server Configuration utility to test functionality on the Collector.  Likewise, open the Blueprint Administrator on the Analyst, select the previously failing Collector and click the Update Status button to retest connectivity.


This issue will be addressed in the future release of Blueprint HotFix, however you can run the attached SQL Script which works around this issue. To apply it please simply run it against the psbprint database.

When I try to log in to a Secure Release device, there is a 15-30 second delay, sometimes followed by a message: "Session not authorized." If I try to log in again, it works just fine and there is no delay. If I let the system sit idle for a little while, the delay happens again. What's going on?

 

Cause

To provide our customers the safety and security of verified and trusted applications, Pharos Systems digitally signs, via a trusted Certificate Authority, our applications and DLLs and registers them with Microsoft. In many cases, signed applications run normally on the operating system because Windows itself does not check, nor validate, the signature. However, applications which run under .NET (like most of ours) can be an exception, and .Net can request signature validation, and this requires an expensive network-based request. Part of this network request will attempt to contact the Certificate Authority owner and Microsoft to determine if the certificate has been revoked by looking at a Certificate Revocation List (the "CRL"). In many cases, the server hosting the Pharos software is unable to reach an external network (VLAN rules, Internet proxy server restrictions, etc.), and so the requests eventually time out.

 

However, this check for the CRL -- and its eventual time out -- occurs during the authentication component of the user's terminal session, and so contributes to the "Inactivity Timeout" associated with the terminal. This causes the error message observed on the terminal's display. The subsequent log in (and log in attempts for the next several minutes) are successful because .Net temporarily "remembers" that it was not able to verify the signature for a short time and chooses not to validate the signature during that time.

 

Resolution

 

Microsoft Windows provides, via Group Policy Object, a way to manage certificate checking for systems not able to connect to the Internet. This is described in Microsoft KB article 2677070. The following extract of this article describes the "how to" process to disable the network check.

From Microsoft KB Article 2677070:

If you cannot avoid installing this update on disconnected systems, you can disable the network retrieval of the trusted and untrusted CTLs. To do this, you disable automatic root updates by using Group Policy settings. To disable automatic root updates by using policy settings, follow these steps:

  1. Create a Group Policy or change an existing Group Policy in the Local Group Policy Editor.
  2. In the Local Group Policy Editor, double-click Policies under the Computer Configuration node.
  3. Double-click Windows Settings, double-click Security Settings, and then double-click Public Key Policies.
  4. In the details pane, double-click Certificate Path Validation Settings.
  5. Click the Network Retrieval tab, select Define these policy settings, and then clear the Automatically update certificates in the Microsoft Root Certificate Program (recommended) check box.
  6. Click OK, and then close the Local Group Policy Editor.
  7. In an administrative command prompt, run GPUPDATE to force the local Computer policies (note: this also refreshes the current user's policies as well). Alternately, the computer can be rebooted, but this is not necessary.

After you make this change, automatic root updates are disabled on those systems to which the policy is applied. We recommend that the policy be applied only to those systems that do not have Internet access or that are prevented from accessing Windows Update because of firewall rules.

 

Further to this advice, it is recommended to disable (uncheck) "Allow issuer certificate (AIA) retrieval during path validation." A completed policy is shown below:

 

1826-01.png

DEP (Data Execution Prevention) on Windows 2003 SP1 and XP SP2 has led to a problem with installing BPE3.1 on Win2003 SP1.

 

To get this it working add the BP3.1 executables to the DEP exception? (DEP options in "Properties/Advanced/Performance/Data Execution Prevention" on My Computer.)

 

Install failed on:

 

Windows 32-bit version
Pentium 4 Processor

Environment

  • Pharos Blueprint Analyst v5.0
  • Pharos Blueprint Administrator v5.0

Symptoms

  • ERROR: "Cannot contact the Blueprint Analyst or the services are not running."

Cause

The WCF (Windows Communication Foundation) security settings were different between the client and server.

 

Resolution

The correct this problem, the WCF security settings between the client and the server must match.

1. On the Blueprint server, go to \Program Files (x86)\PharosSystems\Blueprint\Bin (NOTE: on a 32-bit server, this would be in \Program Files\PharosSystems\Blueprint\Bin) and copy these files:


global.serviceModel.behaviors.config
global.serviceModel.bindings.config
global.serviceModel.client.config
global.serviceModel.extensions.config
global.serviceModel.services.config


2. Paste them into the \Program Files\PharosSystems\Blueprint\bin directory on the client workstation, overwriting the duplicates.

There is no need to restart any services or processes on the client.

Blueprint Enterprise cannot be installed in a directory whose path name contains the ampersand symbol (&) or percent symbol (%). Attempting to install to a directory with one of these symbols in the path name will cause the install to fail with the following error:

 

"Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor."

 

To fix the problem, rename the install directory path without using the & or % symbols.

Blueprint 3.5 / R2 Configuration generates the following error:

Failed to create a symbolic link from the 'C:\Program Files\PharosSystems\Blueprint\Services\BediService\linkedbin' directory to the 'C:\Program Files\PharosSystems\Blueprint\Bin' directory.


1.     Download Junction v1.05
2.     Copy the following files from the Pharos CD to the server

From the Pharos CD copy files in:

..\Program Files\PharosSystems\Blueprint\bin

 

To the Server:

C:\Program Files\PharosSystems\Blueprint\Services\BediService

C:\Program Files\PharosSystems\Blueprint\Services\TrackerService

(depends where the error is being generated on which service)

3. Rename the file to "linkedbin"
4. Then from the Command Prompt run the following command

Usage: junction <junction directory> [<junction target>]

junction C:\Program Files\PharosSystems\Blueprint\Services\BediService\linkedbin C:\Program Files\PharosSystems\Blueprint\bin

See Attached File

Automatic Log Off and the Pharos iMFP for Canon

 

One of the more confusing functions when implementing a Pharos iMFP solution is the "automatic log out" - this is often referred to as "Login timeout" or "auto logoff" by others. It is confusing not because there is no function for this, but because the setting is within the Canon imageRUNNER itself, and not within the Pharos iMFP configuration. Below follows the configuration discussion for the Canon imageRUNNER Advance series. On other imageRUNNERs, this is referred to as Auto Clear Timer, and is found through (Additional Functions) → [Timer Settings] → [Auto Clear Time].

________________________________________________________________

 

Auto Reset Time

If the machine is idle for a certain period of time (after the last print job or key operation is performed), the display returns to the default screen automatically. This period of time is called the "Auto Reset Time."

NOTE: If '0' is selected, the Auto Reset Time mode is not set.

 

 

1. Press (Settings/Registration) → [Preferences] → [Timer/Energy Settings] → [Auto Reset Time].

2. Press [-] or [+] to specify the desired Auto Reset Time → press [OK].

___________________________________________________________________

 

In many cases, it is desirable to have Auto Clear/Reset set to a high value to accommodate "copier composition" - where individual pages or items are being copied/scanned, so that a user's work is not suddenly for naught because a staple or sticky tab was being a nuisance. The tradeoff is that, in a forgetful moment, a user can walk away from the copier and leave it logged in for the next person. In this case, the next person may be thoughtful and press the Logout button before initiating the new session (particularly when Secure Release Here is involved).

 

See Attached Document:


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

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

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

To correct this behavior, do the following:

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

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

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

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

Omega PS100 Power Supply Specifications

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

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

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

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

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

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

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

Solution:

For Server 2003:

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

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

For Server 2008:

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

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

Errors:

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

Or

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

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

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

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

Why This Happens

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

How To Fix It

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

Installation steps (Uniprint)

 

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

 

Installation steps (Blueprint)

 

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

And If It Still Doesn't Work?

 

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

Other Ways Around This

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

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

Uniprint 8.x Support for PS100

 

Product:

 

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

 


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

 

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

 

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

 

 

 


Distribute to:

 

Pharos World-wide Customer Operations
Distribute by:

 

12 October, 2011

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

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

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

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

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

 

B) If running MSDE, follow these steps:

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

 

In the registry, go to:

HKEY_LOCAL_MACHINE\Software\Pharos\Database Server\Database

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

 

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

 

4) Create a batch file with the following command:

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

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

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

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

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

Please see the screenshot below for an example:

Blueprint WCF Secure Communications test failure

Cause

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

Technical Details

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

Resolution

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

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

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

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

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

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

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

 

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

Pharos Omega Cable Table

Posted by toleary Aug 7, 2013

Overview

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

Standard versus Advanced cables - what's the deal?

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

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

The Pharos Cable Table

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

Standard Cable

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

Advanced Cable

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

TRS Copier Cable

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

Vendor Supplied Harness Kit

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

Sister Model

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

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

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

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

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

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

Pin Name

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

NC = not connected

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

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

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

How can this be resolved?

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

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

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

There are two reasons that this message can occur.

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

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

Development is currently investigating this.

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

 

Pharos Uniprint 9.0 Device ConfigurationPharos Blueprint Enterprise 5.1 Terminal Configuration

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

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

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

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

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

 

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

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


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

 

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

 

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

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

 

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

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

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

Background

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

Definitions

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

Installing Third Party Web Applications

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

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

a. Preton Toner Savings integration

b. Secure Release Here

c. Policy Print

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

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

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

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

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

Resolution

Microsoft WSUS Service

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

Other Web Services

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

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

Image

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

Image

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

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

 

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

Image


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

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

Pharos Systems Secure Release Service is not able to start

 

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

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

 

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

 

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

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

The service should now start correctly.

Cause

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

Resolution

There are two courses of action.

Course 1. Change the Driver's Print Processor

 

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

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

 

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

 

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

 

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

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

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

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

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

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

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

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

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

Environment

·  Pharos Uniprint v8.3

Symptoms

· Jobs are not successfully sent to printer.

· Job titles at terminal do not match job name.

Cause

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

Resolution

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

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

Printer Sharing Tab


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

Printer Security tab


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

Inserting Device in Uniprint

Disabling the Online State Check

No, it cannot.

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

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

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

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

2.     2. Select the Pharos Systems button.

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

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

To Uninstall the Pharos HP iMFP Application on the MFP:

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

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

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

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

5. Select Uniprint or Blueprint.

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

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

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

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

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

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

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

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

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

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

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

 

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

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

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

 

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

 

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

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

 

Mobile Print 1.3.x

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

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

         Services:

               Pharos Systems MobilePrint Configurator Service

               Pharos Systems MobilePrint Worker Service

               Pharos Systems MobilePrint Workflow Service

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

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

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

               i. Pharos Systems MobilePrint Configurator Service

               ii. Pharos Systems MobilePrint Workflow Service

               iii. Pharos Systems MobilePrint Worker Service

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

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

7. Validate Mobile Printing.

 

 

 

Mobile Print 2.1

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

         Services:

               Pharos Systems MobilePrint Worker Service

               Pharos Systems MobilePrint Workflow Service

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

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

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

               i. Pharos Systems MobilePrint Workflow Service

               ii. Pharos Systems MobilePrint Worker Service

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

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

7. Validate Mobile Printing.

Problem Installing iMFP for HP from Windows 7?

Problem

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

Solution

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

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

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

3. Choose the Compatibility tab

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

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

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

Types of Universal Printer Drivers

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

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

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

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

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

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

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

2) Universal Printer Driver based on the EMF format

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

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

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

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

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

3) Universal Printer Driver based on the PDF format

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

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

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

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

Uniprint and Net2Printer both use the PDF format.

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

Citrix Printing solution against third party products

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

Some examples are Uniprint and Tricerat.

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

Considerations choosing a product

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

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

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

Conclusion

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

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

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

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

ODBC Pharos Reports error


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

 

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

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

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

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

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

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

Impact With Pharos Blueprint and Uniprint

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

What To Do?

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

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

USE master;

 

ALTER DATABASE <DatabaseName>
SET RECOVERY SIMPLE;

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

> psbprint

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

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

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

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

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

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

 

Pharos Database Structure: Reports Tables

 


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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

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

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

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

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

 

Create the Module executable:

 

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

 

File management:

 

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

 

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

 

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

 

8 = windows XP and 2000

 

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

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

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

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

Changing the Blueprint Server IP Address

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

1. Change the IP address.

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

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

The test should run without failure or prompt.

Changing the Blueprint Server Host Name

 

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

 

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

 

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

 

3. Reboot the server.

 

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

 

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

 


Other items to be aware of:

 

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

 

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

 

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

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

CAUSE

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

SOLUTION

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

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

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

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

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

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

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

 

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

 

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

 

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

 

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

 

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

 

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

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

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

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

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

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

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

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

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

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

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

Choose one of the solutions below.

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

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