23
PastaSam
62d

Microsoft error messages have to be the worst I've ever seen. "Sorry, something went wrong." "Oops, something's not working". Thanks, do you care to elaborate? Would really help my troubleshooting...

Comments
  • 0
    Did it say contact support?
  • 1
    @asgs nope, literally just the first error I quoted. It was Teams. Only other info it gave was the correlation ID which is about as useful as a chocolate teapot. Similar error messages appear in Outlook with even less info.
  • 6
    Microsoft has a long tradition with this https://techrepublic.com/pictures/...
  • 3
    Check the event viewer for actual information on vague error messages ... I've had to use procmon (sysinternals) in the past for a 3rd party app giving a vague message.. turns out it was trying to contact a samba share that no longer existed stored in a cache somewhere.. doing this allowed me to at least get "random chiropractic billing software" to work again
  • 3
    A user just reported another error message received in Teams: "We're sorry - we've run into an issue. Try again." That's fine if the error happens once and is fixed with a refresh, utterly useless if it's a consistent issue...
  • 2
    @anolis unfortunately, due to the Corona lockdown, many of these error messages are being reported by remote users rather than witnesses first hand. Additionally, many of those users are on personal machines so we don't even have remote management. It seems Teams is the biggest culprit for useless error messages, but I've experienced it in other MS/Office apps too.
  • 1
    why do u need to troubleshoot? there is an in built troubleshooter that comes with windows ! ur welcome :)
  • 0
    Microsoft error? Whatever it was...

    have you tried turning it on and off again?
  • 2
    One would think Microsoft would improve their error messages, but nope. Got this error when I tried to change my Microsoft Teams picture.
  • 0
    Correlation Id: 337ea083-22e4-494b-9be9-8c40373fb69a
  • 1
    Lets just throw a super generic error and error code E7533789309.
  • 1
    Why would you need to know? Just parrot the oops message to their support and depending on which string of words you get they have a sheet that tells them what each means.

    kill me
Add Comment