Technical FAQs: Finger Print ID System for Aloha
FREQUENT "INVALID EMPLOYEE NUMBER" ERRORS - WHAT CAN BE DONE? (all versions)
WINDOWS 98 INSTALLATION ERROR: CAN'T FIND INSTMSI.EXE (all versions)
FOH ERROR: DEVICE NOT LICENSED (all versions)
FILE USBDPFP.SYS IS MISSING (version 1.5)
CAN'T FIND LICENSE FILE - NO PATH LISTED (version 1.5)
CAN'T FIND LICENSE FILE - FULL PATH LISTED (version 1.5)
CANNOT UPDATE. DATABASE OR OBJECT IS READ-ONLY (version 1.5)
ODBC DRIVER DOESN'T SUPPORT THIS FUNCTION (version 1.5)
FRONT OF HOUSE - PROGRAM HANGS - DOESN'T START (version 1.5)
XP EMBEDDED (RADIANT): Can't Read Employee Templates - Error 126 (version 1.5)
XP EMBEDDED (RADIANT): Cannot Find Setup.MSI (version 1.5)
FINGERPRINT SCAN IS VERY SLOW (version 2.0+)
FINGERPRINT SCAN RETURNS -8 ERROR (version 2.0+)
FINGERPRINT ID APPLICATION GOES AWAY WHEN SCANNING FINGER (version 2.0+)
URU 4000B SCANNER DOESN'T WORK PROPERLY (version 2.0.0, 2.0.1)
DURING INSTALLATION, USER IS PROMPTED THAT A PREVIOUS INSTALLATION HAS NOT FINISHED
PROBLEM: Frequent "INVALID EMPLOYEE NUMBER" errors on the Front of House for registered fingers.
Cause: The Finger being read may be too dry, due to frequent washing/drying, or low humidity. The fingerprint cannot be identified, so the finger print ID system sends "Employee 0" to the Aloha POS.
SOLUTION: Run the finger lightly across the forehead, then retry on the device. Lightly rubbing the finger across the forehead adds just enough oil to the fingerprint to greatly improve reading ability! This really works!
PROBLEM: ERROR MESSAGE: DB Error: Duplicate Templates for Emp# XXXX Finger XXXX-YY. Delete and Re-Enter.
The following window is displayed at startup by the Finger Print ID Registry program:
Cause: A duplicate finger print template has corrupted the finger print template database.
SOLUTION: Delete all the finger prints for the listed Employee ID and re-register.
PROBLEM: CAN'T FIND LICENSE FILE - NO PATH LISTED
The following window is displayed:
SOLUTION: The SERVER environment variable is not properly set. Make sure the SERVER Environment Variable is setup as a system environment variable in the control panel.
PROBLEM: CAN'T FIND LICENSE FILE - FULL PATH LISTED
The following window is displayed:
SOLUTION: The FPID.LIC file was not copied from the License Disk to the NEWDATA directory on the Back of House Server. Copy the file and try again.
SOLUTION: The BOOTDRV share has not been created. Create the BOOTDRV share on the server.
PROBLEM: CANNOT UPDATE. DATABASE OR OBJECT IS READ-ONLY
The following error window is displayed:
SOLUTION: The Finger Print ID system is trying to access the file: empfp.mdb in the NEWDATA directory on the Aloha BOH server. However, either the file has READ-ONLY attributes, or is not marked as updateable via the network. Note: Both the FOH FingerPrint ID software and the BOH Finger Print ID Registry program access this file via \\SERVER\BOOTDRV\IBERROOT\NEWDATA (SERVER environment variable, IBERROOT environment variable).
In XP, to make the file updateable via the network, make sure the "Allow Network Users to Change my Files" Checkbox is set for the BOOTDRV share (see below).
PROBLEM: ODBC Driver doesn't support this function
The following error window is displayed:
SOLUTION: The Visual Fox Pro ODBC Driver has not been installed on this machine. Click Here to download the Visual Fox Pro Driver. After downloading, right click on the file and select INSTALL.
PROBLEM: FOH PROGRAM HANGS OR DOES NOT START (Version 1.1)
The "Finger Print ID FOH for Aloha" program is started on the Front of House Terminal but appears to hang. Neither the 
nor 
icons can be found in the system tray.
SOLUTION: IF the URU 4000's Red Backlite is ON, then the software is looking for the FPID.LIC file on the Aloha Back of House Server.
- If the file cannot be found, the software assumes that the server is down, checking once every 5 seconds until it finds the file.
- The IBERROOT and SERVER environment variables MUST BE CORRECTLY set! For example, IBERROOT=ALOHA and SERVER=ALOHABOH.
- For Windows 2000/XP, the environment variables must be setup in the Control Panel / System / Advanced.
- Alternately, a batch file may be written to set the environment variables just before starting FPIDFOH.EXE. The following is an example script:
SET IBERROOT=ALOHA
SET SERVER=ALOHABOH
CD %IBERDIR%\BIN
FPIDFOH.EXE
SOLUTION: If the URU 4000's Red Backlite is NOT ON, then there may be an issue with the driver installation. From the Control Panel, remove both the Finger Print ID for Aloha Front of House AND the U. are U. Integrator Platinum Sensor Software. Then reboot and reinstall.
PROBLEM: WINDOWS 98 INSTALLATION ERROR: CAN'T FIND INSTMSI.EXE
The Windows Installer program is not up to date. The URU Integrator installation package requires Windows Installer 2.0
SOLUTION: Click Here to download the Installer for Windows Installer 2.0
1) Unzip all the files to the root directory
2) Double Click on INSTMSIA.EXE to install the Windows Installer 2.0
3) Restart the Finger Print ID system for Aloha (If prompted, choose the REPAIR installation)
FOH ERROR: DEVICE NOT LICENSED
PROBLEM: The Front of House Software is reporting that the connected sensor is not licensed.
Possible Causes:
- The FPID.LIC file was not copied to the NEWDATA (Version 1.5) or the FPID (Version 2.0.x) directory on the BOH Server during the installation.
- The connected fingerprint device is not a licensed device purchased from Lone Tree Technology.
- The device is addition to an existing fingerprint ID system, and the FPID.LIC file is out of date. Copy the FPID.LIC file that was provided with the device to the appropriate directory for your version.
PROBLEM: XP EMBEDDED (RADIANT): Can't Read Employee Templates - Microsoft Access Error 126
Other Symptom: In the ODBC Driver settings, the Microsoft Access Driver is "Un-dated" or "Not Marked"
CAUSE: The image of XP Emedded being shipped on Radiant Terminals appears to be missing the "Microsoft ODBC Desktop Driver Pack 3.5".
SOLUTION: Click here to get the files that make up this driver pack. Unzip and Install in the SYSTEM32 directory, then reboot.
PROBLEM: FILE USBDPFP.SYS IS MISSING
This problem is frequently seen on Radiant 1210 Terminals.
SOLUTION: If the s/w is requesting that you provide the location of this file, look for it in the Windows\System32\Drivers directory.
If you cannot find the file there, or any where else on the harddrive, click here to get an additional install. DO NOT uninstall the URU Integrator S/W. Run this program, then reconnect the reader.
PROBLEM: CANNOT FIND SETUP.MSI
This problem is frequently seen on Radiant 1210 Terminals.
SOLUTION: Click here to get the URU 4000 Driver Installation package. Unzip and run as needed.
PROBLEM: FINGERPRINT SCAN IS VERY SLOW
Fingerprint recognition is taking 30 - 40 seconds or more to return. This problem is frequently seen on Radiant Terminals, but can occur in installations with other hardware as well.
SOLUTION: Define the Aloha LOCALREAD environment variable using the following statement: set LOCALREAD=TRUE. It can be set for the entire machine or set in the IBERCFG.BAT file. This setting is not used directly by the finger print software, but changes the way Aloha interacts with the network.
PROBLEM: FINGERPRINT SCAN RETURNS -8 ERROR
This error will occur on newer Radiant terminals running Windows XP Embedded.
SOLUTION: There is a known incompatability between the Digital Persona driver and the Windows XP Embedded image installed on Radiant terminals. Click here to get the Digital Persona Gold driver and patch. From the Control Panel, unistall any Digital Persona drivers. Refer to "Radiant Terminal Installation Procedures".
PROBLEM: FINGERPRINT ID APPLICATION GOES AWAY WHEN SCANNING FINGER
This problem can occur when using a URU 4000B scanner with versions of software before version 2.0.2.
SOLUTION: Uninstall previous FingerPrint ID software and Digital Persona driver and install version 2.0.2.
PROBLEM: URU 4000B SCANNER DOESN'T WORK PROPERLY
The URU 4000B scanner will only operate correctly with version 2.5+ of the Digital Persona driver.
SOLUTION:Verify that you are using version 2.5+ (lower right corner of FPID screen). If not, uninstall previous FingerPrint ID software and Digital Persona driver and install version 2.0.2.
PROBLEM:During installation of the FPID software(specifically the Digital Persona driver), you are prompted with a message: 'A previous installation has not been completed. Please restart the system and try again'.
CAUSE: An installation on the system failed to close a registry key.
SOLUTION:Open the Registry Editor and navigate to the following path: HKEY_LOCAL_MACHINE\System\CurrentCon
trolSet\Control\SessionManager. Highlight the Session Manager key(folder) and if the value PendingFileRename Operation exists, delete that file. (WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Use Registry Editor at your own risk.)