Runtime Error 429 - activex can't create object

[MQTechie]

Wasn't sure if I should've put this in the VB forum or this one so I've posted to both. But seeing as I'm a sys admin and this involces running an application which has been developed by a 3rd party I thought I'd ask here.

Problem is that I try to install a VB6 application and get "an error occurred while registering [filename.dll]" where the bit in brackets is an actual filename.

As a result, when the application is run, there is a runtime error 429, "activex can't create object".

This is working on another PC running NT4 Wks. Both are running SP6a.

Any ideas?

Thanks in advance

 

[zemp]

Did you try registering the file manually with 'regsvr32'? Thanks and Good Luck!

zemp

 

[MQTechie]

Yes, and it produced an error saying that it had failed, return code is 0x80040154. I have also found the relevant registry enrtries pertaining to this file and exported them from another machine and imported to this machine. Still no luck.

 

[woyler]

what dll is it?

 

[MQTechie]

the filename is psselectdll.dll and is a custom written one for the application I am trying to run. It is not part of the standard VB dll's.

 

[mattKnight]

Do you have a working copy of this software. If you do maybe try taking a copy of the "bad" dll from the working machine, copying that in the correct directory and re-registering the copy.

Another option is that this is some method of software protection (not that i am accusing anyone) Its just a thought...

Good luck

Matt

 

[gpzcrasher]

This might be a red herring but I had a similar problem with a VB app I wrote. It occasionally failed with runtime error 429, but only on one of the 4 PC's it was running on. In the end it turned out to be a memory problem, caused by writing status messages to a listbox during database extraction. When we decreased the number of status messages written, everything was ok.

Hope this helps.

 

[chrisinto]

You might try determining which other components/dll's are utilized by the psselectdll.dll. Perhaps you are unable to register this dll because you don't have the dll's that are required by it on the new machine.
If you have vb on the machine you are trying to install it to, you could attempt to recompile and if it fails you should be able to determine what is missing.

good luck