.Net COM interop challenge
-
Unable to install and run .Net application which uses COM Interop. Please offer suggestions. The Following message occurs on the target machine: System.Runtime.InteropServices.ComException(0x80040112): Creating an instance of the COM component with CLSID {248DD896-BB45-11CF-9ABC-0080C7E7B78D } from the IClassFactory failed due to the following error: 80040112 At Esc.Tos.Utilities.TCP.escTCP..ctor() At clsTCP..ctror() At mdlMain.ConfigureGlobalItems(frmMain theForm) At frmMAin..ctor() At Program.Main() Of course the application runs dandy on the development box, and other development boxes. Background and useful information: 1) Com object 248DD896-BB45-11CF-9ABC-0080C7E7B78D is the Winsock v.6 control. 2) On the target machine there is application A and application B Application A is a VB6 application which uses said COM object and sends TCP Messages Therefore, I assume that com object is correctly install and functional. Application B is My .Net application and throws the above error. Things I have tried: 1) Copy OCX locally and reregister 2) Run RegASM on the Interop Assemblies 3) Clean the registry 4) Validated the Interop code is pointing to the correct OCX. (using Lutz) 5) Installed applicaiton onto alternate development box using xcopy and life is good. ~Jason
You can only be young once. But you can always be immature. - Dave Barry
-
Unable to install and run .Net application which uses COM Interop. Please offer suggestions. The Following message occurs on the target machine: System.Runtime.InteropServices.ComException(0x80040112): Creating an instance of the COM component with CLSID {248DD896-BB45-11CF-9ABC-0080C7E7B78D } from the IClassFactory failed due to the following error: 80040112 At Esc.Tos.Utilities.TCP.escTCP..ctor() At clsTCP..ctror() At mdlMain.ConfigureGlobalItems(frmMain theForm) At frmMAin..ctor() At Program.Main() Of course the application runs dandy on the development box, and other development boxes. Background and useful information: 1) Com object 248DD896-BB45-11CF-9ABC-0080C7E7B78D is the Winsock v.6 control. 2) On the target machine there is application A and application B Application A is a VB6 application which uses said COM object and sends TCP Messages Therefore, I assume that com object is correctly install and functional. Application B is My .Net application and throws the above error. Things I have tried: 1) Copy OCX locally and reregister 2) Run RegASM on the Interop Assemblies 3) Clean the registry 4) Validated the Interop code is pointing to the correct OCX. (using Lutz) 5) Installed applicaiton onto alternate development box using xcopy and life is good. ~Jason
You can only be young once. But you can always be immature. - Dave Barry
Yeah, don't use COM Interop.
-
Unable to install and run .Net application which uses COM Interop. Please offer suggestions. The Following message occurs on the target machine: System.Runtime.InteropServices.ComException(0x80040112): Creating an instance of the COM component with CLSID {248DD896-BB45-11CF-9ABC-0080C7E7B78D } from the IClassFactory failed due to the following error: 80040112 At Esc.Tos.Utilities.TCP.escTCP..ctor() At clsTCP..ctror() At mdlMain.ConfigureGlobalItems(frmMain theForm) At frmMAin..ctor() At Program.Main() Of course the application runs dandy on the development box, and other development boxes. Background and useful information: 1) Com object 248DD896-BB45-11CF-9ABC-0080C7E7B78D is the Winsock v.6 control. 2) On the target machine there is application A and application B Application A is a VB6 application which uses said COM object and sends TCP Messages Therefore, I assume that com object is correctly install and functional. Application B is My .Net application and throws the above error. Things I have tried: 1) Copy OCX locally and reregister 2) Run RegASM on the Interop Assemblies 3) Clean the registry 4) Validated the Interop code is pointing to the correct OCX. (using Lutz) 5) Installed applicaiton onto alternate development box using xcopy and life is good. ~Jason
You can only be young once. But you can always be immature. - Dave Barry
Install VB6 tools on the machine you need to deploy.....it will do all what is necessary to run it! HTH.
Do rate the reply, if it helps or even if it doesnot, because it helps the members to know, what solved the issue. Thanks.
-
Install VB6 tools on the machine you need to deploy.....it will do all what is necessary to run it! HTH.
Do rate the reply, if it helps or even if it doesnot, because it helps the members to know, what solved the issue. Thanks.
VB6 Tools? I am not familar with that product, Could you include a link. Googling it gives me ... lots of similar stuff.
You can only be young once. But you can always be immature. - Dave Barry
-
VB6 Tools? I am not familar with that product, Could you include a link. Googling it gives me ... lots of similar stuff.
You can only be young once. But you can always be immature. - Dave Barry
I found that in Visual Studio 6 installation once i needed! The issue is with registry entries, if you run VS6 installation and install only Tools from it, hopefully the problem will be solved. Additionally, this might be helpful http://support.microsoft.com/kb/146219[^] HTH.
Do rate the reply, if it helps or even if it doesnot, because it helps the members to know, what solved the issue. Thanks.
-
Unable to install and run .Net application which uses COM Interop. Please offer suggestions. The Following message occurs on the target machine: System.Runtime.InteropServices.ComException(0x80040112): Creating an instance of the COM component with CLSID {248DD896-BB45-11CF-9ABC-0080C7E7B78D } from the IClassFactory failed due to the following error: 80040112 At Esc.Tos.Utilities.TCP.escTCP..ctor() At clsTCP..ctror() At mdlMain.ConfigureGlobalItems(frmMain theForm) At frmMAin..ctor() At Program.Main() Of course the application runs dandy on the development box, and other development boxes. Background and useful information: 1) Com object 248DD896-BB45-11CF-9ABC-0080C7E7B78D is the Winsock v.6 control. 2) On the target machine there is application A and application B Application A is a VB6 application which uses said COM object and sends TCP Messages Therefore, I assume that com object is correctly install and functional. Application B is My .Net application and throws the above error. Things I have tried: 1) Copy OCX locally and reregister 2) Run RegASM on the Interop Assemblies 3) Clean the registry 4) Validated the Interop code is pointing to the correct OCX. (using Lutz) 5) Installed applicaiton onto alternate development box using xcopy and life is good. ~Jason
You can only be young once. But you can always be immature. - Dave Barry
Alright, here is the solution. There is a licenes registry key missing. The most likely violates some eula somewhere. so use with caution. but adding this key will reactiviate the winsock.ocx [HKEY_CLASSES_ROOT\Licenses\2c49f800-c2dd-11cf-9ad6-0080c7e7b78d] @ = "mlrljgrlhltlngjlthrligklpkrhllglqlrk"
You can only be young once. But you can always be immature. - Dave Barry