Outlook Internal Exchange Error 80000000

Hallo Christopher,
<br />Kannst du dich problemlos in OWA (https://outlook.office.com) anmelden und bekommst du eine Fehlermeldung?
<br />Besteht das Problem auch bei anderen Benutzern in deiner Organisation oder nur bei dir.
<br />Du kannst auch SARA Programm durchlaufen und prüfen, ob du eine Fehlermeldung bekommst.
<br />Mit freundlichen Grüssen
<br />Galin Karlov
<br />Microsoft 365 Support Engineer
<br />

Hallo Christopher,
<br />Hast du SARA Programm durchgelaufen und geprüft, ob Fehler auftauchen.
<br />Du kannst auch ein neues Outlook Testprofil erstellen.
<br />Mit freundlichen Grüssen
<br />Galin Karlov
<br />Microsoft 365 Support Engineer
<br />

Hallo Galin,
<br />in OWA kann ich mich problemlos anmelden, auch über die Outlook Android App keine Problene.
<br />Das Problem besteht bei 2 Leuten in meiner Organisation, andere wiederrum haben das Problem nicht.
<br />Sara konnte leider nicht weiterhelfen :-(
<br />Danke für die Hilfe!
<br />

<br />

Hallo Wolf, danke für die schnelle Antwort. Der Helathstatus bei Sharepoint ist offensichtlich in Ordnung. Hier sind alle Haken auf Grün und das seit Tagen - das Problem beschäftigt uns jetzt allerdings schon drei Tage.

Es wurden unterschiedliche Rechner und unterschiedlich Browser ausprobiert - bei den es bislang immer geklappt hat. Safari, Internet Explorer, Chrome, Edge und Firefox (jeweils in den neuesten Varianten. Es wurden unterschiedliche Rechner und Betriebssysteme
ausprobiert.

Die Angelegenheit sieht so aus;

Man loggt sich ein in die Gruppe, die Unterhaltung ist sichtbar und wenn ich den Dateien Link betätige wird die Seite geladen:

und direkt danach wird auf eine internal error-Seite umgeleitet.

Und das interessante ist, das manche Kollegen diese Problem nicht haben - am gleichen Rechner. Ich logge mich als ein und habe das Problem nicht und am gleichen Rechner lass yyytaucht das Problem auf.

Wie gesagt die Dienst scheinen alle im grünen Bereich zusein. Hier die Info:

Post Incident Review Report

For

Office 365

Report Date: August 16, 2016

Report By: ICC

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not
be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.

MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.

Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted
in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft,
the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

The descriptions of other companies’ products in this document, if any, are provided only as a convenience to you. Any such references should not be considered an endorsement or support by Microsoft. Microsoft cannot guarantee
their accuracy, and the products may change over time. Also, the descriptions are intended as brief highlights to aid understanding, rather than as thorough coverage. For authoritative descriptions of these products, please consult their respective manufacturers.

© 2016 Microsoft Corporation. All rights reserved. Any use or distribution of these materials without express authorization of Microsoft Corp. is strictly prohibited.

Microsoft and Windows are either registered trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Office 365 Customer Ready Post Incident Review


Incident Information
[table][tr][td]Incident ID [/td][td]SP75032 [/td][/tr][tr][td]Incident Title [/td][td]SharePoint Online admin features issue [/td][/tr][tr][td]Service(s) Impacted [/td][td]SharePoint Online [/td][/tr][/table]

User Impact

Users may have been unable to perform some administrative functions (e.g., updating site resource quotas and creating new site collections). Additionally, admins may have been unable to run PowerShell commands.

Scope of Impact
A few customers reported this issue, and our analysis indicated that this issue may have potentially impacted any of your users attempting to use the affected features.

Incident Start Date and Time
August 15, 2016, at 5:56 PM UTC

Incident End Date and Time
August 15, 2016, at 7:58 PM UTC

Root Cause
An update intended to improve the data storage service caused impact to the availability of specific administrative features.

Actions Taken (All times UTC)
August 15, 2016

5:56 PM – The incident began.

7:10 PM – Engineers investigated the issue, they confirmed impact to end users, and they initiated a high-priority investigation.

7:45 PM – Our investigation determined that an update intended to improve the data storage service caused impact to the availability of specific administrative features. Engineers began to revert the update to restore service.

7:58 PM – Engineers completed the process of reverting the update and they confirmed that service was restored. The incident was resolved.

Next Steps
[table][tr][td]An update intended to improve the data storage service caused impact to the availability of specific administrative features.[/td][td]Review and revise the service update process to prevent a recurrence of this scenario.[/td][td]September 2016 [/td][/tr][tr][td]This event was reported by customers before a communication was published on the Service Health Dashboard.[/td][td]Review the monitoring infrastructure for improvements. [/td][td]September 2016 [/td][/tr][/table]



Schon einmal herzlichen Dank für deine Idee.

Gruß Rudi

Lieber Rudolf Bergers,



Kann ich Ihnen weiter behilflich sein?

Freue mich auf Ihre Rückmeldung.



Mit freundlichen Grüßen,

Wolf Fabian Spohr

Microsoft Office 365 Support Engineer.