Microsoft Outlook is crashing worldwide with 0xc0000005 errors

Post by LadyCailin » Wed, Jul 15, 2020, 11:30 PM UTC

parliament32 wrote: post #93

16bytes wrote: post #59

I still don't understand why Microsoft doesn't print human readable error code instead of just "0xc0000005". To figure out what the actual message is, you first have to figure out if you are seeing a HRESULT or a NTSTATUS[1]. In this case the leading 0xC is an invalid HRESULT, so it's for sure an NTSTATUS. Then you just look up the code in the bottom two bytes [2]. In this case it's just error code 5: "STATUS_ACCESS_…

I think you overestimate how useful "human readable error codes" would be: https://i.imgur.com/SL88Z6g.jpg

Post by annoyingnoob » Thu, Jul 16, 2020, 12:22 AM UTC

ocdtrekkie wrote: post #99

annoyingnoob wrote: post #98

Earlier quoted context omitted.

I would not call this a major outage. The service still worked, just not from a single client app, many apps still worked as did the web interface. My house is more stable too but my office is not. I've had UPS systems fail. I've had ISP outages. The overall up time is better, in the case of Exchange, than I could make it at the office - especially considering the 24/7 nature of email today. We need fewer IT people b…

I would say I've found "cloud engineer misconfigures something that knocks the whole service offline" happens more frequently than "my building has a hardware, power, or ISP failure". To some degree, I feel like cloud services have, after overengineering their redundancies for such common failures... introduced a far worse failure via their extremely sophisticated update cadence and orchestration systems.

Post by perl4ever » Thu, Jul 16, 2020, 6:53 AM UTC

kccqzy wrote: post #92

CWuestefeld wrote: post #73

Earlier quoted context omitted.

A zillion years ago I was able to see some of the internal communications around the development of OS/2. One topic was the way that non-system floppies would (fail to) boot when left in the PC. What the user would see was something like (I forget the exact numbers) SYS!012345 SYS!876543 ...and they were supposed to go look that up in some reference book to see what it meant. The question was why they weren't outputt…

This kind of pictograms always reminds me of Apple. When a Mac can't boot because of corrupt boot files, it shows a "prohibit" sign. I suppose the reasoning was the same—not all users can understand English. But in this day and age a pictogram is in fact harder to search for because people describe it differently.

Post by senectus1 » Thu, Jul 16, 2020, 2:02 PM UTC

16bytes wrote: post #59

I still don't understand why Microsoft doesn't print human readable error code instead of just "0xc0000005". To figure out what the actual message is, you first have to figure out if you are seeing a HRESULT or a NTSTATUS[1]. In this case the leading 0xC is an invalid HRESULT, so it's for sure an NTSTATUS. Then you just look up the code in the bottom two bytes [2]. In this case it's just error code 5: "STATUS_ACCESS_…

Post by zaphar » Thu, Jul 16, 2020, 3:53 PM UTC

_bxg1 wrote: post #47

marricks wrote: post #14

I wonder if large companies get more of a pass with outages then small ones? Bias towards authority in a way. If a service has a big enough base an outage could almost seem like a pass for everyone. “Oo couldn’t do that this morning GITHUB was down.” Whereas if my small GitLab server was down bosses could be “well why aren’t we on GitHub like everyone else, it’s up now?” When google calendar was down a bit ago I trie…

One angle to look at this from is that if Slack or GitHub goes down, there's a good chance your competitors are being held up too. It's like an armistice on (your corner of) capitalism. Whereas if it's just your system, you've been put at a slight disadvantage. Also, unless it's happening every week there's probably an element of, "well it doesn't make me regret the overall choice to use this service, so there's no s…