Back to Olo.com

Aloha POS: Error (0xC0068001) Error trying to login to Aloha


Updated

Audience:

Technical Teams, Engineers

Description of Issue:

Error 01 - (0xC0068001) - Error trying to login to Aloha that happens when Iber(qs) is trying to start per OloAlohaService's instruction to start:

2017-10-24 08:40:46.4594|2017-10-24 12:40:46.4594|WARN|Error trying to login to Aloha System.Runtime.InteropServices.COMException (0xC0068001): Exception from HRESULT: 0xC0068001

Technical Explanation: This issue is rooted in Aloha's need for Iber to load and register all applications and associated files referenced in the intercepts within the Aloha.ini (see Example). Just as a physical terminal requires local exes and dlls in order to load these applications, the interface terminal needs them. This root of this error is difficult to isolate because there is no UI for the interface terminal. Therefore, the answer is actually located in the debout that is named with the ID of the interface server that is configured in Aloha. There are typically one of two reasons this error occurs:

  1. The files do not exist on the Alohaboh machine, which means the prerequisites are missing.
  2. The files exist where they should be, but there is some local resource impeding access to the files, i.e., Windows permissions, RAM is at capacity, flaky network, other erroneous network issue interfering with Aloha's communication. 

Example: 

Note: The values above are informational in nature only and may not be the specific values used for a particular vendor. Because of this, copy and pasting from this article should not be used.


Solution:

Address the impediment to the loading of the prerequisites so that Iber(qs) can boot up completely.

Steps:

Contact reseller if you need assistance with this process of elimination.

  1. Stop OloAlohaService, OloUpdate Service, and confirm Iber(qs) is not running in Task Manager.
  2. Make a backup of the %iberdir%\data\Aloha.ini file in a safe location.
  3. Edit %iberdir%\data\Aloha.ini (from example above) to remove the named CLSIDs (intercepts)

   3. Save, restart the OloAlohaService and watch Iber(qs) come up. 

   4. Stop OloAlohaService, OloUpdate Service, and confirm Iber(qs) is not running in Task Manager.

   5. Edit %iberdir%\data\Aloha.ini (from example above) to add back ONE of the named CLSIDs (intercepts)

 6. Save, restart the OloAlohaService and watch to see if Iber(qs) comes up. 

 7. Repeat process until you find which intercept is missing or cannot access the pre-requisite. As stated before, these can often also be identified in the associated interface server debout. This will likely be listed within the 10-15 lines above the line that looks similar to: 

Oct 24, 11:06:16.270803, [4324], [INFO], [Startup], "ENVIRONMENT START"
 

Caveat: 

These steps are intended for application by a technical resource that has a deep understanding of how Aloha communicates and is staged. Please share this article with your POS technical support team for application so that there are not any permanent changes accidentally made to your POS system.

 

Keywords: Error logging in, error 01, (0xC0068001), offline, Iber will not start

 

LD20171024

 

DIDN'T FIND WHAT YOU NEED?

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

Submit a request

 

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 © 2017 Olo. All rights are reserved.