Unable to Load DLL or DLL is Not Found
Resolutions for unable to load DLL errors. The exception might also appear as Filename.DLL is not found. In most cases, the exception does not occur until the application using Toolkit is moved to a new machine, or the .NET application was developed with the Evaluation or Developer Edition of Toolkit, and is now running under the Production Edition.
Running ActivePDF Toolkit in .NET produces one of the following exceptions:
- Unable to load DLL (APT40LU.DLL)
- Unable to load DLL (APT40LE.DLL)
- Unable to load DLL (APT40SU.DLL)
- Unable to load DLL (APT40SDV.DLL)
- Unable to load DLL (APT40SE.DLL)
- Unable to load DLL (APT40PU.DLL)
- Unable to load DLL (APT40PDV.DLL)
- Unable to load DLL (APT40PE.DLL)
The causes for these errors can be:
- Bin DLLs missing from System32
- Wrong edition of APToolkitNET.DLL referenced in application
- Access denied to DLLs
Bin DLLs missing from System32
In order to use ActivePDF Toolkit 4.0 in .NET, you must add the installed APToolkitNET.DLL as a reference in your .NET application. This DLL references the DLLs found in the Toolkit Bin folder, but only after they have been copied to the System32 folder. The Binfolder DLLs must correspond to the in-use Toolkit edition. For example, if the message indicates the APT40SE.DLL file, then your application references the Standard Evaluation edition and the APT40SE.DLL file is not in the System 32 folder.
Wrong edition of APToolkitNET.DLL referenced in application
Although the name is exactly the same, each edition of Toolkit installs and requires its own unique copy of the APToolkitNET.DLL, which only work with that edition. For instance, you cannot use the Toolkit 4.0 Standard Developer Edition APToolkitNET.DLL with the Toolkit 4.0 Standard Production Edition. You will need to ensure that your .NET application is referencing the correct edition of the APToolkitNET.DLL. You will aslo need to ensure that the corresponding Bin folder DLLs are in the System32 folder.
Access denied to DLLs
It is possible, yet unlikely, that the corresponding Bin folder DLLs in the System32 folder are lacking the necessary permissions. You will need to ensure that all applicable users invoked by the application are given Full Control.