When you try to load a DLL on Windows via our plugins, you may get back an error message on failure.
Error 126: The specified module could not be found.
You passed an invalid path to the DLL or you tried to load a DLL and it refers to another DLL, which could not be found. For example several DLLs belong together and they should all be in same folder, so Windows can find them. Or a Visual Studio Runtime DLL is missing for the version of the C runtime needed by this DLL.
You can use Dependency Walker application to figure out which DLL is missing.
Error 127: The specified procedure could not be found.
The DLL was loaded, but then an expected function was not found. This could happen if you load the wrong DLL, which doesn't have the functions at all. Or if you have an older DLL, which does not yet export the required function.
Error 193: This is not a valid Win32 application.
Either this is really not a DLL or you mixed 32 and 64bit platforms and got the wrong one. Please make sure you use 32-bit DLL for a 32-bit application and a 64-bit DLL for a 64-bit application.
Error 998: Invalid access to memory location.
The path passed may be invalid and cause a memory access error.
Error 1114: A dynamic link library (DLL) initialization routine failed.
The DLL got loaded, but the initialization routine returned an error message. This may happen with Visual C libraries, if you try to load more statically linked libraries, then you have handles available. Memory may be available, but some handles have a limited list and loading too many DLLs (over 500) can run into a limit.