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

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: