Share via

Server Error Code while trying to access Outlook

Anonymous
2023-06-27T18:10:03+00:00

I'm getting the following error while trying to access my Outlook. This is from multiple devices on chrome browser. I have cleared the cache/cookies/browser data and am still receiving this.

UTC Date: 2023-06-27T18:06:26.710Z Client Id: D4EDF29388E8482EA5A9CED94392FDD6 Session Id: 271f5503-c275-446e-815e-c26964f05413 Client Version: 20230609005.14 BootResult: fail Back Filled Errors: None err: System.TypeLoadException esrc: StartupData et: ServerError estack: Error: 500 at Object.b [as createStatusErrorMessage] (https://res-h3.public.cdn.office.net/owamail/20230609005.14/scripts/owa.mailindex.js:2:265154) at https://res-h3.public.cdn.office.net/owamail/20230609005.14/scripts/owa.mailindex.js:2:264316 st: 500 ehk: X-OWA-Error efe: CH0P223CA0016 ebe: CH0PR20MB4011 ewsver: 15.20.6521.31 emsg: ErrorUnexpectedFailure

Microsoft 365 and Office | Subscription, account, billing | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-06-27T19:26:44+00:00

    Dear Emily Jones1

    Good day! Thank you for posting to Microsoft Community. We are happy to help you!

    I'm sorry for the inconvenience this has caused. I've checked from my side, this is a known issue, there is currently some different Service incidents for issues while trying to access Outlook web.

    =======================================================================================

    1. Incident SI: EX610644

    Title: Some users may be unable to access their Exchange Online mailbox using Outlook on the web

    User impact: Users may be unable to access their Exchange Online mailbox using Outlook on the web.

    Current status: We're reviewing service monitoring telemetry to isolate the root cause and determine the next mitigation steps.

    Scope of impact: Impact is specific to some users who are served through the affected infrastructure attempting to access their Exchange Online mailbox using Outlook on the web.

    =========================================================================================

    1. Incident SI: EX609725

    Title: Users can't access Outlook for the web using a specific vanity URL

    User impact: Users can't access Outlook for the web using a specific vanity URL.

    More info: Affected users may see the following error:

    "500: Something went wrong."

    Where possible, users can bypass impact by accessing the Outlook for the web service directly via "outlook.office.com", or by leveraging the Outlook desktop or mobile apps.

    Current status: After reviewing associated logs, we see a behavior occurring where during the authentication process, users are redirected from the vanity URL back to the original domain name, which results in the access request being denied. We're continuing to investigate what is causing this behavior and reviewing potential remediating actions.

    Scope of impact: Your organization is affected by this event, and any user attempting to access Outlook for the web using the affected vanity URL is impacted.

    You can view current information and updates on Service health dashboard at the link here https://portal.office.com/servicestatus. For affected customers to easily identify the information here, this thread will be closed. You may subscribe to this thread or refer to SHD for updated information. If a new update is available for the resolved or restored status, I will update the web page address in this thread accordingly.

    We apologize for any inconvenience this may cause and appreciate your patience and understanding.

    Sincerely,

    Kerry Chen | Microsoft Community Moderator

    Was this answer helpful?

    0 comments