Technical FAQs: XML Order Interface
Aloha XML Menu Extractor: Runtime Error - ODBC Driver Manager
Aloha Crashes on Print Attempt - /DEBUG_COM set
Aloha Crashes on Print Attempt - Invalid Printer ID
POS TERMINAL NOT READY - Message on XML Order Interface Console
Waiting 15 seconds for refresh - Message from Interface Server
PROBLEM: Site License Not Setup
When starting the XML Order Interface, the following message box is displayed:
Solution: The SITEID value in the XMLOrder.INI file has not been setup with Lone Tree Technology. Contact your service provider to get the correct SiteID number for your site.
PROBLEM: Aloha XML Menu Extractor: Runtime Error - ODBC Driver Manager
The following Message box is displayed when a menu is requested:
Solution: The Visual Fox Pro ODBC driver is not installed on the system. Click Here to download the installation package. Double Click to install the driver, reboot the Aloha BOH Server, and restart the XML Order interface.
PROBLEM: The following Message Box is displayed at Startup:
Cause: The program cannot locate the XML Order Interface License Server, and the grace period since the last check with the license server has expired. The typical reason for this error is that the site's Internet connection is not working.
Solution: Verify that the site's internet connection is working properly, then restart the program. If the problem continues, contact your provider.
PROBLEM: The Aloha Terminal Crashes when a print request is made by the XML Order Interface
Cause: Aloha was started with the /DEBUG_COM parameter on the command line. A bug in causes Aloha to crash if /DEBUG_COM is set and the print size is more than 2000 bytes.
Solution: Remove the /DEBUG_COM parameter from the command line when starting IBER or IBERQS.
PROBLEM: The Aloha Terminal Crashes when a print request is made by the XML Order Interface
Cause: An Printer ID specified by the DELTICKETPRINTERID or MSGPRINTERID parameters in the XMLORDER.INI file specifies a printer that does not exist.
Solution: Correct the Invalid Printer ID.
PROBLEM: POS TERMINAL NOT READY - Message on XML Order Interface Console
Possible Causes:
- FOH COM is not enabled - Make sure that the "Use FOH COM Interface?" checkbox is CHECKED on the Aloha Manager Store Settings Maintenance, System Group, Interfaces Tab. Check this and do a refresh.
- The POS Terminal is not corrrectly configured and is not ready to accept requests.
- Check the DEBOUT for this terminal to see if any error messages are present. Correct as needed.
- Temporarily Setup the Terminal Type for the Terminal to "Order Entry Terminal".
- To avoid "Number of Terms" errors, make sure to clear (un-check) the Terminal Type Setting of another terminal
- Verify that the terminal will come correctly, verifying that the floating logo screen is shown.
- Restore the Terminal Type back to "Interface Server", and restore the settings on the other terminal. Be sure to do all necessary refreshes.
PROBLEM: Waiting 15 seconds for refresh - Message from Interface Server
Possible Cause: Environment variables on server could be set to wrong number of terminals. Read interface server debout file. IMPORTANT - Most problems can be found in the debout file for the interface terminal.
Solution: Make necessary changes according to messages from interface server debout file.