ActiveX component can't create object

[djjaan]

If i'm trying to install my winsock app to win2K macine then I receive such message when executing: Run-time error 429 - ActiveX component can't create object. WHY? What can be the problem?

[seoptimizer2001]

Do you have all the necessary .dll's and .ocx's included in the package?

[djjaan]

This is problem with winsock, because even if I create installer and add all the necessary DLL-s it won't work
So - any ideas? Have anyone had same problems with Win2K? On the machine (where is my Win2K VB6 develop environment) everything works fine. Same on the other win2k where is VB6 installed. But on the machine where there is no VB runtime, it wouldn't work at all.

[seoptimizer2001]

The reason it would work on the machines with VB installed is because all the dll's are installed and registered. Don't necessarily trust the VB packaging wizard as it will leave out some dependency files because there is no documentation on those. Check what files you have referenced and what controls you are using and make sure those files are installed on the machines in question. What makes you think that it is winsock causing the problem and not another control?

[djjaan]

well -
My opinion is that in References I should have MS Winsock COntrol. If I check it, there is no control named MS Winsock . If I try to add reference again, program says that name conflict occurs. ;(
I have in beginning of the code these lines:

Private WithEvents Winsock1 As MSWinsockLib.Winsock

I am using latest Windows Common Contols and Common Dialog Control. That's all. Any suggestions?

[seoptimizer2001]

Don't get Components and References confused. The Winsock Control is a Component, thus you need to install and REGISTER the MsWinsck.ocx file on any machine that is going to run this application. Any other files that you have referenced, if any, also need to be installed and REGISTERED on these machines. It really sounds like you are missing one of these files, my guess is the MSWinsck.ocx, because that is the only reason you would get a 'Can't create object error'.

[djjaan]

Actually, MSWinsck.ocx is in all the machines AND it is registered also via regsvr32 (
Same thing when I try to run the program with VB Installer 1.1 which adds all refernces to MSWinsck.ocx and other files. I can try to do the program like this: I do not add reference, but I'm going to use component on the form. This MIGHT help, maybe not. Does anyone more have same problems (installing WinSock app to Win2K machine)?
regardz,

djjaan