I have a customer for whom this is a real pain point so hopefully this will help some of you.
They have an RDS environment with Office 365 (Office 2013) click-to-run. Outlook 2013 for them started crashing all over the place.
We were getting this event in the application logs on all RD Session Host servers:
Log Name: Application
Source: Application Error
Date: 5/4/2016 3:28:41 PM
Event ID: 1000
Task Category: (100)
Faulting application name: OUTLOOK.EXE, version: 15.0.4815.1000, time stamp: 0x56e79eae
Faulting module name: ntdll.dll, version: 6.3.9600.18194, time stamp: 0x569515fc
Exception code: 0xc0000005
Fault offset: 0x0001dd93
Faulting process id: 0x58fc
Faulting application start time: 0x01d1a629442c57ad
Faulting application path: C:\Program Files\Microsoft Office 15\root\office15\OUTLOOK.EXE
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 67ec2891-122e-11e6-8184-00505693f4fd
Faulting package full name:
Faulting package-relative application ID:
And here is the problem: Lync 2013 (Skype for Business) or Outlook 2013 Crash
The fix for us (we use Click-to-Run) was to revert back to an earlier version, the March version.
Here is the link to walk you through that process: How to revert to an earlier version of Office 2013 or Office 2016 Click-to-Run.
From that article:
Determine and note the previous version number. Use the following Microsoft website to find the update version that is previous to the current version:
Microsoft Office 2013 Click-to-Run update
The march update is:
Release: March 2016 Update
We presently have version:
Release: April 2016 Update
you also need to know the bit level of the OS (check that article above if you don’t know yours) – ours is x64.
So these are the commands we ran to revert:
At an elevated Command Prompt window:
cd %programfiles%\Microsoft Office 15\ClientX64
officec2rclient.exe /update user updatetoversion=15.0.4805.1003
When the repair dialog box appears, click Online Repair.
Click Repair, and then click Repair again.
Note If you are prompted to activate Office again, enter your Microsoft account and password. This step does not add your computer to your account a second time.
So far things look a ton better.
I will update this article with any further event IDs that this solves / creates, or any new developments.
Upon this fix, we have also observed that the following two errors in the Event logs have mysteriously vanished as well:
- Event ID 2011 – Office Subscription licensing exception: Error Code: 0x803D0010
- Event ID 25 – Network problems are preventing connection to Microsoft Exchange