[RESOLVED] 429 Error Help

[Tarasque]

When I try to install my program on another computer I get the ActiveX 429 error.

I have read up on this and tried everything I can think of and read though all the posts on here about the issue and even the FAQ.

I know the error is a dll or ocx file not being registered on that computer.

I've used the application setup wizard with vb 5, used Inno, Setup Factory, everything I can think of and still get the error, so I know I'm missing a file somewhere.

Is there a way to find out what file I'm missing so I can get it in the installer and have it get registered on the other computers I'm installing the program on?

When I try to create dependency files with the application set wizard I get an error that some of the ocx files are out of date and I've tried to fix that, but cant find updated versions of them. I've checked MSDN and Microsoft website all over the place and followed instructions to a T and still no good.

Even when I have sent all the files that I can think of too the other computers I've had to manually register them too

Any help on this would be appreciated.

Thanks

About time to tear the house apart and find my VB 6 CD and get rid of VB 5. I know they say "If it aint broke dont fix it", but VB 5 is giving me soooooooooooooooooooo many headaches lol

Edited:

Just an FYI. Both systems have the same OS - Win Xp Pro and both used the same CD to install the OS

[Hack]

Unless I missed something you didn't say what installer you are using.

[Tarasque]

After doing some searching I found a post on the MSDN forums that said:

You are missing an ActiveX component. You can find out which with the Regmon.exe tool. Start it and run your app until you get the error message. The Regmon output is bit, umm, large. Work backwards and look for access to a key in HKCR\CLSID that isn't found. Look for the same key on a PC that doesn't have the problem with Regedit.exe and you'll know what component you're missing.

I followed this and found the registry entry and I was missing the msxml4.dll file.

Everything works great now. Great thing to do for all those that are having trouble with this same error.