You need to refer to official Adobe Documentation: https://www.adobe.com/devnet/acrobat/fdftoolkit.html
I don't know where you've downloaded those DLLs from but it looks like you missed the appropriate guidance in the process. You need to read all documentation.
If you refer to the FDF Toolkit Overview and Reference, right off the bat in the Preface it says :
Windows NT, 2000, or XP (web server software required) or UNIX.
The latest version of the FDF Toolkit to support PDFs was up to Acrobat 8.
I assume that you've already fillout the application to receive from Adobe an official download link for your organization: ftp://ftp.adobe.com/pub/adobe/devnet/acrobat/pdfs/A7Static.pdf
That said, you may need to install the toolkit using the Program Compatibility Troubleshooter and let the wizard detect , download and install any neccesary dependencies and .Net redistributables.
You will (or must) run this toolkit in compatibility mode and test with the troubleshooter how far you need to rollback the program compatibility wizard to an older version of Windows that can support it.
That said, if the wizard detects that it can't be supported it will clearly notify you that the setup cannot continue because is plain and simple "unsupported".
Just remember, that if you already installed the program, all the necessary setup files, .msi files, and DLL's are already there somewhere in your operating system. You just need to know where to find them.
The issue is that, with every new version of MS Windows the tree directory struture of the operating system changes.
So take care in considering that, this 32bit toolkit application used to work in the past with a different folder level structure of the older Windows versions. It is basically expecting to find modules (.dll's) in specific directories that have changed in newer 64bit Windows versions such as Windows Server 2016.
You don't even to download dll's from anywhere, that is unsafe; that was very clearly pointed out to me in these forums when I started last year (but I am not in a production environment like you, so I don't care if my very old computer(s) that I don't ever connect to the Internet get a virus while I am testing hardware with unsafe software, for example).
In your case you should enforce more security awareness and avoid compromising the security standards of your organization (if any) and the customer base that will depend on these services .
In any case, the message that you're getting is very clear. You just need to know where to register these DLL's into the appropriate path.
See this answer where some Adobe XD users are experiencing a crash of the application when they open the program and freezes with a blank screen: https://community.adobe.com/t5/adobe-xd/troubleshooting-adobe-xd-crashes-white-screen-on-launch-on-...
I was able to come up with an observation about 32bit vs 64bit DLL's that helped a few users to partially resolve this issue.
Nevertheless, here is more appropriate Microsoft guidance on how to use the DISM command to scan for corrupted files and restore system health:
https://support.microsoft.com/en-us/help/929833/use-the-system-file-checker-tool-to-repair-missing-o...
https://support.microsoft.com/en-us/help/947821/fix-windows-update-errors-by-using-the-dism-or-syste...
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/sfc
https://bornsql.ca/blog/repair-windows-server-2016-installation/
1
Reply
AdChoices