Microsoft Error Reporting Mac Office 2016

Posted on
Microsoft Error Reporting Mac Office 2016 Rating: 8,9/10 7038 votes

Microsoft Office 2016 Crash Logger Tool

Purpose: Configures the computer to log and archive Office 2016 crash reports
Usage: CrashLogger [--Install] [--Uninstall] [--ViewLog]
Example: CrashLogger --Install

2020-3-7  Skip to main content. 2016-3-22  Microsoft Office Office 2016 for Mac This forum is for general questions and feedback related to Office 2016 for Mac as they pertain to the IT Pro community. 2018-4-16  Excel for Mac error: 'The application Microsoft Excel quit unexpectedly' Content provided by Microsoft. To resolve this problem, use one of the following methods, depending on your version of Office for Mac. Excel 2016 for Mac Step 1: Quit all programs. 2016-6-28  Download Microsoft Junk E-mail Reporting Add-in for Microsoft Outlook® from Official Microsoft Download Center. Transform data into actionable insights with dashboards and reports. Microsoft Junk E-mail Reporting Add-in for Microsoft Outlook®. Requirements for the Junk Reporting Add-in for Office 2007, 2010, 2013.

Section

Microsoft Error Reporting Mac Office 2016

NOTE: CrashLogger requires Microsoft Office 2016 for Mac 15.28 or later

How CrashLogger works
CrashLogger leverages a new ability in Office 2016 15.28 to save the last crash log to disk.
When CrashLogger --Install is run, the following occurs:

  1. The CrashLogger script is copied to $HOME/Library/Application Support/com.microsoft.CrashLogger
  2. A scratch area is created: $HOME/Library/Group Containers/UBF8T346G9.ms/MerpScratch/
  3. An archive area is created: $HOME/Library/Group Containers/UBF8T346G9.ms/MerpArchive/
  4. A LaunchAgent is configured to monitor the creation of new crash reports
  5. MERP crash logging is enabled through defaults write com.microsoft.errorreporting IsStoreLastCrashEnabled -bool TRUE

What happens when an Office application crashes?

Sending Error Report

  1. Microsoft Error Reporting will send the crash report to the Watson server and then persist the log to disk at $HOME/Library/Group Containers/UBF8T346G9.ms/MerpTempItems/LastSentCrashReport.zip
  2. The LaunchAgent will be triggered
  3. The LaunchAgent unzips the crash log, extracts key information, then moves the report to the archive area using a file name based on the date and time of the crash
  4. The LaunchAgent writes a one-line summary of the crash to $HOME/Library/Group Containers/UBF8T346G9.ms/MerpArchive/CrashSummary.txt
  5. The LaunchAgent will send the one-line summary to the console log

Window Problem Reporting

Example of console log entry
11/1/16 7:34:21.943 PM pbowden[60463]: com.microsoft.CrashLogger 2016-11-02 02:34:17 com.microsoft.Excel 15.28.0.161031 SIG_FORCE_QUIT 29c2 CrashReport-161101-193421.txt