The procedure entry point XXXX could not be located in the dynamic link
When trying to run an executable within the debugger a message box is
displayed containing the following error message:
The procedure entry point XXXX could not be located in the
dynamic link library LLLL.dll
The procedure entry point ?Dump@C2DataDefnSet@@UBEXAAVCDumpContext@@@Z
could not be located in the dynamic link library MCOMN.dll
The entry point (‘XXXX’) and library (‘LLLL.dll’) may vary.
Causes and Remedies:
The library that is being used does not contain the entry point (i.e.
procedure/function) needed. There are a number of possible causes for this:
- An old library is being used.
- If a newer version of the library is available then try that.
It may be that a new procedure has been added to the library that
was not available in the old.
- Check that the expected version of the library is in the path.
It may be that there is an old version of the library in the path
and that is being used instead of the expected one.
- Check the 'working directory' within the project settings.
- If this error is encountered after upgrading a library then consider
reverting back to the old one. It may be that the new version no longer
contains an entry point that the old one supported and which the application
- It may be that one of the dlls other than the one specified is causing
These notes have been tested with Windows NT4.
About the author: Brian Cryer
is a dedicated software developer and webmaster. For his day job he develops websites and desktop applications as well as providing IT services. He moonlights as a technical author and consultant.