{"id":36816,"date":"2025-01-13T00:01:03","date_gmt":"2025-01-12T23:01:03","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=36816"},"modified":"2025-01-14T10:21:13","modified_gmt":"2025-01-14T09:21:13","slug":"microsoft-outlook-365-or-other-ms-365-apps-are-dropping-suddenly-errors","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2025\/01\/13\/microsoft-outlook-365-or-other-ms-365-apps-are-dropping-suddenly-errors\/","title":{"rendered":"Microsoft Outlook 365 or other MS 365 apps are dropping suddenly errors"},"content":{"rendered":"

[German<\/a>]German blog reader Robert contacted me recently by emailed to report that he had run into problems with Outlook and other apps under Microsoft 365 on Windows Server 2016 (and 2019) Terminal Server. Microsoft Outlook, Excel crashes in a certain build, which could be related to an Edge update.<\/p>\n

<\/p>\n

Microsoft Outlook 365 crashes<\/h2>\n

\"\"Robert wrote that he was facing something strange. It's about Microsoft 365 (Build 16.0.18324.20168) and apps like Outlook (or Excel, as he found out later).<\/p>\n

\"Outlook-Absturzmeldung\"<\/a><\/p>\n

If he launches Microsoft Outlook Microsoft Outlook (from Microsoft 365, Current Channel) in the latest version on a customer's WTS (a Windows Terminal Server under Windows Server 2016), an error message appears and Outlook is closed again. It's a German version of Microsoft 365, as you can see on the following screenshot, that says \"Microsoft Outlook doesn't work, a problem prevented to execute the program\".<\/p>\n

\"Fehlermeldung<\/p>\n

If he launches Microsoft Outlook 365 in the suggested safe mode, he receives a more detailed error message.<\/p>\n

\"Ausf\u00fchrliche<\/p>\n

The message reports, that the file react-native-win32.dll<\/em> was not found in the specified path. This suggested that something had entered the wrong path or deleted the .dll file. When Robert checked the system, the offending file was found in the correct location and was the same version as on his Windows 10 computer.<\/p>\n

\"Ordner<\/p>\n

That was strange. The only change that the reader could see was an update of Microsoft Edge to version 130.0.2849.142 (official build, stable app, extended channel, 64-bit). Webview2 had not been updated yet, Robert wrote. A new installation, even with freshly downloaded installation files, and a restart of the WTS did not help. The following entry was found in the event log:<\/p>\n

Name der fehlerhaften Anwendung: OUTLOOK.EXE, Version: 16.0.18324.20168, Zeitstempel: 0x67782e8d<\/p>\n

Name des fehlerhaften Moduls: mso20win32client.dll, Version: 0.0.0.0, Zeitstempel: 0x675b7486<\/p>\n

Ausnahmecode: 0x201c24a0
\nFehleroffset: 0x001bda04
\nID des fehlerhaften Prozesses: 0x2690<\/p>\n

Faulting application start time: 0x01db6414ae82343f<\/p>\n

Faulting application path: C:\\Program Files (x86)\\Microsoft Office\\root\\Office16\\OUTLOOK.EXE<\/p>\n

Faulting module path: C:\\Program Files (x86)\\Common Files\\Microsoft Shared\\Office16\\mso20win32client.dll<\/p>\n

Report identifier: eefe039c-d007-11ef-bdfe-000c29ac047d<\/p>\n

Full name of faulting package:<\/p>\n

Application ID relative to faulting package: …<\/p><\/blockquote>\n

During further diagnostic steps, Robert discovered that Microsoft Excel 365 suddenly stopped working and left the following entry in the Event Viewer.<\/p>\n

Faulting application name: EXCEL.EXE, version: 16.0.18324.20168, time stamp: 0x67782fb2<\/p>\n

Faulting module name: KERNELBASE.dll, version: 10.0.14393.7513, time stamp: 0x67171aad<\/p>\n

Exception code: 0xc06d007e<\/p>\n

Error offset: 0x000dd562<\/p>\n

Faulting process ID: 0x5f8<\/p>\n

Faulting application start time: 0x01db64152e395a8c<\/p>\n

Faulting application path: C:\\Program Files (x86)\\Microsoft Office\\root\\Office16\\EXCEL.EXE<\/p>\n

Faulting module path: C:\\Windows\\System32\\KERNELBASE.dll<\/p>\n

Report ID: 77c7e2bc-d008-11ef-bdfe-000c29ac047d<\/p>\n

Full name of the faulty package:<\/p>\n

Application ID relative to the faulty package:<\/p><\/blockquote>\n

At this point it was clear that an update of a component was causing this error.<\/p>\n

A downgrade helps<\/h2>\n

In a third email, Robert then provided a solution to the problem that had occurred. He managed to install the previous version .20162 of Microsoft 365. Try the following command:<\/p>\n

\"C:\\Program Files\\Common Files\\microsoft shared\\ClickToRun\\OfficeC2RClient.exe\" \/update user updatetoversion=16.0.18227.20162<\/pre>\n
After that, everything seems to be working again. The reader notes that it looks like the latest Microsoft 365 feature update to build .20168 is faulty and does not work, at least on Windows Server 2016.<\/p>\n
Confirmed by Microsoft<\/h2>\n
Addendum:<\/strong> Microsoft has confirmed that they are investigating the issue in MS Service Health Portal, Message ID MO978220.<\/p>\n
Some users' Microsoft 365 applications may be unexpectedly crashing on Windows Server 2016 devices<\/p>\n
Problem-ID: MO978220
\nAffected services: Microsoft 365 suite
\nStatus: Service impairment
\nProblem type: Note
\nStart time: Jan 13, 2025, 09:56 MEZ<\/p>\n
User impact
\nUsers' Microsoft 365 applications may be unexpectedly crashing on Windows Server 2016 devices.<\/p>\n
Scope of impact
\nImpact is specific to some users who are served through the affected infrastructure.<\/p>\n
Current status
\n13. Jan. 2025, 11:45 MEZ
\nWe're continuing to review service monitoring telemetry to isolate the root cause and develop a remediation plan.
\nNext update by:
\nMonday, 13. Januar 2025 14:00 MEZ<\/p><\/blockquote>\n
Addendum:<\/strong> It's also confirmed for Windows Server 2019 WTS.\u00a0A German blog reader pointed to the article\u00a0Microsoft Outlook 365 wirft pl\u00f6tzlich Fehler und st\u00fcrzt ab (Windows Server 2016 RDS)<\/a>. This guy confirmed, the issue is caused by an Edge update that changed the file react-native-win32.dll<\/em>. He was able to use an old version to keep Office 365 to run again. But it's risky to exchange an .dll within a system, especially, if the .dll is from a 3rd party source. It's better to use the .dll from an old backup.<\/p>\n","protected":false},"excerpt":{"rendered":"
[German]German blog reader Robert contacted me recently by emailed to report that he had run into problems with Outlook and other apps under Microsoft 365 on Windows Server 2016 (and 2019) Terminal Server. Microsoft Outlook, Excel crashes in a certain … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,11],"tags":[78,47,1805,395],"class_list":["post-36816","post","type-post","status-publish","format-standard","hentry","category-issue","category-office","tag-app","tag-issue","tag-microsoft-365","tag-outlook"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/36816","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=36816"}],"version-history":[{"count":7,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/36816\/revisions"}],"predecessor-version":[{"id":36834,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/36816\/revisions\/36834"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=36816"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=36816"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=36816"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}