Technical FAQs: Rental System for Aloha
TABLES ALWAYS SHOW AS AVAILABLE
NOTHING HAPPENS WHEN YOU PRESS "STATUS OF POOL TABLES"
FILE NOT FOUND ERROR OCCURS ON WINDOWS STARTUP
CHANGED LIGHT CONTROLLER SETTINGS AND NOW POOL TABLE LIGHT CONTROLS DON'T WORK
LIGHTS WORK WHEN USING RENTAL SYSTEM ADMIN, BUT NOT AT TERMINALS
XP: RENTAL SYSTEM CANNOT BE DISPLAYED FROM FRONT OF HOUSE, MUST USE ALT-TAB
ILLEGAL OPERATION ERROR MESSAGES FROM CHECKINOUT OR ACTIVETICKETLIST ON FOH TERMINAL
FATAL STARTUP ERROR: CANNOT INITIALIZE ACTIVE TICKET (TSAM) INTERFACE: PERMISSION DENIED
ACTIVE TICKET LIST - CANNOT CONTACT TSAM
RADIANT 1210 TERMINALS - M/S DTC NOT ENABLED
TICKET SYSTEM ACTIVITY MANAGER NOT PRESENT IN DCCOM CONFIG
STARTUP ERROR: PARKING EXIT FEE CALC INTERFACE
SERVER DOES NOT EXIST OR IS NOT ONLINE ERROR MESSAGE ON FOH TERMINAL
REFRESH TABLE DISPLAY ERROR ON FOH TERMINAL.
CANNOT CONTACT TICKET SYSTEM ACTIVITY MANAGER
RENTAL FEES NOT BEING APPLIED AFTER MIDNIGHT
MISSING COMMAND LINE ARGUMENTS, IS PASS PARAMETERS CHECKED
PROBLEM: Able to Start a Pool Table, then return to Aloha, then return to the Rental system, but the Pool Table shows that it still AVAILABLE.
Possible REASONS:
- DCOM Config Settings are not correct on the Terminal;
- DBFs missing in the Aloha DATA directory on the Server;
DCOM SOLUTION - The DCOMCNFG location settings for the Ticket System Activity Manager on the Aloha Terminals are incorrect. See the settings below. Reboot the terminal after updating the settings.
DBF SOLUTION - The following files may be missing or corrupted in your Aloha DATA / NEWDATA directory:
- ActiveTickets.DBF
- ActiveTickets.CDX
- TicketActivity.DBF
Locate these files in either the LTT\DB or LTTDB directories, and copy them to the DATA / NEWDATA directories.
Reboot the Server and all terminals.
PROBLEM: Nothing Happens when pressing "Status of Pool Tables"
Possible REASONS:
- TSBUTTON.CFG file settings are incorrect;
- Anti-Virus software may be enabled;
TSBUTTON SOLUTION: If you did not install the Rental System for Aloha Client at C:\LTT\BIN, the TSBUTTON.CFG file settings in the DATA directory will not be correct. The file settings include the path name to the Rental System Launcher program. Typically, you need to change the drive from "C:" to whatever drive the LTT\BIN directory is located.*
ANTIVIRUS SOLUTION: Anti-Virus software MUST be disabled to communicate FOH applications with the BOH.
*TSBUTTON.CFG is described in AKBID1185.
PROBLEM: LTT_TBL.DBF file not found error in the DATA directoy upon windows startup. The path to the file is listed and appears correct. If you type in the full directory path at the START->RUN prompt, the DATA directory on the server is displayed.
SOLUTION:
The Rental System for Aloha program has begun, but either Aloha is not running or windows networking is not fully enabled. The CheckInOut.Exe program uses a network pathing of \\SERVER\BOOTDRV\IBERROOT\DATA to locate the data directory on the server. Delay the startup of the Rental System Launcher program in the STARTUP group by either using WAIT.EXE or LoneTreeDelay (in the LTT\BIN directory). Using LoneTreeDelay, specify the delay in seconds as the first parameter, then the full path to CHECKINOUT.EXE as the second parameter.
PROBLEM: CAN'T STOP TABLE RENTAL
A software error occurred, possibly due to an invalid/incorrect configuration, that cause the ActiveTickets.DBF to become corrupt.
SOLUTION: Copy the ActiveTickets.DBF/CDX files from the NEWDATA directory into the DATA directory, or the LTT\DB directory. Reboot the SERVER and ALL Terminals.
PROBLEM: CHANGED LIGHT CONTROLLER SETTINGS AND NOW POOL TABLE LIGHT CONTROLS DON'T WORK
SOLUTION: Refresh the system using Aloha Manager. Verify that the Light Control program restarts.
PROBLEM: POOL TABLE LIGHT CONTROL DOESN'T WORK
SOLUTION: Use the Rental System Administration program to test light settings.
- Choose the Item Layout Tab and select items which are configured for light control.
- Select an Item to show the Item Detail Display.
- Click on the ON or OFF button
- Bring up (Maximize) the Pool Table Light Control Program
- Check the console to verify that settings are correct (see example below):
- X10 Example:
- Verify that displayed Controller Type is X10
- Verify that the firecracker device is physically connected to the COM PORT listed
- Verify that the pool table lite can be turned on with the handheld remote
- Verify that the House and Unit code values match the settings on the X10 device
- Verify that the Transceiver for the selected item is no more than 100 feet from the firecracker unit
- Test wireless connection to transceiver by issuing remote control command from firecracker's location
PROBLEM: LIGHTS WORK WHEN USING RENTAL SYSTEM ADMIN, BUT NOT AT TERMINALS
SOLUTION: For versions pre 1.5- Check LTTCHECKINOUT.INI file on affected terminal and verify that parameter LIGHTS is set as LIGHTS=TRUE
SOLUTION: For versions 1.5 & up- Check RENTALSYS.INI file on affected terminal and verify that parameter LIGHTS is set as LIGHTS=TRUE
SOLUTION: Verify DCOMCNFG Location settings on affected terminal to insure that:
- "Run Application on this Computer" is not set (unless light control hardware attached to this terminal)
- Parameter for "Run Application on the following Computer" is checked and set for ALOHABOH or computer where Light Control Hardware is attached.
PROBLEM: XP: RENTAL SYSTEM CANNOT BE DISPLAYED FROM FRONT OF HOUSE, MUST USE ALT-TAB TO SEE IT
SOLUTION: A new version of the CheckInOut.exe is available to address this problem. Click Here to download the new version (1.4.0 or greater).
Install Procedure:
- Unzip and copy into the LTT\BIN directory on each FOH terminal running the rental system;
- Open a DOS command box on the terminal and change the directory to LTT\BIN
- From the DOS command box, do CHECKINOUT /REGSERVER
- Restart the Terminal.
PROBLEM: ILLEGAL OPERATION ERROR MESSAGES FROM CHECKINOUT OR ACTIVETICKETLIST ON FOH TERMINAL
SOLUTION: Verify on the BOH Server that the DCOM Config settings, in Default Protocols, that "Connection Oriented TCP/IP" is the first listed protocol. If not, add, then reboot.
PROBLEM: FATAL STARTUP ERROR: CANNOT INITIALIZE ACTIVE TICKET (TSAM) INTERFACE: PERMISSION DENIED.
The following window is displayed:
OR
PROBLEM: ACTIVE TICKET LIST - CANNOT CONTACT TSAM.
The following window is displayed:
CAUSE:
The DCOM Configuration security settings on the BOH Server Machine are not configured to allow other machines to access the Ticket System Activity Manager program.
SOLUTION:
Using DCOMCNFG on the Aloha BOH Server machine, check the following settings, then reboot:
1) Make sure the TSAM Identity Setting is set to the "Interactive User" (see below):
2) Make sure the TSAM Security Access and Launch Permissions are set to use Default (see below):
3) Make sure that under the DCOM Default Security that Default Access and Default Launch Permissions allow EVERYONE to access the system. If not, add the EVERYONE object, with ALLOW ACCESS (see below). Check this for both Default Access and Default Launch.
4) For DCOM Default Properties, make Sure that DCOM is Enabled (See Below):
5) For DCOM Default Protocols, make sure that "Connnection Oriented TCP/IP is listed FIRST (see below):
PROBLEM: DCOM Configuration Settings cannot be changed on a Radiant 1210 Terminal running XP Embedded.
SOLUTION: The Radiant 1210 Terminal is being shipped with the Microsoft Distributed Transaction Coordinator (M/S DTC) uninstalled, preventing DCOM settings from being changed. Radiant has provided a command set to fix this problem. Click Here to download the command set; unzip and run on the Radiant 1210 terminal and reboot. You should now be able to change DCOM settings.
PROBLEM: Ticket System Activity Manager is missing in DCOM config after installing Rental System on Back of House.
SOLUTION: On the Back of House server, navigate to the LTT\BIN directory and run the file "ltt_regserver.bat". This will install the necessary components allowing configuration of the Rental System.
PROBLEM: DB Error in createFeeGroupList(): File 'feegroups.dbf' does not exist.
CAUSE:
The ODBC path settings for "FEE COMPUTER" and "FEES" are incorrect.
SOLUTION: Open the Control Panel on the FOH machine. Right click on "ODBC Data Source Settings" and choose properties. In the "User DSN" tab, click on "Fee Computer", then click on the "Configure" button. Set the correct values to the path of the LTTDB directory located on the server under the "Path" textbox. Typically, the setting is "\\ALOHABOH\BOOTDRV\ALOHA\LTTDB". Repeat for "FEES". Click OK and reboot the FOH.
PROBLEM: When starting Rental System, the following error message is displayed: "Server does not exist or is not online".
CAUSE:
Firewall on BOH server may be running and not configured to allow the Rental System to communicate from FOH terminal.
SOLUTION: Add Rental System to the exceptions list of the firewall. If firewall is not necessary, turn off firewall(IMPORTANT NOTE:Failing to use a firewall can increase the risk of malicious attacks on the host system).
CAUSE:
Operating system may not have the most recent service packs loaded (Windows 2000 & XP).
SOLUTION: Update operating system to the most recent Windows Service pack.
PROBLEM: During installation of the Wait List System, the following error message is displayed:"Database Error: Driver does not support this function."
CAUSE:
Microsoft Visual FoxPro ODBC driver is not installed on the server. (This is common among post Windows 2000 Operating Systems)
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: When attempting to access the Rental System from FOH terminal, "RefreshTableDisplay error" is displayed.
CAUSE:
Rental System database has been corrupted due to improper editing.
SOLUTION: When attempting to remove Floorplans, be sure to first remove items applicable to each Floorplan being deleted. After removing the items on applicable Floorplan, then remove the Floorplan.
PROBLEM: 'Cannot contact Ticket System Activity Manager" message displayed on FOH terminal.
CAUSE:
Rental System activity interceptor not set.
SOLUTION: In Aloha manager click on Maintenance - Store Settings - System Group. In the "Interfaces" tab, add "RENTALSYS.FOH" to External Activity Interceptors.
PROBLEM: Rental System fees are not being applied to the Aloha check after midnight.
CAUSE:
Fees are not set to begin after midnight.
SOLUTION: Create a fee rule similar to the days previous fee, to begin at midnight(00:00). Any rentals that begin AFTER midnight will then be calculated.
PROBLEM: 'Missing command line arguments, is pass parameters checked?" is displayed at FOH terminal.
POSSIBLE REASON:
Rental System is not installed at the terminal.
SOLUTION: Open Windows Control Panel, choose Add/Remove Programs. If 'Rental System for Aloha FOH' is not installed, you must install the application on the FOH terminal.
PROBLEM: Rental System items do not show as busy/available immediately after changing the status of the item.
POSSIBLE REASON:
System time between FOH and BOH are not synchronized.
SOLUTION: Synchronize the time via Aloha Manager or through the System settings directly on each terminal.
PROBLEM: After installing and configuring the Rental System, when choosing 'Status of Tables', nothing happens.
POSSIBLE REASON:
Environment variable may be set incorrectly.
SOLUTION: Check environment variables SERVER, IBERDIR, LOCALDIR and IBERROOT. Make sure valid values are set. Invalid value could be 'TRUE' or a non-existent value.