Error 429 : ActiveX component can't create object

I'm getting an Error 429 : ActiveX component can't create object when trying
to run a program that ran perfectly fine on Windows XP. It was created in VB6
but does not run on my version of Vista Business. Anyone have any ideas as to
why this may not work. We are desperate...it is a buisiness application that
our customers cannot run!

The particular activex object may not be registered on your system, so you
may need to install it.

Otherwise try running the program elevated.

We also have a complex VB6 financial app which, when we installed on Vista
32 - runs with no problems.

Are you using the Microsoft Best Practices - for instance, if the app tries
to write anything to Program Files on the target computer where the user is
not an ADMIN, you can get funny messages. Perhaps the DLL is not registered
properly..

Perhaps the DLL should be in Program Files\Common Files\Company
Name\DLLName.dll and not %System32%.

Perhaps you should have a VISTA machine with VB6 installed as your test
developement environment. See if the error happens there within the
development environment.

WE use VMWare very successfully for this kind of problem. You can install a
Vista VM under XP but, I am not sure if the environment is really identical
to a real time Vista installation.

Consider also testing the APP on Vista 64 bit. This is the future so get
used to it.

Or, even worse, the app is trying to write to HKEY_LOCAL_MACHINE - that is
*very* tricky with Vista, and actively discouraged by Microsoft...

I use VirtualPC for the same thing - it's certainly close enough to the real
thing for testing purposes...

Absolutely!

We tried to regsvr32 the file: documark_bsl.dll under the c:\Program
Files\Midmark\Documark directory.

We are getting an error though when completing the previously stated
procedure.

The module "documark_bsl.dll" was loaded but the call to DllRegisterServer
failed with error code 0x80004005.

For more information about this problem, search online using the error code
as a search item.

Try registering the component from an elevated Command Prompt window. Click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

We did run a regsvr32 in the elevated Command Prompt window, but we still
recieve an error 429 - ActiveX component can't create object when we start
the application. Just wondering if you have any suggestions on what to do at
this point. Thanks.

Did you get any errors when registering the module? It appears that the registration was not successful. Check if the ProgID that you're initializing in your program is listed in the registry.

Also sure that you're registering the correct dll ie make sure that that is
definitely the component that is causing the error. It may be another.

Go back to the source code, if you have it, and look for statements
containing 'CreateObject'. Then find the file associated with the ProgID eg
via the registry.

[jshenry1963]

The answer is supposedly here:
http://support.microsoft.com/kb/247979
I haven't tried it.
There is a scripting issue, and on this link above there is a patch that you can download and install.
Let us know how it works out.

[mia6224]

I'm facing the same problem.... have you finally found a solution????

[Argamonius]

I have the same problem, and the link to the 'solution' involves coding something or other, and the download is just the scripting program. I mean really? It would prob take them about 30min to make a patch/fix and make it self installing. You would think MS would just create it themselves and allow poeple to d/l it, rather then instructing them how to code it. Not everyone can write code or understand it. Seems Ironic they admit to their error and toss some instructions at you on how to fix it.
Guess some of us will just have to wait for the service pack that will surely come. Which sucks cause I was perfectly happy with my XP what a waste of 200.oo for win 7 pro.

[EINSTEIN_007]

Originally Posted by Argamonius

I have the same problem, and the link to the 'solution' involves coding something or other, and the download is just the scripting program. I mean really? It would prob take them about 30min to make a patch/fix and make it self installing. You would think MS would just create it themselves and allow poeple to d/l it, rather then instructing them how to code it. Not everyone can write code or understand it. Seems Ironic they admit to their error and toss some instructions at you on how to fix it.
Guess some of us will just have to wait for the service pack that will surely come. Which sucks cause I was perfectly happy with my XP what a waste of 200.oo for win 7 pro.

Somebody at microsoft was able to fix this issue. What he did was he added reference to Microsoft DAO 3.6 Object Library instead of Microsoft DAO 3.51 Object Library in his project and it worked, now both on Windows Server 2003 and on Windows XP Professional. Dunno whether it works on Windows 7 or not but you can give it a try.