Adobe Acrobat 32BitMAPIBroker funktioniert nicht mehr

[Veith5EA9]

Hallo,

ich habe das Problem, dass auf meinem Terminal-Server die Folgende Meldung kommt: Adobe Acrobat 32BitMAPIBroker funktioniert nicht mehr.

Der Fehler kommt wenn ein User ein geöffnetes pdf via Adobe Acrobat Reader DC per Mail verschicken möchte. 

Genutzt wird die Version: 2020.012.20041

Server wird mit Windows Srv 2012 R2 Std betrieben

Der Server wurde mehrmals neu gestartet und Adobe wurde mehrmals neu Installiert. Davon hat nichts eine besserung gebracht.

[MeenakshiNegi]

Hi there,

Thank you for reaching out.

As per the above description, the error appears when trying to send the PDF as an email via Adobe Acrobat Reader DC.

Could you please confirm if the issue occurs only with Reader DC? Please check if you can share the PDF from File Explorer using the "Send to" option. Check if you experience a similar behavior.

Did you make any recent changes after which the issue start occuring?

We will be waiting for your response.

Thanks,

Meenakshi

[ChrissyDJ20]

Yes

[arvindy]

Hi Veith5EA9,

We tried but the issue it is not reproducible at our end. We are investigating the issue.

Meanwhile, could you please try the following workaround and let us know if it resolves the issue at your end.

Try the following steps to do that: 

-Quit Adobe Acrobat Reader if already running.

-Download the registry file from: https://documentcloud.adobe.com/link/track?uri=urn:aaid:scds:US:81721873-7907-45dc-9616-ca429b31c008

-Right click on the reg file and select “Merge” then click “Yes” to apply the reg file

-Now try to attach PDF

Kindly let us know if this helps.

Regards,

Arvind

[Veith5EA9 · Accepted solution]

Hi arvindy,

thank you for your help. The Problem was solved by itself. I can send E-Mails via Adobe DC. 

I did nothing. Maybe it was an Windows Update.

Regards

Veith

[arvindy]

Hi Veith,

Thanks for the update, glad to hear that the issue is resolved at your end!

Regards,

Arvind

[TheFirstBold]

Hi,

I had the same problem on our Terminal Server and tried this workaround. After applying this the problem did not occur anymore.

Version 2020.013.20074

What feature is disabled by this workaround?