429 Can't create activeX object Error

[mortgagedeveloper]

I am packaging and deploying an application using the VB6 wizard and a strange problem is coming up. The wizard is not copying a DLL to the installing machine. The DLL is set in the dependencies and it is present in the .CAB file.

I made sure the service packs on the installing machine are the same as mine(W2K SP2). I also tried changing the rights on the installing computer to admin rights. I checked the properties on the DLL and everything seems fine. I can manually install the DLL and everything works fine as long as the DLL is installed before the setup routine is run. This is quite the pain since it will go on about 20 computers. I haven't been able to find any reference to this problem in an of the other threads after hours of searching. Any help would be appreciated. Thanks

 

[CCLINT]

Are you using VB6 Service PAck 5?

Which DLL is it? [/b][/i][/u]_{*******************************************************
General remarks:
If this post contains any suggestions for the use or distribution of code, components or files of any sort, it is still your responsibility to assure that you have the proper license and distribution rights to do so!}

 

[mortgagedeveloper]

Yes, using SP5. The DLL is a 3rd party called DES3.DLL. It is an encryption DLL.

 

[CCLINT]

Try setting the application path as the destination path for the dll (in the P&D wizard) and see if that works (it should work)

1. If a DES3.DEP file exists, check out the files it uses and compare them to the ones on the client.

2. Use a dependency walker to see which other dlls this dll needs and uses. Then compare them with the ones on the client machine.

[/b][/i][/u]_{*******************************************************
General remarks:
If this post contains any suggestions for the use or distribution of code, components or files of any sort, it is still your responsibility to assure that you have the proper license and distribution rights to do so!}

 

[mortgagedeveloper]

Found the problem, actually the opposite of what you said, but it pointed me in the right direction. I had a second copy of the DLL in my program files, how, I don't know. The wizard was trying to use that one although another DLL was dependent on that DLL. The wizard was using the AppPath of the DES3.DLL instead of the WinSysPath. changed that and alles klah. Thanks for taking the time to help me out.

 

[CCLINT]

Great!

( And that's: "Alles klar" - "All is clear&quot [/b][/i][/u]_{*******************************************************
General remarks:
If this post contains any suggestions for the use or distribution of code, components or files of any sort, it is still your responsibility to assure that you have the proper license and distribution rights to do so!}