Back to Olo.com

Aloha POS: Olo Orders do not Appear on Aloha Kitchen Screens


Olo and Aloha Kitchen

Audience:

Technical Teams, Account Managers, Product Development, Brand IT


Summary:  

Failure to register the ALOHAPOSKITCHENINTERFACE.DLL or AK in a state of redundancy results in online orders not being sent to the Kitchen screens.


Details:

In an environment where the Aloha Kitchen Service is running, when a physical terminal or an Interface terminal first boots up in the environment,  alohaposkitcheninterface.dll will register automatically. (located in Bin folder). Occasionally, however, this does not happen.

If all regular orders are going to Kitchen screens as expected, but online orders are not going to Kitchen, and there are no reroutes, events, or routing rules configured that would explain the behavior, then it’s likely that one or both of the below are the root per instructions we have collected from NCR.

*Olo recommends you take these steps with the support of your reseller or NCR team, as Olo does not support your physical POS environment*

Part 1) To manually register the interface:

For Aloha versions up to 14.1

Open up CMD (command prompt) on the terminal and navigate to the POS bin folder.  Then type in:

%WINDIR%\MICROSOFT.NET\FRAMEWORK\V2.0.50727\REGASM.EXE /VERBOSE %LOCALDIR%\bin\ALOHAPOSKITCHENINTERFACE.DLL /CODEBASE

followed by:

%WINDIR%\MICROSOFT.NET\FRAMEWORK\V4.0.30319\REGASM.EXE /VERBOSE %LOCALDIR%\bin\ALOHAPOSKITCHENINTERFACE.DLL /CODEBASE

Note: Replace %LOCALDIR% with the actual path to Aloha\BIN or AlohaQS\BIN if LOCALDIR is not defined in your environment variables.                 

  • When using an interface terminal, this must be done on the file server.
  • Make sure you reboot after running these registrations command in Command Prompt.

For Aloha versions 15.1 + (least privileged environment)

On BOH (because this is where the interface terminal runs), you will need to be logged in to windows with a user that has administrative rights, perform the following:
1. Stop both OLO services.
2. Open task manager and verify iber.exe/iberqs.exe is not running
3. Open a command prompt and copy/paste the following lines (one of the first two may give an error, this is OK as long as one of them says successful). 

*term x, use the ID for the interface server. 

*term y, use the ID for the interface terminal.
 

%WINDIR%\MICROSOFT.NET\FRAMEWORK\V2.0.50727\REGASM.EXE /VERBOSE %LOCALDIR%\bin\ALOHAPOSKITCHENINTERFACE.DLL /CODEBASE

%WINDIR%\MICROSOFT.NET\FRAMEWORK\V4.0.30319\REGASM.EXE /VERBOSE %LOCALDIR%\bin\ALOHAPOSKITCHENINTERFACE.DLL /CODEBASE

cd C:\Program Files (x86)\Aloha SupportReady\AlohaAdm

AlhAdmin.exe /command startaloha /term x (You will need to wait several minutes for the green RAL window to open, run through some configurations, and close)

AlhAdmin.exe /command startaloha /term y (You will need to wait several minutes for the green RAL window to open, run through some configurations, and close)


4. Reboot the computer.

Part 2) Confirm there is an IP address specified in Local Settings:

Even if the POS system is functioning normally, it is possible for AK to operate as if it were in redundancy as a result of having no IP address specified in Local Settings. There needs to be a valid IP address for the AK server specified as depicted here "10.10.1.100"

<LocalSettings>
   <IsMaster>True</IsMaster>
   <NumInstances>2</NumInstances>
   <IPAddress>10.10.1.100</IPAddress>
</LocalSettings>

 

Additional questions should be routed thru the team you receive support from on your Aloha POS and ancillary NCR products.

 

 

 

Didn't find what you need?

Submit a request to our Help Team and someone will
get back to you shortly.

Submit a request

Copyright © 2018 Olo. All rights are reserved.