[outages] [EXTERNAL] login screen errors

[Jay R. Ashworth]

Well, I kept beating on it meanwhile, and it looks like customer "unplugged
all the cables for the storm"... and plugged the ETH1 cable for their PDC...

back into the DHCP ETH2 jack, and nobody could get DNS either.  Redherring,
cause Screen Connect apparently no longer *requires* DNS to phone home (which
is pretty damn handy).

Sorry for the noise, everybody; hope y'all made it through the rain, ok.

Cheers,
-- jra

----- Original Message -----
> From: "Matthew Saks" <msaks at tvc.org>
> To: "jra" <jra at baylink.com>, outages at outages.org
> Sent: Monday, October 14, 2024 12:27:05 PM
> Subject: RE: [EXTERNAL] [outages]  login screen errors

> Can you browse to there? I can
> 
> [cid:image001.png at 01DB1E1B.3B2396E0]
> 
> From: Outages <outages-bounces at outages.org> On Behalf Of Jay R. Ashworth via
> Outages
> Sent: Monday, October 14, 2024 9:20 AM
> To: outages at outages.org
> Subject: [EXTERNAL] [outages] login screen errors
> 
> 
> [EXTERNAL EMAIL]
> Anyone have an opinion either way on whether this is at Microsoft's end?
> 
> User logs into Outlook.com<http://Outlook.com> for their hosted domain, using
> Chrome (for which
> they have a bookmark-bar link, so I assume it's what they usually use), and
> after several seconds of delay (5-15), they get this:
> 
> ===
> UTC Date: 2024-10-14T16:04:31.323Z
> Client Id: E6FE5F2C16B7401FA8BBAED29635B969
> Session Id: 9edcbe8e-dffb-4ba2-a03d-3231d2c178ee
> Client Version: 20240927008.13
> BootResult: network
> Back Filled Errors: Unhandled Rejection: TypeError: Failed to
> fetch:undefined|Unhandled Rejection: TypeError: Failed to
> fetch:undefined|Unhandled Rejection: TypeError: StartupData:StartupData:Failed
> to fetch:undefined|Unhandled Rejection: TypeError:
> StartupData:StartupData:Failed to
> fetch:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined
> err: TypeError: StartupData:StartupData:Failed to fetch
> esrc: StartupData
> et: ServerError
> estack: TypeError: Failed to fetch
> at
> https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mailindex.4641e6f0.js:1:119719<https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mailindex.4641e6f0.js:1:119719>
> at new Promise (<anonymous>)
> at a
> (https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mailindex.4641e6f0.js:1:119355<https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mailindex.4641e6f0.js:1:119355>)
> at
> https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mailindex.4641e6f0.js:1:119056<https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mailindex.4641e6f0.js:1:119056>
> at async
> https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mailindex.4641e6f0.js:1:138601<https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mailindex.4641e6f0.js:1:138601>
> ===
> 
> That sure feels server-end to me, but I'm not seeing any other reports about
> it so far. Most of their office uses Windows-Outlook, and appears to be fine.
> We're tracking a couple other windows-domain-login problems there, but I
> don't believe those could apply to OWA, right?
> 
> Cheers,
> -- jra
> --
> Jay R. Ashworth Baylink jra at baylink.com<mailto:jra at baylink.com>
> Designer The Things I Think RFC 2100
> Ashworth & Associates http://www.bcp38.info<http://www.bcp38.info> 2000 Land
> Rover DII
> St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274
> _______________________________________________
> Outages mailing list
> Outages at outages.org<mailto:Outages at outages.org>
> https://puck.nether.net/mailman/listinfo/outages<https://puck.nether.net/mailman/listinfo/outages>
> 
> 
> STOP & THINK!
> **This email was sent from outside The Vancouver Clinic. Do not open attachments
> or click links you are not expecting. Do not enter your clinic username or
> password into unauthorized websites. Any questions contact Help Desk at
> extension 3287.**
> 
> TVC CONFIDENTIALITY NOTICE
> This e-mail and any attachments are for the sole use of the intended recipients
> and contain information that may be confidential or legally privileged.
> If you have received this e-mail in error, please notify the sender by reply
> e-mail and delete the message.
> Any disclosure, copying, distribution, or use of this communication by someone
> other than the intended recipient is prohibited.

-- 
Jay R. Ashworth                  Baylink                       jra at baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates       http://www.bcp38.info          2000 Land Rover DII
St Petersburg FL USA      BCP38: Ask For It By Name!           +1 727 647 1274