Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Run-time error 429: ActiveX Component Can't Create Object

Status
Not open for further replies.

mmignot

Programmer
Jul 16, 2001
44
US
Hello,

I am trying to run an application on a Windows 2000 client machine. The application was written in VB6. When I try to run the app I get the following error:

Run-time error '429'
ActiveX component can't create object

The application then closes. This only occurs on Windows 2000 machines. The app works on all other O/S platforms (WIN95, WIN98, NT) with no problem.

Does anyone know what the problem is and how to resolve it?

Thanks in advance,
MM :)
 
What ho,

it does rather depend on what your application is trying to do and how you've installed it into your 2000 box. There could be any number of reasons why this might happen, but, just on the off chance that it might help, here's one I've come across myself; My application was performing data access using ADO. Windows 2000, by default, uses MDAC 2.6, whereas the NT box I was developing on used MDAC 2.5, so I was getting object errors because of that.

I think you're going to have to step through it and see what's failing, I'm afraid :(


Paul
 
It may be due to a DLL or activeX component not registered. Check in the project references. At could also be given if a data source in a related dll or other file is unavailable - I assume that it may be if 'anything' in a referenced .dll (or ocx etc) is unavailable.
Hope this helps.
:G)
 
I have a very simple COM object (returning a string) that works fine on my machine, but get the 429 error on any others I try it on. I have registered the dll and get a message back saying that was successful. Why isn't it working? Does the dll need to be in the same path as it was on the original machine? Is the executable looking in the wrong place in the registry?? Any idea welcome.
Cheers
Paul
 
It appears that the '429' run-time error happens when the following line is executed:

Set oDmoServer = New SQLDMO.SqlServer

I'm not sure what this line is. Does anyone have an idea what the problem is??

Thanks,
MM :)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top