Library Not Found or Failed to Load When Importing DLL

Solution

Try the troubleshooting steps below to resolve these errors.

Right click on the Call Library Function node and ensure that your program has the correct file path to your DLL.
- Check if the Call Library Function Node (CLFN) uses absolute or relative paths.
- If the file path is correct, load your DLL into a dependency checker program that will make sure that you are not missing any dependencies.
  - There is an open source dependency checker on GitHub that would work for this job, although it is not the only software that would work for checking dependencies.
  - If there is a dependency missing, you will need to place the dependency in the correct location or statically include the dependency when you build the DLL. The particular methods for doing this will depend on your programming language and particular application.
Contact the developer of the DLL and ask whether there are dependencies that require the installation of additional software.
This issue can also occur after updating your Windows OS. Please make sure all of your dependencies of your DLL (Ex: FTD2xx.dll) are not erased after the Windows update.
- Windows 10 uses two directories for program installations. 64-bit programs are located in the Program Files directory and 32-bit programs are located in the Program Files (x86) directory.
Ensure that your Windows account has permission to read the file.
Make sure no other program like Source Code Control or AntiVirus are blocking the DLL.