Outlook 2016 crashes when sending e-mail

[Nick Panaccio]

I've asked this everywhere and have yet to find a solution. Only two users have come forward with this issue, but I have to believe that others just aren't reporting it. Occasionally, when somebody is writing an e-mail (no attachments) and they click on Send, Outlook 2016 completely crashes:

 

 

The crash log is less than useless, because it doesn't point to anything in particular. I've had both users run Outlook with no add-ins enabled and it still crashes. This only happens in our App Layering image for Windows 10, in both build 1709 and 1809.

 

Anyone have any ideas here? I'm trying to avoid building the Office 2016 layer from scratch again, but at the same time, feel that's my only play here.

[Heinz Wirth]

Hi Nick

 

We are facing exact the same with Citrix XenDesktop 7.15 and Office/Outlook 2016 in Online Mode with Exchange 2013 on prem.

Outlook crashes (0xc0000005) while sending an email. After Outlook restart, the Email hasnt been sent and can be found in the outbox.

I created a crash report over all VDIs and users, but I was unable to find any time or object related connection, it is completely random.

 

We already did:

1. Updates Office to latest updates (MSI installation)

2. Disabled any Outlook Add-Ons

3. Changed to mapi over http

4. Re-created Outlook profile

5. Repaired Office 2016

 

We are planning to upgrade to Citrix 1912 anyway and have some options left:

6. Disable Kernel APC Hooking for outlook.exe: https://support.citrix.com/article/CTX107825
7. Enable Outlook Cache (with FS-Logix)

 

Let me know if you have any other findings.

[Nick Panaccio]

29 minutes ago, Heinz Wirth said:

Hi Nick

 

We are facing exact the same with Citrix XenDesktop 7.15 and Office/Outlook 2016 in Online Mode with Exchange 2013 on prem.

Outlook crashes (0xc0000005) while sending an email. After Outlook restart, the Email hasnt been sent and can be found in the outbox.

I created a crash report over all VDIs and users, but I was unable to find any time or object related connection, it is completely random.

 

We already did:

1. Updates Office to latest updates (MSI installation)

2. Disabled any Outlook Add-Ons

3. Changed to mapi over http

4. Re-created Outlook profile

5. Repaired Office 2016

 

We are planning to upgrade to Citrix 1912 anyway and have some options left:

6. Disable Kernel APC Hooking for outlook.exe: https://support.citrix.com/article/CTX107825
7. Enable Outlook Cache (with FS-Logix)

 

Let me know if you have any other findings.

 

I haven't had a report of this in a while, but that doesn't mean much since our users simply may just not be reporting it. My next step was going to be disabling the hook for Outlook.exe, as well. If you go that route and have users who can actually report a success, definitely let me know. We're upgrading to 1912 LTSR next month, and and are actually running FSLogix already, though we're online mode for on-prem users. The few users who have been migrated to O365 are in cache mode with FSLogix's ODFC container.