Hi Maxy,
OK, that's a start. Now lets be absolutely sure do you have all the dlls and their dependencies installed into the Blue Prism Automate folder? Which in the default instance is
C:\Program Files\Blue Prism Limited\Blue Prism Automate.
The PDFToolkit has a number of dependencies and some of those have dependencies of their own. The problem comes when we get to the dependencies that are part of the .NET framework that Blue Prism also uses. So, Blue prism might use x.dll version 1.2.3.4 but PDFToolkit might use x.dll version 1.2.3.3. When you are using Visual Studio, to overcome this problem we can use an assembly redirect. This isn't possible with Blue Prism so we need to trap an event. However, at this time, I just think we have a versioning issue and its not always down to the file that is listed in the error, it can be a dependency of that file. The interesting thing I noted was that my version of Jose.JWT doesn't use System.Collections. I need to ask now, do you have your Adobe credentials setup for the PDF service as this product isn't free.
Let me know how you get on working through the above.
regards
Geoff Hirst
Geoff Hirst
Senior DX Engineer - Digital Exchange - EMEA
SS&C Blue Prism