32bit MAPIbroker has stopped responding

[Guest]

Hello,

I'm seeing a few users here have this issue. We are running the latest versions of Adobe and Office, I have checked for updates on both.

Office 2016 H&B: 1706 8229.2103

Adobe Reader: 17.9.20058

Steps to Reproduce:

1) Launch both Outlook and Adobe Reader

2) Open PDF in Adobe Reader

3) Use the Send File button and make sure that Adobe Reader opens a new Email Message in Outlook

4) Close out of the New Message Window, Close out of Adobe Reader

5) Wait a few seconds and the message appears

This message is quite annoying. Attempting to apply the older fixes for this message have simply changed the error message from 32BitMAPIBroker has stopped responding to a message that Adobe Reader has Stopped responding after being closed.

[Guest]

Exactly the same behaviour.

We are running on a Windows Server 2012 r2 on a RDP session, Office 365 32 bit (2016 ), same Reader.

Acrobat installato:
Acrobat installato: C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\AcroRd32.exe
    Versione: 17.9.20058.234434
    Data di creazione: 2017/07/02
    Ora di creazione: 23:33:38
Browser predefinito: C:\Program Files\Internet Explorer\iexplore.exe
    Versione: 11.00.9600.16384 (winblue_rtm.130821-1623)
    Data di creazione: 2017/05/06
    Ora di creazione: 17:33:47
Controllo:
    Nome: RDPUDD Chained DD
    Risoluzione: 1024 x 768 x 32
    Bit per pixel: 32
Dettagli account:
   Diritti utente: Amministratore
   Controllo account utente: Predefinito
   Integrità processo: Bassa
   Tipo di profilo: Nessuno/a
Dettagli Acrobat:
   Sandbox: Attivato
   Lettore Captive: No
   Supporto per Multi-Reader on Desktop: Disattivato
Dettagli monitor:
   Larghezza schermo: 1024
   Altezza schermo: 768
   Numero di monitor: 1
   Numero di pulsanti mouse: 2
   Con rotellina: No
   Con Pen Windows: No
   Set caratteri a doppio byte: No
   Con Input Method Editor: Sì
   Assistente vocale interno: No
Dettagli sessione:
   Tipo di avvio: Normale
   In chiusura: No
   Rete: Disponibile
   In Citrix: No
   In VMWare: Sì
   Sessione remota:  Sì
   Controllo remoto:  No
   Con JAWS: No
   Con ZoomText: No
   Con Windows-Eyes: No
   Con NVDA: No
Dettagli Windows:
   Tablet PC: No
   Starter Edition: No
   Media Center Edition: No
   Computer lento: No
Directory temporanea: C:\Users\ADMINI~1.EUR\AppData\Local\Temp\2\acrord32_sbx\
Directory Windows: C:\Windows
Fuso orario: ora solare Europa occidentale
Lingua: Italiano (Italia)
Memoria fisica disponibile: 754308 KB
Memoria fisica totale: 3144732 KB
Memoria virtuale disponibile: 3985968 KB
Memoria virtuale totale: 4194176 KB
Nome sistema: TS2013
Nome SO: Microsoft Windows 8.1
Nome utente: administrator
Posta predefinita: Microsoft Outlook
    mapi32.dll
    Versione: 1.0.2536.0 (winblue_rtm.130821-1623)

Processore: Intel64 Family 6 Model 26 Stepping 5  GenuineIntel  ~2267  Mhz
Produttore SO: Microsoft Corporation
Scheda grafica:
    Versione: 0.0.0.0
    Verifica: Non supportata
Spazio file di paging: 3669020 KB
Versione BIOS: INTEL  - 6040000
Versione SO: 6.3.9600 
Plug-in installati:
C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\plug_ins\EScript.api
    Versione: 17.9.20044.222436
    Data di creazione: 2017/04/05
    Ora di creazione: 02:38:18
C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\plug_ins\IA32.api
    Versione: 17.9.20044.222436
    Data di creazione: 2017/04/05
    Ora di creazione: 02:38:18
C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\plug_ins\Updater.api
    Versione: 17.9.20044.222436
    Data di creazione: 2017/04/05
    Ora di creazione: 02:38:18
