LoadLibrary error with error code 14001

Question

I am using Visual C ++ 2008 Express Edition to create only a resource DLL. The problem I am facing is that running an application using a DLL on a computer other than mine results in a LoadLibrary () function error with error code 14001.

Internet search seems to be a computer dependency issue running an application with missing libraries of the Microsoft Visual C ++ 2008 redistributable package.

My first step was to install the latest Microsoft Visual C ++ 2008 redistributable package, but this did not solve the problem.

I also changed the setting of my project, so the DLL compiles with a static CRT link, assuming that this way I will get rid of the dependencies.

These options seem to be workarounds for other people having the same problem. Any idea in which direction to look is much appreciated.

thanks

==================================================== ==================================

Thank you for your responses.

Both Dependency Walker and the event viewer indicated a side-by-side configuration problem because I lacked the debug library version of the distributed VC ++ package.

I was sloppy and compiled my DLL in debug mode, recompiling the solution to the problem in release mode.

Answer 1

Try isolating the missing Dependency Walker library:

http://www.dependencywalker.com/

Just run the application on a second computer with this tool, it should tell you which library is missing. Make sure you install the correct version of the Visual C ++ 2008 Redistributable Package; There are two of them, for VS 2008 with SP1 and without SP ...

Answer 2

Take a look at the eventviewer. There is a good chance that an error will appear in Windows SideBySide explaining which build is missing.
This will probably be the VC CRT runtime, which you will have to associate with your DLL.

(Redistributable VC is available here: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=29 )

Answer 3

I had the same problems, but with Visual Studio 2013; DLL debugging set that requires a manifest. In my case, Microsoft.DTfW.DHL.manifest and dbghelp.dll had to be added to the path (I used the exe directory).