{"id":236652,"date":"2020-10-17T12:00:04","date_gmt":"2020-10-17T10:00:04","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=236652"},"modified":"2020-10-18T00:46:32","modified_gmt":"2020-10-17T22:46:32","slug":"strung-exchange-online-onedrive-for-business-8-und-16-10-2020","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2020\/10\/17\/strung-exchange-online-onedrive-for-business-8-und-16-10-2020\/","title":{"rendered":"Störung: Exchange Online, OneDrive for Business (8. und 16.10.2020)"},"content":{"rendered":"

[English<\/a>]Microsofts Online-Dienste Exchange Online (Vorfall: EX224266 vom 8.10.2020), sowie OneDrive for Business in Verbindung mit SharePoint Online (Vorfall OD224379 vom 16. Oktober 2020) waren\/sind von einer St\u00f6rung betroffen. Kurzer \u00dcberblick, was Microsoft dort an Informationen bereitstellt.<\/p>\n

<\/p>\n

\"\"Blog-Leser Andreas P. hat mir gerade die betreffenden Statusmeldungen aus dem Administrator-Dashboard bereitgestellt (danke daf\u00fcr). Auf Twitter hat @MSFT365Status noch nichts gepostet.<\/p>\n

EX224266: St\u00f6rung Exchange Online seit 8.10.2020<\/h2>\n

Manche Nutzer von Exchange Online k\u00f6nnen seit dem 8. Oktober 2020 keine E-Mails mehr versenden, da sie eine Fehlermeldung wegen einer Quota-\u00dcberschreibtung erhalten. Zum 16. Oktober 2020 gibt Microsoft folgende Details der Fehlermeldung \"Message can't be submitted because the sender's submission quota was exceeded\" in Exchange Online bekannt. Die obige Nachricht erscheint ggf. beim Versenden von Nachrichten. Den nachfolgenden Statusmitteilungen zufolge gibt es diese St\u00f6rung seit dem 8. Oktober 2020.<\/p>\n

Published Time: 16.10.2020 18:55:49
\nTitle: Some users may be unable to send email messages
\nUser Impact: Users may receive a Non-Delivery Report (NDR) when attempting to send email messages.
\nMore info: The NDR error message reads \"Message can't be submitted because the sender's submission quota was exceeded\".
\nCurrent status: We're continuing to deploy the fix to the affected environment and will provide a timeline for complete saturation as soon as one becomes available.
\nScope of impact: A small number of users may be impacted by this issue.
\nStart time: Thursday, October 8, 2020, at 2:54 PM UTC
\nRoot cause: A recent service update inadvertently caused an issue where sent emails are being miscounted, resulting in users being unable to send email messages.<\/p><\/blockquote>\n

Laut Microsoft sind nur wenige Nutzer betroffen und Microsoft war an diesem Fehler seit einigen Tagen dran. Am 15. Oktober 2020 wurde ein Update der Exchange Online-Funktionen versprochen. Die Ursache benennt Microsoft folgenderma\u00dfen:<\/p>\n

We've determined that a recent service update inadvertently caused an issue where sent emails are being miscounted, resulting in users being unable to send email messages. We've raised sending limits for some users and confirmed that this has resolved impact. In parallel, we're working to formulate potential mitigation actions, including a code fix.<\/p><\/blockquote>\n

Im Rahmen einer Diensteaktualisierung (Update) wurde ein Fehler eingebaut. Exchange Online hat dann\u00a0 gesendete E-Mails falsch gez\u00e4hlt. Das f\u00fchrte dazu, dass Benutzer keine E-Mail-Nachrichten senden konnten (deren Quota war \u00fcberschritten). Microsoft hat dann die Sendebeschr\u00e4nkungen f\u00fcr betroffene Benutzer erh\u00f6ht und best\u00e4tigt, dass dies den Fehler behoben hat. Man versprach potenzielle Abhilfema\u00dfnahmen, einschlie\u00dflich einer Codekorrektur.<\/p>\n

W\u00e4hrend der Entwicklung der Korrektur entdeckten die Microsoft Leute ein nicht damit zusammenh\u00e4ngendes Problem, das sich auf den Einsatz der Testumgebung auswirken w\u00fcrde. Daher dauerte die \u00dcberarbeitung der Korrektur etwas l\u00e4nger. Das Problem wurde zwar am 8. Oktober 2020 durch einen Fix behoben. Zum 16.10.2020 schreibt Microsoft aber:<\/p>\n

Current status: We're continuing to deploy the fix to the affected environment and will provide a timeline for complete saturation as soon as one becomes available.<\/p><\/blockquote>\n

So ganz ist das Problem scheinbar noch nicht behoben.<\/p>\n

OD224379: St\u00f6rung OneDrive for Business seit 16.10.2020<\/h2>\n

Seit dem 16.10.2020 kommt es zu einer Dienstbeeintr\u00e4chtigung im Umfeld von SharePoint Online in Verbindung mit OneDrive for Business. Die Synchronisation der SharePoint Online Team Site Bibliotheken (Libraries) mit OneDrive for Business klappt nicht. Microsoft gibt folgende Statusinfos bekannt.<\/p>\n

Published Time: 17.10.2020 03:18:08
\nTitle: Some users may be unable to sync SharePoint Online team site libraries with OneDrive for Business
\nUser Impact: Users may be unable to sync SharePoint Online team site libraries with OneDrive for Business.
\nMore info: This issue only affects users who are using the classic experience. If possible, we recommend users utilize the modern experience, as it is unaffected by this issue. Additional information about experiences can be found here: https:\/\/support.microsoft.com\/en-us\/office\/sharepoint-classic-and-modern-experiences-5725c103-505d-4a6e-9350-300d3ec7d73f
\nCurrent status: We've completed our validation of the fix and we're initiating our deployment procedures to the affected environment to resolve the issue. We'll monitor its progress throughout the weekend and we'll provide a deployment update by the next update time.
\nScope of impact: This event impacts users attempting to sync SharePoint Online team site libraries with OneDrive for Business within the classic experience.
\nPreliminary root cause: A recent change inadvertently affected the validation of specific Globally Unique Identifiers (GUIDs) which is preventing users from syncing SharePoint Online team site libraries with OneDrive for Business.
\nNext update by: Monday, October 19, 2020, at 10:00 PM UTC<\/p><\/blockquote>\n

Die Erstmeldung erfolgte zum 16.10.2020 02:23:07 Uhr Zeit mit folgender Statusinformation:<\/p>\n

Title: Some users may be unable to sync SharePoint Online team site libraries with OneDrive for Business
\nUser Impact: Users may be unable to sync SharePoint Online team site libraries with OneDrive for Business.
\nCurrent status: We've determined that a recent change inadvertently affected the validation of specific Globally Unique Identifiers (GUIDs) which is preventing users from syncing SharePoint Online team site libraries with OneDrive for Business. We're developing a fix that we expect will remediate impact and will provide an estimated timeline for deployment with our next update.
\nScope of impact: This event may impact some users attempting to sync SharePoint Online team site libraries with OneDrive for Business.
\nRoot cause: A recent change inadvertently affected the validation of specific Globally Unique Identifiers (GUIDs) which is preventing users from syncing SharePoint Online team site libraries with OneDrive for Business.<\/p><\/blockquote>\n

Irgend jemand von euch betroffen?<\/p>\n

Erg\u00e4nzung: Auf Twitter hat @MSFT365Status eine neue St\u00f6rung MO224459<\/a> f\u00fcr Microsoft 365 gepostet. Das Admin-Center von Microsoft 365 ist nicht erreichbar. Antwort eines genervten Kunden<\/a>:<\/p>\n

I am beginning to move my clients away from 365. I have also started suggesting my larger corporate users move away as well. MS has proven over the last 3 weeks that testing in production, poor maintenance, and an inability to answer support requests are the new M.O.<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"

[English]Microsofts Online-Dienste Exchange Online (Vorfall: EX224266 vom 8.10.2020), sowie OneDrive for Business in Verbindung mit SharePoint Online (Vorfall OD224379 vom 16. Oktober 2020) waren\/sind von einer St\u00f6rung betroffen. Kurzer \u00dcberblick, was Microsoft dort an Informationen bereitstellt.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7263,7862],"tags":[1171,672,987],"class_list":["post-236652","post","type-post","status-publish","format-standard","hentry","category-cloud","category-stoerung","tag-cloud","tag-microsoft","tag-storung"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/236652","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/comments?post=236652"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/236652\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=236652"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=236652"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=236652"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}