Error message when trying to access Outlook.com

Topic

New Reply

I’m posting this here because I can’t really be sure if this on Microsoft’s end or mine.

I will say though that no other site I’ve been on has thrown any errors

Since Thursday every time I try to access Outlook I get this error message after entering my email and password

UTC Date: 2023-11-11T17:02:35.206Z
Client Id: BBA23F1F13D2426BB4B00517E73DE934
Session Id: e347a763-ea14-42d6-ad3c-bf4dd26c5a26
Client Version: 20231103003.14
BootResult: network
Back Filled Errors: None
err: NetworkError: A network error occurred.
esrc: Runtime
et: ClientError

I don’t know enough about these things to know what I’m reading, so if someone could explain this, I’ be grateful.

Reply | Quote

Replies

If you have the web based  Outlook you have to clean out your cache.

Reply | Quote

In that case, I may have a problem then because I do that every time I close my browser

Reply | Quote

Ping or tracert outlook.com and see if you reach the servers.

Reply | Quote

how do I do that?

Reply | Quote

Something I didn’t mention in the original post is that after a few seconds the page will automatically reload and the inbox itself will load none of the buttons are clickable and no emails will open.

The only way to get out is to exit the page or close the browser.

Reply | Quote

Moonbear wrote:

how do I do that?

Type CMD in the search box.
In the window the opens type Tracert outlook.com
You will get a list of servers (IPs) the your request passes on its way to Microsoft’s outlook servers.

Copy and past it here.

1 user thanked author for this post.

Steve

Reply | Quote

Ok, for a second I didn’t think I was gong to be able to copy this, but here it is

 

C:\Users\PC>tracert outlook.com

Tracing route to outlook.com [52.96.172.98]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms home [192.168.1.254]
2 32 ms 34 ms 36 ms adsl-75-49-19-254.dsl.wotnoh.sbcglobal.net [75.4
9.19.254]
3 34 ms 35 ms 36 ms 12.83.38.82
4 43 ms 44 ms 44 ms 32.130.17.249
5 43 ms 44 ms * 32.141.192.2
6 43 ms 46 ms 50 ms ae35-0.icr01.ch4.ntwk.msn.net [104.44.237.19]
7 66 ms 64 ms * be-120-0.ibr02.ch4.ntwk.msn.net [104.44.11.22]
8 65 ms 64 ms 66 ms be-11-0.ibr02.cle30.ntwk.msn.net [104.44.29.44]

9 163 ms 66 ms 66 ms be-8-0.ibr04.bl7.ntwk.msn.net [104.44.28.120]
10 65 ms 64 ms 66 ms be-12-0.ibr04.bn6.ntwk.msn.net [104.44.29.26]
11 65 ms 64 ms 64 ms ae172-0.icr07.bn6.ntwk.msn.net [104.44.32.155]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 62 ms 64 ms 62 ms 52.96.172.98

Trace complete.

Reply | Quote

UTC Date: 2025-03-10T15:39:27.135Z
Client Id: E29B35AA40444A318E6ABAAA40D76183
Session Id: e8e709f0-bcc3-40d7-ac94-07e6c1408aaf
Client Version: 20250228007.06
BootResult: fail
Back Filled Errors: Unhandled Rejection: SyntaxError: Unexpected end of JSON input:undefined|Unhandled Rejection: Error: 440:undefined|undefined:undefined|undefined:undefined
err: Error: 440
esrc: StartupData
et: ServerError
estack: Error: 440
    at Object.s [as createStatusErrorMessage] (https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mailindex.9eace4bd.js:1:142455)
    at https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mailindex.9eace4bd.js:1:154851
st: 440
efe: SJ2PR07CA0014, MW4P220CA0024
ebe: SJ2PR17MB6544

Reply | Quote

Are you asking for help? More info please.

cheers, Paul

Reply | Quote

Is there any reason to think that using uBlock Origin may have something to do with this?

Late last year I had a situation similar to this where ublock was blocking one of the things outlook needed to fully load, I set that to noop and everything worked again.

This time nothing new has been blocked that I can see but I want to cover all my bases.

Reply | Quote

You can disable U block and try it without  U block.   Go in and see what other

add On’s you have and if you don’t recognize any of them delete them.

Reply | Quote

uBlock does appear to be the problem, disabling it let Outlook load normally.

Now I just to figure out why this started happening.

2 users thanked author for this post.

Steve, Alex5723

Reply | Quote