COM DLL registration problem
-
Hi Friends, I am facing a problem in registering my COM DLL. We have build an Addin for a CAD application, which is a COM addin. At some customer site, the addin dll is not getting registered. When we try to register using Regsvr32.exe, the exe returns an error code of
0x000000B6
. The error description is "The operating system cannot run %1." when viwed with'Error Lookup'
tool. I searched on google newsgroups and i found 1 article stating this error occurs when the ATL.dll on the target machine does not match with the ATL.dll with which the addin dll (the DLL being registered) was built. And we have to use the mindependency build to remove the ATL.dll dependency. Accordingly i found my machine has ATL.dll with version 3.0xxx. where as the client's machine has ATL.dll 2.0xxx. I replaced the ATL.dll with the one that i had and tried to register. Still the problem persists. Any clues on the above problem ? This is the most urgent and most important issue for us. Thanks and Regards, Vikram -
Hi Friends, I am facing a problem in registering my COM DLL. We have build an Addin for a CAD application, which is a COM addin. At some customer site, the addin dll is not getting registered. When we try to register using Regsvr32.exe, the exe returns an error code of
0x000000B6
. The error description is "The operating system cannot run %1." when viwed with'Error Lookup'
tool. I searched on google newsgroups and i found 1 article stating this error occurs when the ATL.dll on the target machine does not match with the ATL.dll with which the addin dll (the DLL being registered) was built. And we have to use the mindependency build to remove the ATL.dll dependency. Accordingly i found my machine has ATL.dll with version 3.0xxx. where as the client's machine has ATL.dll 2.0xxx. I replaced the ATL.dll with the one that i had and tried to register. Still the problem persists. Any clues on the above problem ? This is the most urgent and most important issue for us. Thanks and Regards, VikramDid you check whether you have all the dependencies for your COM dll on the client's machine. Also, if possible try doing the registration through some installer (like installshield). I had a similar problem, when I had previous versions of the same COM Dll on the user's machine, it went fine through a installer. Cheers, Kannan