Skip navigation
All Places > Knowledge Base & Downloads > Blog > Author: toleary
1 2 3 4 Previous Next

Knowledge Base & Downloads

394 Posts authored by: toleary

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.

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

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.


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.


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.


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.


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


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.


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?




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