Aloha Delivery Interface Error 429: ActiveX Component

[alohatech2]

I broke something!

Aloha Delivery ver. 5.27.2 (this is not an aloha version, it's the fastech version)

Doing a file server replacement, Win2k is the OS on both old and new.

While working on transferring files from the old server to the new server, I accidentally copied the backoffice\ds folder from old to new. This is the folder that contains the customer database and the executables for Aloha Backoffice components. The actual backoffice application is in the backoffice root, called Fastech5.exe.

Now, whenever I try to start anything in the Aloha Backoffice application - example: System Parameters - and whenever I try to start the delivery interface, I get the following error:

429: ActiveX component can't create object.

That's all it says.

If I lookup the error in the RKS, I get a similar response that refers to the region/language setup on the server. THIS IS NOT THE PROBLEM. That is setup correctly.

We actually spent a lot of time on this once upon a time when we were trying to figure out how to import the old delivery database into a replacement situation like this. After weeks of trying, our answer was to tell sites that they could use this as an "opportunity" to "cleanup" their customer contacts by starting over. (Translation: SOL, oh well)

So now I am facing a situation where I would have to send them the install CD and reinstall delivery to get it working (this solution is proven).

However, I would rather avoid that, and since I have been active on this forum lately, I thought, "Hey, why not ask them!"

So, anyone got any thoughts?

Thanks

 

[bigblok403]

I had to fix this several years ago, but I forget what the hell I did. If I can remember correctly it had to do with ActiveX looking in the wrong folder. I'm not sure if I fixed it in the registry or Dcom config in Component services.

 

[alohatech2]

Well, it's a start Thanks! I will let you know if I find anything...

 

[SwampGas]

In the control panel, your regional settings may be set to something other than english. No actual translation is necessary if you use the default English in Delivery.

Use English US regional settings and edit the date/time and number formats as desired.

Install the Aloha Inventory Control Translation Utilities and enable use of Trans.mdb by editing the registry

 

[SwampGas]

Sorry, you already mentioned it wasn't regional setting related. Don't know what else to suggest.

 

[alohatech2]

Hey for giggles, can you post the instructions for doing the Trans.mdb registry edit?

The RKS says that it's in the install documentation but I don't see that anywhere. I am going to double check the CD right now but don't think I will find it there.

 

[alohatech2]

I found the setup instructions manual but the language thing is not in there.

 

[alohatech2]

The fastech security client has an incorrect local path in dcom config. The problem is, I don't see how to edit that path. It's not in a field and I am not sure where else to look for the setting ... I am going to search the registry now to see if it's getting it from there.

 

[alohatech2]

Ok Now I am not sure if the path is incorrect.

It doesn't seem to matter where I run Dsoli08.exe from, it gets the same error.

Reinstall here I come...

 

[SwampGas]

I am very weak with Delivery since we are not a delivery concept, but all the registry settings for the Fastech products are at:

HKLM\Software\Fastech

 

[alohatech2]

Thanks- that's good info.

I did fix it, but the back way...

We were "lucky" enough to have another server replacement of the same type right now. I took the backoffice folder, unmodified, from the server image on the second server, and replaced the backoffice folder on the first server. I was back to "normal" and could then just copy the license file, which is what I was trying to do when I copied the DS folder to begin with!

We are up and running. I wish I knew what the issue boils down to, but it's fixed!

Thanks everyone.