Aloha Activity 1

[loyalty3]

Hi.

I have an application that use a DLL development for us, this component intercept the aloha events, we are installing our DLL with "Regasm /codebase" and 180 terminals works fine but in 2 terminal I have the next error:

"AlohaActivity: Failed to create CLSID AlohaActivity.ActivityPrinter, result=0x80070002"

In the DEBOUT show me this Log:

Jan 28, 13:26:38, [2548], [INFO],,"Dialog Login [655952] created"
Jan 28, 13:26:38, [2548], [INFO],,"AlohaActivity: Failed to create CLSID FPSSrvr.FPSSrvr, result=0x80070002"
Jan 28, 13:26:38, [2548], [INFO],,"AlohaActivityInterceptManager::Startup() - AlohaActivityInterceptManager::InstantiateFromProgId() CLSID Radiant.Hospitality.AlohaToGo.Intercept.AlohaToGoIntercept"
Jan 28, 13:26:38, [2548], [INFO],,"AlohaActivityInterceptManager::Startup() - Unable to get ClassId"
Jan 28, 13:26:38, [2548], [INFO],,"AlohaActivityInterceptManager::Startup() - AlohaActivityInterceptManager::InstantiateFromProgId() CLSID AlohaActivity.ActivityPrinter"
Jan 28, 13:26:39, [2548], [INFO],,"AlohaActivity: Failed to create CLSID AlohaActivity.ActivityPrinter, result=0x80070002"
Jan 28, 13:26:39, [2548], [INFO],,"Begin reading transaction log..."
Jan 28, 13:26:46, [2548], [INFO],,"Done reading transaction log."
Jan 28, 13:26:47, [2548], [INFO],,"Initializing ComLockdown with C:\Bootdrv\Aloha\bin\radacctl.lic"
Jan 28, 13:26:47, [2548], [INFO],,"Successfully plugged PrintIntercept.IAlohaPrintMonitor.1 InterceptPrinting handler into Aloha"
Jan 28, 13:26:47, [2548], [INFO],,"Failed to instantiate InterceptPrinting plugin: AlohaActivity.ActivityPrinter"
Jan 28, 13:26:47, [2548], [INFO],,"NBCreateConnection 1"


I have another terminal identical with the same hardware and software installed and works fine.

Can you help us to solve this issue please?

Regards!!!

 

[eburks]

because your log shows an inability to create several CLSID's you may be dealing with a permissions issue

Your "Regasm /codebase" software that applied the "patches" should have a logfile and it may point you to the install problem.

If these are all the same version of Aloha your bin folders on your good machine vs problem should be the same, you could check that and possibly find a missing binary on the problem machine.

Maybe the terminals in question are running the iberrq.dll and syncinclusionlist.cfg and are limiting the install of a necessary binary

If you download and run regscanner freely available from Nirsoft and search for the actual CLSID (globally unique identifier) that a working install has for, for instance, AlohaActivity.ActivityPrinter you will probably find that CLSID missing from your problem machine. You may also find any instance of AlohaActivity.ActivityPrinter missing from the registry too. These would just verify that the machine did not create those registry entries that were suppose to be made. I am pretty lost once I get to this level in the registry but is it possible for you to make a batch file to manually register the important dll's using Regsvr32.exe on the problem machines like the unregister and reregister aloha bat files

Tweaking.com has several tools and an all in one tool that will let you reinstate windows settings that may have gotten deliberately or maliciously locked down. I have used it on a machine that refused to complete a version upgrade of one of my least favorite programs Quickbooks. After running their fix acl's tool my install went fine.

You say the terminals have the same hardware and software INSTALLED. If the software was actually INSTALLED on the offending terminals that may be where a problem could creep in. Often proper installs fail (especially Aloha updates I have dealt with) because an installer was expecting one subversion of a C++ runtime or .Net and a different one was actually present on the machine. You can have failures even if the machine has newer versions of the same runtimes.

Most likely your problem starts on the Aloha Server not on the terminal.

And in usual paranoid fashion I should bring up that if you are only having this problem on 2 machines are they at the same location. Even if not, I would search the machines and their servers for any trace of a malicious program.


If you have the ability to clone a working machine and apply that to the problem machine it may fix the problem but not identify where the problem is

 

[reserve2015]

Hi Guys,
Were you able to figure out the issue on this one? Was it a permissions thing?

Our system is getting the error on bootup and none of the terminals work - here's the DEBOUT:
Apr 29, 16:42:42, [3812], [INFO],,"AlohaActivityInterceptManager::Startup() - AlohaActivityInterceptManager::InstantiateFromProgId() CLSID Reserve.InterceptMagcard.1"
Apr 29, 16:42:42, [3812], [INFO],,"AlohaActivityInterceptManager::Startup() - Unable to get ClassId