SOLVED: Outlook.Office.com – Something Went Wrong – Unhandled Rejection: Error: 500 User Has No Mailbox And No License Assigned Error

Recently a client had a problem opening the Outlook Web Ppp (OWA):

SOMETHING WENT WRONG

BootResult: configuration

Back Filled Errors: Unhandled Rejection: Error: 500:undefined|undefined:undefined
err: Microsoft.Exchange.Clients.Owa2.Server.Core.OwaUserHasNoMailboxAndNoLicenseAssignedException

esrc: StartupData
et: ServerError
estack: Error: 500
at Object.w [as createStatusErrorMessage] (https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mailindex.487dd620.js:1:1040)

at https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mailindex.487dd620.js:1:159827
st: 500
ehk: X-OWA-Error
efe: YT4P288CA0072, YQBPR0101CA0030

emsg: UserHasNoMailboxAndNoLicenseAssignedError

This is telling you the user does not have a mailbox setup or even licensed, but we know that is not true because:

1. We can see the users mailbox configuration in the Exchange Online Management Console
2. Outlook on her cell phone functions without problem
3. We can open OWA successfully using a different browser

How to Fix OWA UserHasNoMailboxAndNoLicenseAssignedError

The first thing to do is close ALL of the browsers and try again.

If that does not work, surf to https://portal.office.com, click the users icon (now in the bottom LEFT of the screen), and select SIGN OUT. The close all browsers and try again.

If that does not work, you will have to do what we had to do. This is an old story but one that just keeps working, clear your cache. In our case we were using Google Chrome / MS Edge:

1. Click the three dots in the top right corner of the browser
2. Click SETTINGS (near the bottom of the menu)
3. Type CACHE into the search bar
4. Click the CHOOSE WHAT TO CLEAR button
5. Set the TIME RANGE to a day that includes the last time it was working
   • in our case, we ended up just selected ALL TIME
6. Accept the defaults by clicking just CLEAR NOW button
   • if you scroll down, you will see that important things like password cache is not cleared)
7. Close ALL browser sessions
8. Try again