Dependency Walker Error: The Side-by-Side configuration information for "ABC.DLL" contains errors

7
votes

I am running a program that I built in Visual Studio 2010 which uses a third party DLL "ABC.DLL". I am on Windows 7 64-bits.

However, it fails to run due to one DLL. When running Dependency walker on this DLL, i get the following error:

Error: The Side-by-Side configuration information for "...\ABC.DLL" contains errors. The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail (14001).

with missing dependencies MSCVR80.DLL and MSVCP80.DLL.

I have tried all the solutions in this following topic but I still am getting the same error.

The ABC.DLL is a third party library that was built in Visual Studio 2005, and I have no way to rebuild it.

I have installed Visual Studio C++ 2005 Redistributable, and tried copying the DLL's taken from another computer (since I do not have them in my computer) and nothing works.

1
visual-studio-2010visual-c++dependenciesmsvcrtside-by-side
Do the program run? Or is the error just in Dependancy walker? – CharlesB
+1 for running Dependency Walker... – user180326
The program does not run, that is why I used the Dependency walker. I will edit my post. – julienln
OK, deleted my answer, thought it was a problem only with dependency walker – CharlesB
Installing the redist should have solved the problem. Be sure that you got the right version, there are 3 of them. Using different versions of the CRT is very unhealthy, hard to diagnose memory leaks are common since the heap isn't shared. You can't have a function that returns std::string for example. A valid license to use the DLL should always include a way to get updates. – Hans Passant

1 Answers

2
votes

You need to look at the manifest in the DLL to determine which version of the Visual C++ runtime you need to install. There are several of them out there; and chances are, you are just using the wrong one.

There are five installers I have found so far.

If the manifest specifies a version that isn't in the list above, you need to contact the makers of the DLL in question. They should be able to provide you with an installer.