How to solve procedure entry point not found in dll ?

Question

0.00/5 (No votes)

See more:

, +

I have written a c++ cod for windows 7 32 bit machine using visual studio 2015 and build the solution. The exe file executed perfectly in my system, in which code is built but shows missing dll files. I have downloaded dll files but then came new error. "Missing procedure entry point in dll".
How to solve this??

What I have tried:

I have tried downloading new dlls

Posted 17-Feb-16 18:26pm

Shijin Chandran

Updated 17-Feb-16 18:48pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Garth J Lancaster · Answer 1 · 2016-02-17T18:48:00

Quote:
"Missing procedure entry point in dll".
How to solve this??

I guess, find the correct entry point - either get an updated copy of the documentation for the dll's from the supplier, or, use Microsoft's DumpBin program to see what they export - ie

DumpBin /EXPORTS xyz.dll

where xyz.dll is the dll you wish to use - there's no guarantee you'll get what you need though, going with good documentation is always best