Error 53 (HRESULT 0x80070002) calling DLL from DLL
-
Hi ! I have two DLLs (VB.NET converted from VB6 COM). First of them is instantiated in the test windows executable. Then the method of this DLL is called, that in turn has to instantiate the second DLL and to call it's method. On two computers it works, on the third - fails with error in subject on instantiating second assembly. The only difference between these computers is the VS2008. On the first two it is installed, on the third - not. I've tried all that I could find in the Internet and that looks more or less close to my problem. With no luck. Can somebody please help me to solve this problem and to understand - why this happens. The issue is very urgent. Thanks in advance. Regards, Gennady
My English is permanently under construction. Be patient !!
-
Hi ! I have two DLLs (VB.NET converted from VB6 COM). First of them is instantiated in the test windows executable. Then the method of this DLL is called, that in turn has to instantiate the second DLL and to call it's method. On two computers it works, on the third - fails with error in subject on instantiating second assembly. The only difference between these computers is the VS2008. On the first two it is installed, on the third - not. I've tried all that I could find in the Internet and that looks more or less close to my problem. With no luck. Can somebody please help me to solve this problem and to understand - why this happens. The issue is very urgent. Thanks in advance. Regards, Gennady
My English is permanently under construction. Be patient !!
Error 53 is "network path not found". Is this second .DLL locally installed on the machine and does it reside in the .EXE's folder or one of the folders listed in the PATH environment variable?
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008
But no longer in 2009... -
Hi ! I have two DLLs (VB.NET converted from VB6 COM). First of them is instantiated in the test windows executable. Then the method of this DLL is called, that in turn has to instantiate the second DLL and to call it's method. On two computers it works, on the third - fails with error in subject on instantiating second assembly. The only difference between these computers is the VS2008. On the first two it is installed, on the third - not. I've tried all that I could find in the Internet and that looks more or less close to my problem. With no luck. Can somebody please help me to solve this problem and to understand - why this happens. The issue is very urgent. Thanks in advance. Regards, Gennady
My English is permanently under construction. Be patient !!
What about framework versions? VS2008 can build against 2.0, 3.0 or 3.5 I believe. Check which version your dlls were compiled against and check what is installed on the third machine.
If you have knowledge, let others light their candles at it. Margaret Fuller (1810 - 1850) [My Articles] [My Website]
-
Error 53 is "network path not found". Is this second .DLL locally installed on the machine and does it reside in the .EXE's folder or one of the folders listed in the PATH environment variable?
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008
But no longer in 2009...All DLLs and .exe are in the same folder. Thanks. Regards, Gennady
My English is permanently under construction. Be patient !!
-
What about framework versions? VS2008 can build against 2.0, 3.0 or 3.5 I believe. Check which version your dlls were compiled against and check what is installed on the third machine.
If you have knowledge, let others light their candles at it. Margaret Fuller (1810 - 1850) [My Articles] [My Website]
Good point. I'll check it tomorrow morning (it's 20:45 now). I suppose that 3.5 on the target computer is installed, but it's worth to check. Thanks. Regards, Gennady
My English is permanently under construction. Be patient !!
-
What about framework versions? VS2008 can build against 2.0, 3.0 or 3.5 I believe. Check which version your dlls were compiled against and check what is installed on the third machine.
If you have knowledge, let others light their candles at it. Margaret Fuller (1810 - 1850) [My Articles] [My Website]
I've checked it. Versions 2.0,3.0 and 3.5 are installed on all three machines. Regards, Gennady
My English is permanently under construction. Be patient !!
-
Hi ! I have two DLLs (VB.NET converted from VB6 COM). First of them is instantiated in the test windows executable. Then the method of this DLL is called, that in turn has to instantiate the second DLL and to call it's method. On two computers it works, on the third - fails with error in subject on instantiating second assembly. The only difference between these computers is the VS2008. On the first two it is installed, on the third - not. I've tried all that I could find in the Internet and that looks more or less close to my problem. With no luck. Can somebody please help me to solve this problem and to understand - why this happens. The issue is very urgent. Thanks in advance. Regards, Gennady
My English is permanently under construction. Be patient !!
Hi ! Finally the problem solved. Thanks to Ben Peterson and his A .NET assembly viewer[^] !! Among Referenced Assemblies I've found the ADODB assembly, that is absent on the third machine. Now all works as expected. Thanks to everyone who tried to help me. Regards, Gennady
My English is permanently under construction. Be patient !!