Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

The procedure entry point could not be found

I have a program that I am writing program.exe, it loads a dll lib.dll. When I run program.exe in debug mode everything works fine. When I try to run in release mode I get an error:

The procedure entry point ... could not be located in the dynamic link library lib.dll.

When I open the dll in dependency walker that exact function with all the same weird symbols is there. I looked at the module window in visual studio to make sure that I am not loading the dll from the wrong directory but that is not the case. I compiled both the dll and exe with the same compiler (Visual Studio 2012) so that is not the problem either. What could be causing this?

Edit:

I converted lib.dll into a static library and everything works fine. I give up!

like image 982
Benjy Kessler Avatar asked Dec 31 '13 08:12

Benjy Kessler


People also ask

How do I fix the procedure entry point steam controller could not be located in the dynamic link library?

This error is mostly caused by a corrupted dll file, other configuration files, drivers, or a bad configuration and can be fixed by either fixing or replacing the dll files, performing a system restore, reinstalling a fresh copy of the application, or updating to the latest version.

How do I fix the procedure entry point could not be located in the dynamic link library ADVAPI32 DLL?

On some versions of Windows, the error "CreateProcessWithTokenW could not be located in the dynamic link library ADVAPI32. dll" can be solved by installing the Adobe Acrobat and Reader update. Run a virus/malware scan of your entire system.

How do I fix kernel32 entry point not found?

To resolve the issue, download the Microsoft Windows 7 update using the link below: Windows 7 Microsoft Update. Unzip the file. For 32-bit machines install x86 and for 64-bit machines install x64.

How do you fix the procedure entry point Skidrow could not be located in the dynamic link library?

Open the folder the game was installed in at C:\Program Files, right click to copy of the binkw32. dll file. Paste the file into my C:\Windows\System32 directory. I hope this helps.


1 Answers

I ran into the same problem, and in my case, this was due to the fact that I had two versions of the same library installed on my computer.

In the end, the problem was that I was linking my program against the new LIB file while my PATH was pointing to the old DLL. When the library version number is not included in the LIB or DLL file names, it is very easy to mix the versions.

like image 195
BConic Avatar answered Oct 15 '22 02:10

BConic