Copy link to clipboard
Copied
We are using Adobe Reader
And Office 2013 Version
on Windows Server 2012 (not R2) with all Udpates installed - August 2020.
This happen after successfully send the Mail via Outlook in the Moment when we close the Adobe Reader. It happens every Time. I would be happy to receive any Help. Thank You, Jens from Hamburg, Germany
Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: 32BitMAPIBroker.exe
Anwendungsversion: 20.12.20041.1044
Anwendungszeitstempel: 5f235099
Fehlermodulname: 32BitMAPIBroker.exe
Fehlermodulversion: 20.12.20041.1044
Fehlermodulzeitstempel: 5f235099
Ausnahmecode: c0000005
Ausnahmeoffset: 000059fc
Betriebsystemversion: 6.2.9200.2.0.0.16.7
Gebietsschema-ID: 1031
Zusatzinformation 1: 5861
Zusatzinformation 2: 5861822e1919d7c014bbb064c64908b2
Zusatzinformation 3: d8b5
Zusatzinformation 4: d8b5eca0c5e4432f58aa293d866a59d7
Lesen Sie unsere Datenschutzbestimmungen online:
http://go.microsoft.com/fwlink/?linkid=190175
Wenn die Onlinedatenschutzbestimmungen nicht verfĆ¼gbar sind, lesen Sie unsere Datenschutzbestimmungen offline:
C:\Windows\system32\de-DE\erofflps.txt
Hi,
Adobe Acrobat and Reader official update (20.013.20064) containing the fix for this issue is now available. This update will be automatically pushed to all existing installations of Acrobat and Reader. You may also manually trigger the update early by opening the application and going to Help > Check for Updates.
There is no need to set any registry, fix will work with or without the earlier shared reg file.
More information about this release is here: https://helpx.adobe.com/acrobat/release-note/release-notes-acrobat-reader.html
Copy link to clipboard
Copied
Hi there,
Thank you for reaching out and sorry for the trouble.
We have released an update today for Acrobat and Reader DC (Continuous Track) desktop application.
Please update the application to the latest version by going to the Help menu > Check for updates in the application.
For more information on the recent update, you may refer to this link: https://www.adobe.com/devnet-docs/acrobatetk/tools/ReleaseNotesDC/continuous/dccontinuousaug2020qfe....
Let us know if the issue persists.
Thanks,
Meenakshi
Copy link to clipboard
Copied
Hallo Meenakshi,
even with Version 2020.012.20043 is the Issue still the same.
Greetings from Germany, Hamburg
Jens
Copy link to clipboard
Copied
Hi Jens,
We are looking into 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 your workflow
Kindly let us know if this helps.
Regards,
Arvind
Copy link to clipboard
Copied
I can confirm that we are running into this same issue after upgrading to Adobe Acrobat Reader DC (20.012.20043). We applied the above registry fix and so far it has resolved the 32BitMAPIBroker.exe error.
Will the next Adobe Reader update address this issue? Will we need to take any action on the registry change after upgrading to the next version of Reader?
Thanks
Copy link to clipboard
Copied
Hi Arvind,
We have the same issue but don't have the \FeatureState entry in our registry.
Could you please advise how to fix this?
Copy link to clipboard
Copied
Hi Thomas5C2A ,
Please double click and apply the shared registry it will automatically create the FeatureState key and the required dword under it.
If you want the create the dword manually, you need to first create the key āFeatureStateā( click on DC then select āNew>>Keyā then rename it as āFeatureStateā).
And next, create the dword: "4163520" with value: zero(0).
Regards,
Arvind
Copy link to clipboard
Copied
Hi,
This is still an issue for one of my customers with O365 Office.
Below is the Adobe error when closing the Adobe application, emailing a file still works. We have spent some time troubleshooting this . Based on this we have noted there is a conflict between the latest version of MS Office O365(16.0.13127.21216) and latest Adobe Reader DC (2020.013.20074) version(Dec 2020).
Adobe Acrobat 64BitMAPIBroker has stopped. When you close it after a succesful mail being sent.
Any ideas anyone - been going on a long time!!
Thanks
Copy link to clipboard
Copied
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\Acrobat Reader\DC\FeatureState]
"4163520"=dword:00000000
registry settings for future reference
Copy link to clipboard
Copied
Hi,
This is still an issue for one of my customers with O365 Office.
Below is the Adobe error when closing the Adobe application, emailing a file still works. We have spent some time troubleshooting this . Based on this we have noted there is a conflict between the latest version of MS Office O365(16.0.13127.21216) and latest Adobe Reader DC (2020.013.20074) version(Dec 2020).
Adobe Acrobat 64BitMAPIBroker has stopped. When you close it after a succesful mail being sent.
Any ideas anyone - been going on a long time!!
Copy link to clipboard
Copied
Hi,
Adobe Acrobat and Reader official update (20.013.20064) containing the fix for this issue is now available. This update will be automatically pushed to all existing installations of Acrobat and Reader. You may also manually trigger the update early by opening the application and going to Help > Check for Updates.
There is no need to set any registry, fix will work with or without the earlier shared reg file.
More information about this release is here: https://helpx.adobe.com/acrobat/release-note/release-notes-acrobat-reader.html
Please try it out and let us know your feedback!
Thanks for your patience and support!
Regards,
Arvind
Copy link to clipboard
Copied
Hello Adobe,
We are experiencing this same error message on Windows Server 2012 R2 with Adobe Acrobat Reader DC 21.005.20060 and Office 2013 Standard. We have crashdumps from the 32BitMAPIBroker.exe program if needed but to reproduce the issue is the same as the original posted. The registry fix also did not resolve the issue. Please advise.