Technical Teams, Developers, Account Managers, Database Administrators, and Product Teams.
Description of Issue:
While running Aloha POS version 15.1 and Olo, Iber(qs).exe is looping. Olo will not come to an "online" state.
The Olo log will display repeated errors with HRESULT: 0x8007007E. Below is an example of the error you will see in the Olo log.
Note that this issue can manifest itself as a 4E error as well. The solution noted below can solve many issues related to Aloha 15.1 and the interface server.
2019-10-10 18:12:35.7040|2019-10-10 23:12:35.7040|INFO|Iber was up but the COM interface was not available
2019-10-10 18:12:48.2308|2019-10-10 23:12:48.2308|INFO|Starting Iber
2019-10-10 18:12:48.7924|2019-10-10 23:12:48.7924|INFO|Iber started with process ID 9836
2019-10-10 18:13:00.8044|2019-10-10 23:13:00.8044|INFO|Iber is still Starting
2019-10-10 18:13:12.8165|2019-10-10 23:13:12.8165|INFO|Iber is still Starting
2019-10-10 18:13:24.8285|2019-10-10 23:13:24.8285|WARN|Unable to instantiate the IberFuncs using provided license
System.IO.FileNotFoundException: The specified module could not be found. (Exception from HRESULT: 0x8007007E)
In Aloha 15.1, Iber(qs).exe is dependent on RAL to register the files required to run. In later versions of RAL (RAL 188.8.131.52+), this process may be automatic. In some cases, the process is not successful, and will require manual intervention to complete the registration process.
Manually Register Iber using RAL on 15.1
- Disable Olo services
- Open the Bootdrv\Aloha(qs)\TMP folder. You’ll be watching this to monitor the RAL progress since you won’t see anything on screen.
- Open a command prompt as an Admin and type: cd C:\Program Files (x86)\Aloha SupportReady\AlohaAdm
- Now, type: AlhAdmin.exe /command startaloha /term x (where x = the ID of your interface server)
- At this point in your TMP folder, you should see new RAL logs being generated. Once RAL is done, the AlhAdmin debout will say to “reboot the terminal” at the very bottom of the log. This process can take several minutes each time. Please also be aware that if this is the first time Iber has been registered, the server may reboot on it's own to complete this process.
- Reboot the server
- Repeat steps 2-5 until you see the System.evt files, or the term debout says “terminal up”. (We've seen this complete after 1 reboot, or 3 reboots, it depends on how far along the registration process is)
- Kill Iber(qs).exe and start the Olo services. You should see Olo connected and online at this point.
Possible additional steps:
In some cases the above steps will complete, Aloha will appear to come to a "terminal up" state, but still will not connect to Olo. An additional step could help. In such a case, you may need to manually register Iber(qs) using a command line. (As always, we recommend involvling your reseller/POS support provider when troubleshooting your local POS environment)
- Disable and stop the OloAlohaService.
- Confirm Iber(qs).exe is not running in Task Manager.
- Open a command prompt and path to the %Iberdir%\Bin folder (C: or D:\Bootdrv\Aloha(qs)\Bin).
- Type: "Iberqs.exe /regserver" OR "Iber.exe /regserver" without the quotation marks.
- Start the OloAlohaService service.
- Restart CTLsvr service.
This solution will require some knowledge of the contents of the Aloha(qs)\TMP folder and how to read RAL and terminal debouts. If you aren't comfortable completing the these steps, please contact your POS Specialist for assistance.