Skip navigation
All Places > Knowledge Base & Downloads > Blog > 2014 > July
2014

How can the SQL connection's server instance, username and / or password be updated for Pharos Systems SiteMonitor?

 

This procedure utilizes the SiteMonitor installation utility (SiteMonitor.msi) to generate a new configuration file.  It will be necessary to locate the correct Blueprint Enterprise installation package that matches the version that is installed.

  1. On the Analyst server, navigate to the X:\Program Files (x86)\PharosSystems\SiteMonitor\Service folder, where X is the drive letter onto which Blueprint Enterprise was installed.  If the OS is 32-bit, navigate to the X:\Program Files\PharosSystems\SiteMonitor\Service folder
  2. Move the PharosSystems.SiteMonitor.Service.exe.config file out of this folder and place it on the desktop temporarily.
  3. Launch the SiteMonitor.msi installer from the Blueprint installation package.
  4. Click the Next button.
  5. Choose the Repair option.
  6. Within the Site Monitor Setup window that appears, enter the correct SQL server instance, username and password for the SiteMonitor database.
  7. Click the Next button.
  8. Cick the Repair button.
  9. Click the Finish button when completed.
  10. Launch the Pharos Systems Site Monitor Administrator to verify that the service is online and operational.

Environment:

  • Pharos Systems Blueprint Enterprise v5.1
  • Microsoft Windows Server - Cluster Services


Symptom:

  • An invalid Windows Registry key is defined for the creation of the Pharos Systems Secure Release Service generic service for a Microsoft Windows clustered server implementation. This error will cause Secure Release Here job lists to fail at the terminal.


Resolution:

Please use the attached update to the "Blueprint Installation Guide" that comes with the product software download. This update corrects a Windows Registry key error for the Pharos Systems Secure Release Service generic service configuration.

Environment:

  • Pharos iMFP for HP version 4.x (HP FutureSmart)


Symptoms:

  • Install appears to be successful, but after restarting the Pharos application does not run.
  • Uninstalling and reinstalling does nothing to solve the problem.
  • This only happens on some devices, not on most.


Cause:

There is a pre boot menu option called "Skip Disk Load". The option exists right next to "Cold Reset" which is one of the more frequently used options. We have seen folks turning this "Skip Disk Load" feature On by accident while trying to do Cold reset.  If this is option is checked, then Device will not load anything from Disk. The solution loads fine on Disk, but Device behaves as if it doesn't exist. Since it is a sticky setting, multiple reboots and reloading of SW would not have any affect.

Resolution:

Change "Skip Disk Load" to off and then restart the device.

Note: Access to the boot menu should be done by individuals familiar with the HP hardware.

Magtek card reader is connected to supported Xerox iMFP device, however card swipe events are no detected, i.e. nothing is happening after a card swipe.

 

#1. Xerox devices MUST see sentinels in card data obtained from a Magtek card reader.  If the data read from the card does not have sentinels, the Xerox device will completely ignore the card swipe.  Your card readers were configured so that sentinels were disabled, therefore the Xerox was ignoring the card swipe.

 

To re-enable to sentinels, execute the following command to the card reader using the Magtek USBMSR Demo program:

     01 04 63     <send msg>    (This restores the default state to sentinel data flags)
     02     <send msg>

 

If you then swipe a card, the returned data should look something like this:
     ;6008962500504550=99121200000000000000?

 

Note that the ; character the the starting sentinel for Track 2 data.  The ? is the ending sentinel.

 

 

#2. Some older Xerox devices do not like card swipes that contain only Track 2 data.  This will create a situation in which the 1st card swipe will work but then subsequent card swipes will be ignored.  To resolve this issue, reconfigure the card reader to send the Track 1 sentinel of % for the Track 2 data.  This will trick the Xerox into believing that the data is Track 1, thusly allowing each card swipe to behave normally.

 

To change the Track 2 sentinel, execute the following command to the card reader using the Magtek USBMSR Demo program:
     01 15 25     <send msg>        (This sets the Track 2 sentinel to the % character)
     02     <send msg>

 

If you then swipe a card, the returned data should now look something like this:
     %6008962500504550=99121200000000000000?

 

Note that the % character is now the starting sentinel for Track 2 data.  This will trick the Xerox into thinking the data is Track 1.  The ? is the ending sentinel.