14-07-22 03:48 PM
Hi,
I have a requirement to convert a PDF doc into a Word file. I've selected the PDF Toolkit but I am running into errors surrounding some of the DLL Dependencies. My vers of of BP is 6.8.
I have followed the steps within the PDF Toolkit guide to get the Adobe.PDFServicesSDK v2.2.1 and all DLL Dependencies listed within the screenshot. These have all been added to the BP automate folder. When I try and run through the PDFToDocx action (via the PDF Toolkit Test process) I am receiving an error for the System.Linq.dll file not being loaded:
"Exception encountered while executing operation:Adobe.PDFServicesSDK.exception.SDKException: Unable to sign jwt token. ---> System.IO.FileLoadException: Could not load file or assembly 'System.Linq, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) ---> System.IO.FileLoadException: Could not load file or assembly 'System.Linq, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)..."
I've managed to resolve other errors that we're related to the DLLs listed in the screenshot of the guidance, but this DLL is not listed anywhere in the guidance and doesn't come with the core product as standard. I've tried adding in different vers of the System.Linq.DLL file, and have tried adding external references / Namespace import for the DLL, but the error continues to appear.
How can I resolve this in order to get the object working?
Thanks,
Rob
Answered! Go to Answer.
18-07-22 10:52 AM
14-07-22 05:29 PM
18-07-22 09:58 AM
Hi @Geoff Hirst
Appreciate your help with this, we are using vers 4.7 of the .Net framework with our current BP setup
Regards,
Rob
18-07-22 10:52 AM
18-07-22 04:21 PM
Hi Geoff,
I went with a clean slate creating a new console app, and followed your suggestion to do a build on the project. I've then copied across all of the DLLs available in the bin/debug folder and placed them into the automate directory. The PDF test process and toolkit object is now working correctly and I'm getting the expected result (docx output from converting a PDF file).
As you mentioned, I did try and take some of the dependencies listed in the guide document straight from nuget, and along the way I've grabbed the wrong vers of a DLL (couldn't tell you which one though). In the end, no additional DLLs are required outside of those listed in the guide. Performing the Build of the project and grabbing the dependencies from their is much safer and eliminates the risk of getting that wrong vers.
Thanks for your help!
Rob
18-07-22 04:42 PM
22-07-22 11:49 AM
22-07-22 12:52 PM