cacomputerguy
asked on
VB .EXE gets a "Run Time Error 429 - ActiveX component can't create object" when moved to a target machine
I am using the SOAP Toolkit 3.0 to access a web server application with a VB6 program. When I compile the VB program on the development computer, it works fine. When I move the .EXE to another computer, the program won't run until I install the SOAP Toolkit 3.0 on that computer. I have tried the Package and Deployment Wizard but that doesn't make a difference. I have also added every reference to SOAP components for inclusion in the compiled .EXE. It still doesn't work. I don't want to have to install the SOAP Toolkit on every machine this program will run on. Can anyone tell me what specific files from the SOAP Toolkit need to be copied to the target machine and if something needs to be registered? I can then include these specific files/procedures in the installation process. Thanks!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
http://www.dependencywalker.com/
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I tried DependencyWalker and found 3 DLL's that needed to be installed on the target machine. I copied those from my development machine and registered one, but the other two wouldn't register (regsvr32 gave me an initialization error). I tried InstallShield Express and it built a Setup.exe file that I copied to the target and executed. It installed the VB appl program. When I try to execute the VB pgm, I get "Run-Time error '-2147023782 (8007045a)' Automation error - a dynamic link library (DLL) initialization routine failed"
The names of the DLL would be nice to know.
ASKER
MSSOAP30.DLL, WISC30.DLL and WSDLGEN3.DLL were the 3 DLL's that I manually copied to the target and tried to register.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I found out from the company that wrote the server-side application that Microsoft acknowledges there is a problem with the SOAP client environment. Right now it IS necessary to load the FULL MS SOAP Toolkit on the client machine. Since there was no answer to my specific question (what DLL's can I individually load on the client), I won't award ponts on that basis. However, the answers were thoughtful and informative, so I'm splitting the points accordingly. Thanks.