Link to home
Start Free TrialLog in
Avatar of Richie Knight
Richie Knight

asked on

Adobe Acrobat failed to send a DDE command - Fatal Error

Hi all.

We have a third party bit of software which generates reports in PDF format and automatically opens the generated report in Adobe Acrobat via SQL. For some reason around 2 weeks ago, instead of opening reports in Adobe Acrobat, it now generates an Adobe Acrobat fatal error, "Acrobat failed to send a DDE command".

We have tried completely removing Adobe Acrobat as per their usual guidance on this error using their removal / cleanup tool but we're still getting the same problem.

Any assistance would be appreciated.

Regards,
Richie Knight.
Avatar of Hello There
Hello There

1. Adobe Acrobat and Reader official update containing the fix for this issue is now available. This update will be automatically pushed to all existing installations of Acrobat and Reader. If you want, you may also manually trigger the update by opening the application and going to Help > Check for Updates.
2. Manually update Adobe Acrobat!

If the above doesn't help (not mine):
3.  (This error may occur when you have more than 1 process of Acrobat running)
Open Task manager -> End all processes related to Acrobat -> Launch Acrobat again.
4.  Open Acrobat navigate to Help menu & Repair the installation.
5.  Check the file association on your system.
6. Navigating to HKEY_CLASSES_ROOT\acrobat\shell\open\ddeexec\application and changing the Key "AcroviewA11"  to  "AcroviewR11.
Avatar of Richie Knight

ASKER

Thanks for your reply Hello There.

We are already on the latest version of Acrobat reader, Version 2018.009.20050. Your suggested fix has already been attempted.

Kind regards,
Richie Knight.
So the issue has been solved?
No, I am afraid not.
ASKER CERTIFIED SOLUTION
Avatar of Richie Knight
Richie Knight

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Our third party developer produced an update that resolved this issue.