has exited with code -1073741515 (0xc0000135) 'A dependent dll was not found'.

Question

_{Sunday, July 13, 2014 7:53 AM}

Am getting the program '[4368] sample.exe: Native' has exited with code -1073741515 (0xc0000135) 'A dependent dll was not found'. 

 the mentioned dll is already in the debug folder, but it shows Cannot find or open the PDB file.

How can i fix such errors 

Debug\SDL.dll', Binary was not built with debug information.
..\Debug\FZ_API.dll', Cannot find or open the PDB file.
..\Debug\avformat-55.dll', Binary was not built with debug information.
..l\Debug\avutil-52.dll', Binary was not built with debug information.
..\Debug\swscale-2.dll', Binary was not built with debug information.
..\Debug\Kinect10.dll', Cannot find or open the PDB file.

All replies (9)

_{Sunday, July 13, 2014 8:06 PM ✅Answered}

What exactly does your project look like?  Are you trying to add a dll from one VS project ot another?  It appears that the project that you are adding as an existing item didn't full compile possibly due to compiler errors. I would start by recompiling the existing project and then after it compiles properly rebuild the second project.

jdweng

_{Sunday, July 13, 2014 10:48 AM}

Never move a dll into the debug folder.  Let the compiler move the file.  By moving the file you won't automatically get updates when the other project gets updated.  Always add dll to project by using the Add existing Item and then browse for the dll in the DEBUG folder in other projects or other locations on the PC.  Moving the dll from its original location will loose the links to the source files.  There is nothing you can to about the Error "Binary was not built with debug information" unless you have the source files.  This error is caused by selecting the executable from the release folder instead of the debug folder.

Sometimes errors like these are occur when referenced projects have compile errors.  Make sure all you other projects are fully compiled.

jdweng

_{Sunday, July 13, 2014 12:47 PM}

"Always add dll to project by using the Add existing Item and then browse for the dll in the DEBUG folder in other projects or other locations on the PC"

In which folder and from where should  I have to add  it then , i mean the dll files using add existing item?

_{Sunday, July 13, 2014 12:52 PM}

Add existing you can browse to any folder on you PC.  From your existing projects or if they came from a vendor's software browse to the vendors folder in c:\Program files.  Many dll don't have full paths names internal so the dll can be install any place.  They will have references like .\.\bin.  So if you move then you don't get internal links.

jdweng

_{Sunday, July 13, 2014 1:09 PM}

I get .dll file is missing when I moved those dll files from the working directory and debug folder....

_{Sunday, July 13, 2014 1:22 PM}

Use the solution explorer and remove the items.  This will remove the items from the compiler build instructions.  Then add the items back using Add Existing.  Currently the build instruction are looking for the source of the reference in your debug folder.  When you browse for the dll in their original location the build instructions will have the new full pathnames.

jdweng

_{Sunday, July 13, 2014 1:59 PM}

I removed the dll from the debug , and tired solution-> add existing item ->dll files ....but the problem of missing dlls still exist....I think I didn't get where to add it exactly

_{Sunday, July 13, 2014 4:35 PM}

A dll may call other dlls.  Did you get the error for the dlls you added as existing or for different dlls? 

jdweng

_{Sunday, July 13, 2014 6:29 PM}

for the dlls I removed from the debug folder

According to dependency walker I got "ERROR OPENING FILE, the system cannot find the file specified".

FZ.LLL.DLL

MSVCP80D.DLL

MSVCP80D.DLL

IESHIMS.DLL

PYLONBASE_MDD_VC80.DLL

Error: The Side-by-Side configuration information for "..\visual studio 2013\....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).

Error: At least one required implicit or forwarded dependency was not found.
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.