{"id":283428,"date":"2023-07-07T04:36:49","date_gmt":"2023-07-07T02:36:49","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=283428"},"modified":"2023-07-07T04:48:00","modified_gmt":"2023-07-07T02:48:00","slug":"outlook-com-suche-gestrt6-7-juli-2023-ms-teams-bug-seit-ende-mrz-2023","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2023\/07\/07\/outlook-com-suche-gestrt6-7-juli-2023-ms-teams-bug-seit-ende-mrz-2023\/","title":{"rendered":"Outlook.com-Suche gestört;(6.\/7. Juli 2023); MS Teams-Bug "doppelte Kontakte" seit Ende März 2023 ungefixt"},"content":{"rendered":"

[English<\/a>]Microsoft k\u00e4mpft in den letzten Stunden (6. \/ 7. Juli 2023) mit diversen St\u00f6rungen seiner Cloud-Infrastruktur. Vor Stunden war die Suche in Outlook.com kaputt – Ursache war wohl ein fehlerhaftes Update. Und aktuell meldet die Statusanzeige Probleme mit Microsoft Teams private.<\/p>\n

<\/p>\n

Outlook.com-Suche kurzzeitig gest\u00f6rt<\/h2>\n

\"\"Nutzer von Outlook.com wurden vor Stunden bei der Suche nach Mails mit der kryptischen Fehlermeldung 401 und dem Fehlertext: Sorry, something went wrong. Please try again later. <\/em>begr\u00fc\u00dft. Sowohl Bleeping Computer<\/a> als auch neowin.net<\/a> haben dieses (inzwischen wohl gel\u00f6ste) Problem aufgegriffen.<\/p>\n

\"outlook.com<\/p>\n

Im Statusbereich findet sich seit dem 5. Juli 2023 der nachfolgende St\u00f6rungseintrag, der dann zum 6. Juli 2023 durch Microsoft als \"gel\u00f6st\" gekennzeichnet wurde:<\/p>\n

Title: Users can't search using keywords in Outlook.com<\/p>\n

User impact: Users couldn't search using keywords in Outlook.com.<\/p>\n

More info: When attempting to search, users were receiving an error which stated \"Sorry, something went wrong. Please try again later.\"<\/p>\n

Final status: Our further analysis into the 401 exception errors has identified a recent service update which had introduced a configuration issue that prevented users' keyword searches in Outlook.com. After reverting the offending service update, we've validated that impact has been remediated.<\/p>\n

Start time: Wednesday, July 5, 2023, at 7:00 PM UTC<\/p>\n

End time: Thursday, July 6, 2023, at 8:30 AM UTC<\/p>\n

This is the final update for this event.<\/p>\n

Title: Users can't search using keywords in Outlook.com<\/p>\n

User impact: Users can't search using keywords in Outlook.com.<\/p>\n

More info: When attempting to search, users receive an error which states \"Sorry, something went wrong. Please try again later.\"<\/p>\n

Current status: We're continuing to investigate into the 401 exception errors to confirm the source generating these errors and determine a plan to remediate impact.<\/p>\n

Next update by: Thursday, July 6, 2023, at 7:30 PM UTC<\/p>\n

Title: Users can't search using keywords in Outlook.com<\/p>\n

User impact: Users can't search using keywords in Outlook.com.<\/p>\n

More info: When attempting to search, users receive an error which states \"Sorry, something went wrong. Please try again later.\"<\/p>\n

Current status: Our initial review of Outlook.com server logs, in parallel with HTTP Archive format (HAR) logs captured during an internal reproduction of impact, indicates 401 errors are occurring due to an exception when users attempt to perform the search. We're continuing to investigate to confirm the source generating these exception errors and determine methods to remediate impact.<\/p>\n

Next update by: Thursday, July 6, 2023, at 2:30 AM UTC<\/p>\n

Title: Users can't search using keywords in Outlook.com<\/p>\n

User impact: Users can't search using keywords in Outlook.com.<\/p>\n

More info: When attempting to search, users receive an error which states \"Sorry, something went wrong. Please try again later.\"<\/p>\n

Current status: We've identified an issue is occurring affecting users' ability to search using keywords in Outlook.com, and are reviewing Outlook.com service logs to identify potential sources of impact for further troubleshooting.<\/p>\n

Next update by: Thursday, July 6, 2023, at 12:30 AM UTC<\/p><\/blockquote>\n

Die Suche nach Schl\u00fcsselw\u00f6rter war in Outlook.com war also ausgefallen. Nach einer internen Untersuchung des Fehlers 401 teilte Microsoft mit, dass ein k\u00fcrzlich durchgef\u00fchrtes Dienstupdate zu einem Konfigurationsproblem f\u00fchrte. Dadurch wurde die Suche nach Schl\u00fcsselw\u00e4rtern in Outlook.com verhindert. Das problematische Service-Update wurde r\u00fcckg\u00e4ngig gemacht, so dass die Auswirkungen des Bugs behoben wurden. Der Dienst sollte inzwischen wieder sauber laufen.<\/p>\n

MS Teams Consumer: Bug seit Monaten ungefixt<\/h2>\n

Als ich beim Schreiben des Beitrag die Statusseite des Office-Portals<\/a> von Microsoft besucht habe, stie\u00df ich zwar auf den Hinweis, dass Outlook.com st\u00f6rungsfrei arbeitet. Aber das Portal meldete \"Wir haben Probleme\" und zeigte folgende \u00dcbersicht.<\/p>\n

\"MS<\/p>\n

Bei Microsoft Teams Consumer schreibt Redmond, dass die Kontaktlisten der Benutzer doppelt vorl\u00e4gen. Der Fehler tauchte in den Statusmeldungen erstmals am 28. M\u00e4rz 2023 auf, ist bisher aber nicht behoben. Microsoft schreibt dazu:<\/p>\n

Title: Users' contact lists are duplicated<\/p>\n

User impact: Users' contact lists are duplicated.<\/p>\n

More info: This issue only impacts users who synced their personal account device contacts with Microsoft Teams. New syncs are no longer resulting in duplicate contacts since we've implemented the long-term fix.<\/p>\n

To remove the duplicate contacts created by this issue prior to the completion of our long-term cleanup process, affected users can use the workaround described here: https:\/\/answers.microsoft.com\/en-us\/outlook_com\/forum\/all\/workaround-for-outlookcom-users-experiencing\/d58d75c2-76a9-4176-b907-333ddfa44952<\/p>\n

We'd like to get your feedback on the workaround we provided. From a non-mobile device, please rate this post and submit it in the textbox.<\/p>\n

Current status: We've identified an issue with the cleanup solution while validating it in our testing environments. Deployment to the affected infrastructure will be delayed as we fix that issue, so we're determining the new estimated deployment timeline. Affected users can manually remove the duplicate contacts before our cleanup process is complete by following the instructions in the workaround article linked above.<\/p>\n

Start time: Tuesday, March 28, 2023, at 12:00 PM UTC<\/p>\n

Next update by: Friday, July 7, 2023, at 6:00 AM UTC<\/p><\/blockquote>\n

Es ist ein l\u00e4stiger Bug, der wohl bei Leuten mit vielen Kontakten durch Doubletten nervt, aber die MS Teams-Funktionalit\u00e4t als solches nicht beeintr\u00e4chtigen d\u00fcrfte. Trotzdem ist es \u00fcberraschend, dass der Fehler so lange nicht korrigiert wurde. Dazu f\u00e4llt mir nur ein \"Gut Ding will Weile haben\" ein.<\/p>\n","protected":false},"excerpt":{"rendered":"

[English]Microsoft k\u00e4mpft in den letzten Stunden (6. \/ 7. Juli 2023) mit diversen St\u00f6rungen seiner Cloud-Infrastruktur. Vor Stunden war die Suche in Outlook.com kaputt – Ursache war wohl ein fehlerhaftes Update. Und aktuell meldet die Statusanzeige Probleme mit Microsoft Teams … Weiterlesen →<\/span><\/a><\/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,4359,987,5595],"class_list":["post-283428","post","type-post","status-publish","format-standard","hentry","category-cloud","category-stoerung","tag-cloud","tag-outlook-com","tag-storung","tag-teams"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/283428","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=283428"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/283428\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=283428"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=283428"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=283428"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}