Olo and Aloha Kitchen
Technical Teams, Account Managers, Product Development, Brand IT
Failure to register the ALOHAPOSKITCHENINTERFACE.DLL or AK in a state of redundancy results in online orders not being sent to the Kitchen screens.
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.
1) To manually register the interface:
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
%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.
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"
Additional questions should be routed thru the team you receive support from on your Aloha POS and ancillary NCR products.