Regsvr32 writes an error
-
I wrote a COM Server using ATL wizard, so i made a DLL, and want to use it on another machine - but, when i try to register my server using regsvr32 i have next message: "LoadLibrary("the way to my dll") failed. The specified module could not be found". Where the problem is???
-
I wrote a COM Server using ATL wizard, so i made a DLL, and want to use it on another machine - but, when i try to register my server using regsvr32 i have next message: "LoadLibrary("the way to my dll") failed. The specified module could not be found". Where the problem is???
is it a COM DLL ? or ordinary one ? programming in VB is like riding a kiddy bike, while programming in C++ is like driving a Formula 1 racing car
-
I wrote a COM Server using ATL wizard, so i made a DLL, and want to use it on another machine - but, when i try to register my server using regsvr32 i have next message: "LoadLibrary("the way to my dll") failed. The specified module could not be found". Where the problem is???
Does the path/file specified in the call to
LoadLibrary()exist? Are you using an absolute or relative path name?
"When I was born I was so surprised that I didn't talk for a year and a half." - Gracie Allen
-
I wrote a COM Server using ATL wizard, so i made a DLL, and want to use it on another machine - but, when i try to register my server using regsvr32 i have next message: "LoadLibrary("the way to my dll") failed. The specified module could not be found". Where the problem is???
Assuming you have specified the path to your DLL correctly then your module is probably dependent on another module that is not present on the second machine. Check you are using a release version, or have installed the relevant debug libraries to the second machine. Try using the depends utility to see what modules your DLL is dependent on. Mike
-
Assuming you have specified the path to your DLL correctly then your module is probably dependent on another module that is not present on the second machine. Check you are using a release version, or have installed the relevant debug libraries to the second machine. Try using the depends utility to see what modules your DLL is dependent on. Mike
As i understood the machine i want to install on my dll, doesn't have some "dll's", that my program is required. Yes in my COM dll i have deal with MSXML and RAPI. I'll try to install both of them. But i have some questions about your message: what is the "release version" - is it options of compilor that i usually use where i can change - debug or release in visual studio?, and another question , what is the "relevant debug libraries"?
-
Assuming you have specified the path to your DLL correctly then your module is probably dependent on another module that is not present on the second machine. Check you are using a release version, or have installed the relevant debug libraries to the second machine. Try using the depends utility to see what modules your DLL is dependent on. Mike
So i installed active sync on machine, but nothing changed, i still got this error.
-
I wrote a COM Server using ATL wizard, so i made a DLL, and want to use it on another machine - but, when i try to register my server using regsvr32 i have next message: "LoadLibrary("the way to my dll") failed. The specified module could not be found". Where the problem is???
-
is it a COM DLL ? or ordinary one ? programming in VB is like riding a kiddy bike, while programming in C++ is like driving a Formula 1 racing car
-
As i understood the machine i want to install on my dll, doesn't have some "dll's", that my program is required. Yes in my COM dll i have deal with MSXML and RAPI. I'll try to install both of them. But i have some questions about your message: what is the "release version" - is it options of compilor that i usually use where i can change - debug or release in visual studio?, and another question , what is the "relevant debug libraries"?
Rassul Yunussov wrote: what is the "release version" - is it options of compilor that i usually use where i can change - debug or release in visual studio? Yes I meant the debug/release options in Visual Studio. These control whether debug information is included in your DLL and also whether your DLL uses the debug or release versions of DLLs. This will affect whether it is using for example msvcrt.dll (release) or msvcrtd.dll (debug). The best thing to do is use the Depends utility that is included with Visual Studio and point it at your COM DLL. It will then show you all the DLLs that your DLL depends on. You then need to ensure that all these DLLs are available and registered on the second machine. Mike