Error 429 ActiveX Control Cannot Create Object.
-
Hello all, I am developing a small activeX DLL that will simply be a wrapper for a function that takes a string as a parameter. This string represents a name to be resolved in the Outlook Global Address Book. I have created a group rproject in VB6 containing two project: one being my ActiveX dll and the other as a test program my ActiveX exe. When I built the ActiveX dll code it created a dll and registered it correct? Then I went ahead and built the exe test code this generated an executable. When I run the exe file on my development machine with Visual Studio 6 on it the exe runs fine. I transported this exe and my dll via floppy to a test machine without the Visual Studio 6 IDE and everytime I attempt to run the exe i get "error 429 ActiveX Control cann create object". I have already registered my dll on the test machine (its location is c:\winnt\system32 if that matters), and this method within the ActiveX dll uses MAPI to verify the names passed to it(i also made an attemp to register MSMAPI32.dll but it tells me it cannot find the entry point? is it protected? I also registered msmapi32.ocx which worked fine) I cannot seem to pin point why this exe will not run. I am not sure if One or more dll's are missing or they are not registered right and I have been using process tracking applications to try to pin point the missing libraries with little luck. If anyone has had this problem before or has some advice on how to locate the absent files I need on the test system I would greatly appreciate the help. Thanks for helping out a newbie. Frank :confused:
-
Hello all, I am developing a small activeX DLL that will simply be a wrapper for a function that takes a string as a parameter. This string represents a name to be resolved in the Outlook Global Address Book. I have created a group rproject in VB6 containing two project: one being my ActiveX dll and the other as a test program my ActiveX exe. When I built the ActiveX dll code it created a dll and registered it correct? Then I went ahead and built the exe test code this generated an executable. When I run the exe file on my development machine with Visual Studio 6 on it the exe runs fine. I transported this exe and my dll via floppy to a test machine without the Visual Studio 6 IDE and everytime I attempt to run the exe i get "error 429 ActiveX Control cann create object". I have already registered my dll on the test machine (its location is c:\winnt\system32 if that matters), and this method within the ActiveX dll uses MAPI to verify the names passed to it(i also made an attemp to register MSMAPI32.dll but it tells me it cannot find the entry point? is it protected? I also registered msmapi32.ocx which worked fine) I cannot seem to pin point why this exe will not run. I am not sure if One or more dll's are missing or they are not registered right and I have been using process tracking applications to try to pin point the missing libraries with little luck. If anyone has had this problem before or has some advice on how to locate the absent files I need on the test system I would greatly appreciate the help. Thanks for helping out a newbie. Frank :confused:
Hi Frank, Did you make sure that you had all of the required dependencies for your component installed including the Visual Basic runtime DLL required by your component? Also, if your component references others, they may have references to not only other components, but perhaps versions (or different versions) of DLLs which they require. If those aren't installed, they will most likely fail to load. Sometimes it takes a bit of investigation to determine all dependencies and even the dependencies of those required for them to be used. Regards, Joe
-
Hi Frank, Did you make sure that you had all of the required dependencies for your component installed including the Visual Basic runtime DLL required by your component? Also, if your component references others, they may have references to not only other components, but perhaps versions (or different versions) of DLLs which they require. If those aren't installed, they will most likely fail to load. Sometimes it takes a bit of investigation to determine all dependencies and even the dependencies of those required for them to be used. Regards, Joe
I have looked at this for a while now and I really cant seem to find what Dll's or Ocx's my exe is missing. I have tried refreshing the files on the client maachine eliminating the possibility that they are corrupt, and I have also registered them all numerous times. I beleive the exe hangs when I try to do the following in the code within the exe project. Dim Instance As MyActiveXDllName.ClassName Set Instance = New MyActiveXDllName.ClassName 'This line causes it to hang So i think the problem is with the DLL that I created with VB. I have this dll in the C:\winnt\system32 directory on the client machine and i made sure to register it within the directory. I am not sure what I need to do, as I really do not want to install VB 6 on the client machine, which would defeat the whole purpose of this application. I curerntly have SP5 on VB 6.0 so I think I have the mose current runtimes in the development machine and I made sure that MSVBVM60.DLL was on the client machine and registered and it is. I am really running out of ideas. If anybody has suggestions or an idea that I have missed please help I would greatly appreciate it. Thanks for helping out a newbie. Frank :confused:
-
I have looked at this for a while now and I really cant seem to find what Dll's or Ocx's my exe is missing. I have tried refreshing the files on the client maachine eliminating the possibility that they are corrupt, and I have also registered them all numerous times. I beleive the exe hangs when I try to do the following in the code within the exe project. Dim Instance As MyActiveXDllName.ClassName Set Instance = New MyActiveXDllName.ClassName 'This line causes it to hang So i think the problem is with the DLL that I created with VB. I have this dll in the C:\winnt\system32 directory on the client machine and i made sure to register it within the directory. I am not sure what I need to do, as I really do not want to install VB 6 on the client machine, which would defeat the whole purpose of this application. I curerntly have SP5 on VB 6.0 so I think I have the mose current runtimes in the development machine and I made sure that MSVBVM60.DLL was on the client machine and registered and it is. I am really running out of ideas. If anybody has suggestions or an idea that I have missed please help I would greatly appreciate it. Thanks for helping out a newbie. Frank :confused:
From your problem description, it sounds like you definitely have a dependancy issue. You can use the Dependancy Walker tool (C:\Program Files\Microsoft Visual Studio\Common\Tools\DEPENDS.EXE) on your DLL to make sure you have all the files you need. If your depending on the Package and Deployment wizard to find the dependant files for you, it does a lousy job. I highly recommend using the DW to get a definitive list. Also, since we can't see your code, we can't tell you what your missing. One thing that hits me as strange - you said that your test project is an ActiveX EXE? Why? Is this some kind of server? RageInTheMachine9532
-
From your problem description, it sounds like you definitely have a dependancy issue. You can use the Dependancy Walker tool (C:\Program Files\Microsoft Visual Studio\Common\Tools\DEPENDS.EXE) on your DLL to make sure you have all the files you need. If your depending on the Package and Deployment wizard to find the dependant files for you, it does a lousy job. I highly recommend using the DW to get a definitive list. Also, since we can't see your code, we can't tell you what your missing. One thing that hits me as strange - you said that your test project is an ActiveX EXE? Why? Is this some kind of server? RageInTheMachine9532