Description

I was contacted, by a customer, about this error message when trying to log-in into Outlook Web Access, searching the error doesn’t show up a lot, some people were able to resolve it by clearing the cache of the browser, it wasn’t the case here I would like to share what we did.

Error Message

UTC Date: 2024-10-15T13:17:47.601Z
Client Id: 886589E359584D7CAF66EB4D640B796D
Session Id: 317f815c-7d76-4821-85e1-9575872e3f5c
Client Version: 20241004002.14
BootResult: cdnError
Failed resource: https://res.cdn.office.net/owamail/hashed-v1/resources/locale/es/owa.AppBoot.m.043e9350.json?bO=1
Back Filled Errors: Unhandled Rejection: Error: Failed to load localized strings:undefined|Unhandled Rejection: Error: Failed to load localized strings:undefined|undefined:undefined|undefined:undefined
err: Error: Failed to load localized strings
esrc: InitLoc
et: ClientError
estack: Error: Failed to load localized strings
at d (https://res.cdn.office.net/owamail/hashed-v1/scripts/owa.mailindex.a06faf83.js:1:92952)
at f (https://res.cdn.office.net/owamail/hashed-v1/scripts/owa.mailindex.a06faf83.js:1:92746)

Resolution

I could reproduce the error by opening Browser’s developer tools, selecting the Network tab and using the right-click block domain on the res.cdn.office.net request.

So, it had to be something related to filtering or network, I contacted the network team and they whitelisted res.cdn.office.net.

That made the trick and the error was gone. Hope this is useful for anyone out there.

Leave a comment

tip of the week

When everything else fails, use SysInternals process monitor tool and you will be surprised

~ Me