Share via

Outlook Login Error

Rachel 0 Reputation points
2026-03-11T21:03:17.1666667+00:00

Can no longer access Outlook. When trying to access Outlook via app, receive the following error:

We couldn't reach the email server. Please try again.

Can log in to Microsoft account on a browser, but receive the following error when trying to access Outlook:

BootResult: fail Back Filled Errors: Unhandled Rejection: SyntaxError: Failed to execute 'json' on 'Response': Unexpected end of JSON input:undefined|undefined:undefined|undefined:undefined|undefined:undefined|Unhandled Rejection: SyntaxError: Failed to execute 'json' on 'Response': Unexpected end of JSON input:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|Unhandled Rejection: SyntaxError: Failed to execute 'json' on 'Response': Unexpected end of JSON input:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined err: AccountTerminationException esrc: StartupData et: ServerError estack: Error: 440     at Object.w [as createStatusErrorMessage] [Moderator note: personal info removed] st: 440 ehk: X-OWA-Error efe: [Moderator note: personal info removed]

Checked the status of the user's account via admin's user management, account shows active.

Outlook | Web | Outlook on the web for business | Sign in
0 comments No comments

2 answers

Sort by: Most helpful
  1. Kristen-L 12,020 Reputation points Microsoft External Staff Moderator
    2026-03-11T22:32:05.6666667+00:00

    Hi @Rachel,

    Thank you for reaching out and sharing the details of the errors you’re seeing in Outlook. I know how disruptive it can be when you’re unable to access email - especially when both the Outlook app and Outlook on the web return different errors.

    Your OWA error trace includes err: AccountTerminationException, along with Error 440 and esrc: StartupData, which typically indicates that the mailbox object itself is disabled, even when the Entra ID (Azure AD) user account still appears active. In these situations, the user can sign in normally at the identity layer, but Exchange Online treats the mailbox as terminated or disabled, preventing Outlook and OWA from loading.

    This also aligns with the Outlook app message, “We couldn’t reach the email server. Please try again,” since the client can’t establish a mailbox session when the mailbox is in a disabled state.

    Below are the actions required on the admin side. Kindly share these instructions with your IT administrator so they can complete the necessary checks:

    1/ Check whether the mailbox is disabled

    Get-Mailbox ******@domain.com | fl AccountDisabled
    

    If the result shows AccountDisabled : True, that matches the behavior indicated by the AccountTerminationException error.

     

     

    2/ Re-enable the mailbox

    Set-Mailbox ******@domain.com -AccountDisabled $false
    

     

    3/ (Optional) Identify any other disabled mailboxes

    Get-Mailbox -ResultSize Unlimited | Where-Object { $_.AccountDisabled -eq $true }
    

    After re-enabling, have the user try signing into Outlook on the web again.

     

    Here are the next steps you can try after your IT administrator completes the checks above:

    A/ Refresh authentication

    • Sign out of all Microsoft sessions
    • Sign back in using https://outlook.office.com/

    User's image

     B/ Clear browser session

    • Try InPrivate/Incognito
    • Or clear cookies for outlook.office.com

    image

     

    C/ For the Outlook app error (“We couldn’t reach the email server”)

    If the mailbox is re-enabled but the desktop client still fails:

    • Remove cached credentials (Windows Credential Manager > Windows Credentials > Generic Credentials > remove Outlook/Office entries)
    • Disconnect and re-add the Work/School account under Windows Settings
    • Restart the device and sign in again

    These steps address cached authentication failures that can persist after mailbox reactivation.

     

    I hope this information helps. Please try the steps and let me know whether they resolve the issue. If the problem persists, we can work together to find a solution.  

    As other users will also search for information in this community, your vote can significantly help those with similar inquiries quickly locate the most relevant resources. 

    Thank you for your kindness and for contributing to the forum.   


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".       

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  2. Q&A Assist
    2026-03-11T21:03:31.09+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The error message includes AccountTerminationException with status code 440, which indicates that the mailbox/account for Outlook on the web has been terminated or blocked on the service side, even though the Azure AD/Microsoft 365 user object still appears as Active in admin user management.

    Because this is a server-side mailbox state, client troubleshooting (reinstalling apps, clearing cache, changing devices, or browsers) will not resolve it. The account must be checked and remediated by an administrator with the appropriate rights in the tenant.

    Recommended actions for the admin:

    1. Verify mailbox status
      • In the Microsoft 365 admin tools, confirm that the user not only exists and is Active, but also has an Exchange Online license assigned.
      • If the license was removed and re-added recently, allow time for provisioning and then test Outlook on the web again.
    2. Check for access restrictions or termination
      • Review any security, compliance, or lifecycle policies that might have soft-deleted, blocked, or terminated the mailbox (for example, account termination workflows, litigation/hold changes, or automated deprovisioning).
      • If the mailbox has been soft-deleted or is in a terminated state, restore or re-enable it according to the organization’s procedures.
    3. Confirm sign-in works outside Outlook
      • Since sign-in to the Microsoft account portal works, focus on Exchange/Outlook service specifically rather than identity sign-in.
    4. If Outlook mobile is also blocked
      • If Outlook for Android or iOS shows an access denied or cannot reach server error and the account is governed by mobile access policies, the account may be blocked for Outlook mobile as well. In that case, the IT admin must review and adjust any conditional access or mobile application management policies that deny Outlook mobile access.
    5. Escalate within the organization
      • If the admin cannot see any obvious reason (license, mailbox state, or policy) for the AccountTerminationException, the issue must be escalated to the organization’s higher-level Microsoft 365/Exchange Online administrators or support channels so they can check the backend mailbox state and remove any termination/block flags.

    End users cannot fix AccountTerminationException themselves; only the IT admin or Microsoft support (via the admin) can restore access.


    References:

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.