Hyper-V with a VM RDS Server running on Server 2019 RDS - Users Office 365 Outlook Crashing

Occasional Contributor

 

We have a brand new Dell R7515 with a new AMD EPYC Processer. The OS is Windows Server 2019 Hyper-V with a VM RDS Server running on Server 2019 Standard. We decided to go with a shared license Office Pro Plus installed on the RDS Server. Each user is licensed in O365 with an MS 365 Apps for Enterprise License.

There was nothing special configured about each user's Outlook except Cached Mode was enabled since employees are using O365 Groups. 

Shortly after cutting over users, we found that some employees were experiencing crashes when sending emails outbound. The crashes appear to be completely random, unrepeatable and occur only a few times a day. The only consistent theme was 98% of the cases; the employee was hitting send right before the crash. 

 

Event Log Errors:

Faulting application name: OUTLOOK.EXE, version: 16.0.13328.20356, time stamp: 0x5fa4af94

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0xff00ffff

Faulting process id: 0x39c0

Faulting application start time: 0x01d6bd0373b5916e

Faulting application path: C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE

Faulting module path: unknown

Report Id: 1a3e6b0a-890d-4b30-b12f-1474c0ad8dc5

Faulting package full name: 

Faulting package-relative application ID: 

--------------------------------------------------------------------------------------------------------------------------------

Faulting application name: OUTLOOK.EXE, version: 16.0.13328.20292, time stamp: 0x5f976a62

Faulting module name: mso20win32client.dll, version: 0.0.0.0, time stamp: 0x5f925668

Exception code: 0xc0000005

Fault offset: 0x0005c7d4

Faulting process id: 0x6a70

Faulting application start time: 0x01d6bc4271fa08f9

Faulting application path: C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE

Faulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\Office16\mso20win32client.dll

Report Id: b68ac5e5-621c-435d-92cb-182d0771aa6e

Faulting package full name: 

Faulting package-relative application ID: 

 

Steps Taken to Troubleshoot: 

Complete Reinstall ProPlus 64-Bit

Complete Uninstall ProPlus 64-Bit

Complete Install ProPlus 32-Bit

Rolled back the version of Office using officec2rclient.exe /update user updatetoversion=16.0.12827.20470

Complete Uninstall of all Office and Reinstall of 32-Bit

Disabled Hardware Acceleration 

Disabled Add-Ins

Sfc /scannow

dism online cleanup-image restorehealth

Offline Chkdsk repair 

Brand new build of Server 2019 RDS Server with new 32-Bit Office install 

Host Firmware Updates 

Likely more that I cannot think of

 

I attached ProcMon to Outlook.exe to monitor for System.Threading.ThreadAbortException or System.AccessViolationException. 

Today we experienced a crash at 9:01. Here were the exceptions recorded. 

 

[09:01:58] Exception: E06D7363.?AV?$windows_exception_impl@$0A@@@

[09:01:58] Exception: E06D7363.?AVOException@@

[09:01:58] Exception: E06D7363.?AVOException@@

[09:01:59] Exception: E06D7363.?AVOException@@

[09:01:59] Exception: 40080201

[09:01:59] Exception: 40080201

[09:01:59] Exception: 40080201

[09:01:59] Exception: 40080201

[09:01:59] Exception: 40080201

[09:01:59] Exception: E06D7363.?AVJson_exception@Json@Mso@@

[09:01:59] Exception: 40080201

CLR Version: vv4.0.30319

 

[09:02:00] Exception: E0434F4D.System.FormatException ("Input string was not in a correct format.")

[13:57:27] Exception: E0434F4D.System.Threading.ThreadAbortException ("Thread was being aborted.")

[13:57:27] Dump 1 initiated: C:\tools\OUTLOOK.EXE_201124_135727.dmp

[13:57:29] Dump 1 writing: Estimated dump file size is 1317 MB.

0 Replies