Description of Issue:
- Iber(qs) will not start and the Olo log states that there are multiple instances of iber(qs) running.
- Iber(qs) may also return generic error messages that can be, but may not always be related. Examples of such errors are:
- Exception from HRESULT: 0xC0068001
- Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE))
When using Aloha POS 12.3 and higher, Aloha Transaction Gateway (ATG) is required although it may not necessarily be utilized at every location. ATG can be configured to instruct NCR products to launch iber(qs) which will prevent Olo from being able to start it successfully. This, in turn, creates a loop of both Olo and ATG attempting to start their own instances simultaneously.
Configure ATG to not have the local NCR products launch Iber by editing the AlohaTransactionGateway.cfg file.
- Navigate to %iberdir%\newdata
- Open AlohaTransactionGateway.exe.cfg in Notepad or preferred text-editor.
- Ensure the "LaunchIber" key matches: <AtgSetting key="LaunchIber" value="false" />
- Ensure the "ForceLaunchIber" key matches: <AtgSetting key="ForceLaunchIber" value="false" />
- Save the file.
- Refresh POS from Aloha Manager or CFC.
- Restart the "NCR Aloha Transaction Gateway Helper" Windows service.
ATG configurations can sometimes be overwritten during upgrades or by installation of additional integrations. You may need to repeat these steps after any such change.
For version 6.7, ATG may only be required under certain scenarios such as if you are using Aloha Guest Manager, Aloha TakeOut, and/or any other 3rd Party or NCR applications. If your 6.7 Aloha implementation does not specifically require ATG, we recommend to check with Reseller or NCR Local Office support to see if it can be safely removed from your system.