C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\plug_ins\weblink.api
    Versione: 17.9.20058.234434
    Data di creazione: 2017/07/02
    Ora di creazione: 23:33:40

[Guest]

I may run updates for Office or switch to the deferred channel for Office updates to see if that resolves the issue.

[benjaminj13606833]

Any update on this?

Experiencing the same issue.

We are also having IE crash, which I believe could be tied to this.

Thanks

[Guest]

I haven't been able to reach the person reporting this issue. So I haven't been able to test. You should be able to rollback Office 365 updates using this method thou.

windows - How do I roll back to a specific version of Office 2016? - Super User

[Guest]

Found this information from a different post. Currently reinstalling office and will try this if my current solution doesn't work.

Acrobat Reader DC crashes when sending pdfs via email

[Guest]

Reinstalling Office or rolling back to the deferred channel of updates did not resolve the issue. Issue must be within Adobe Reader. I've also discovered that if we Use Acrobat X Standard instead of it returning an error message the program simply stop responding when sending the email.

[zawtowers]

I have experienced the same issue myself, and did some further testing with Adobe Reader 17.009.20044 and Office 365 32-bit on a Windows 10 PC.

It seems that an Office update after version 16.0.8201.2102 has caused the issue with MAPIBroker - it usually in my case crashes when I exit Adobe Reader - but it does allow the email to be sent.

Any third party program calling Outlook 2016 for a MAPI call seems to utilise fixmapi.exe (in C:\WINDOWS\SysWOW64) which also cross references an Office DLL when you look in the event logs - C:\Program Files (x86)\Microsoft Shared\Office16\ms20win32client.dll

To test if Office has broken it, you can use the Snipping Tool in Windows and select File > Send To > Mail Recipient - if you see a crash message for FixMapi once the email sends (as I did) it shows that it's Office that actually is the problem.   I set the test device not to automatically update Office afterwards, as going to 16.0.8326.2062 also still has the same MAPI issues.

So, 16.0.8201.2102 = stable.  Anything after that = not so.

There is also a new update for Adobe Reader (17.012.20093) so I'll also try that and report back in case the interaction using Adobe's 32-bit MAPIBroker has taken account of the "new" Office functionality.

[thomaslinnepe]

I have the same Problem with the latest Adobe Reader DC and Office Version 16.0.8326.2070 just downloaded from current branch. Waiting for a fix.

[benjaminj13606833]

Switch to deferred channel, it works.

[zawtowers]

Deferred channel is currently on an older build (7766.2099) which is before the last working current build of Office 2016 (8201.2102).

However, after doing further research, this isn't an Adobe issue with Reader as such - it's more a Microsoft issue.  Try doing a "send to" from Windows Explorer with any file - the same crashes occur.

I've recommended users to open a mail in Outlook and attach the files in the more traditional way - it does work.  Microsoft have released another Office update but apparently that doesn't fix their issue either...

[Fantazuiper]

We have exactly the same problem at our company. is there any fix yet?

[zawtowers]

According to this thread on the Microsoft Office forums, version 16.0.8420.100 will be the one to fix the issue.  It didn't just affect Adobe either, but in fact any send to (so for example from File Explorer, 7-Zip, using the Windows Snipping Tool etc).

The thread is here:

https://answers.microsoft.com/en-us/msoffice/forum/msoffice_install-mso_win10/fixmapi-10-mapi-repair...

[zawtowers]

Microsoft have released Office version 16.0.8431.2079 to both the Semi-Annual Channel and the Monthly Channel.

This version successfully sends emails using Send To... without any crashes, and I've tested with the following:

• Adobe Reader DC 17.012.20095
• Using snipping tool and "Send to.." from there
• Using "Send to.." in File Explorer with various types of file

As an added bonus for Excel users, this update also reinstates the "Share Workbook" options that a July update had removed - Microsoft wanted to push people to "co-authoring" until they realised for data protection reasons that not everyone wants to share on OneDrive or SharePoint Online (not even on-prem SharePoint)

So for those of you waiting, it's here, and proves categorically the issue was not with Adobe, but with Microsoft.