Both of the below errors are most likely related to the internal network issues that were reported in StackStatus twitter account, but still think it's better reporting here.

  1. When trying to write a new query, I'm greeted with the generic ASP.NET error page:

  2. When trying to execute existing query (example) I get the error:

    The target principal name is incorrect. Cannot generate SSPI context.

  • 1
    Bug? Heck, that's just sentient servers knowing who you are and cringing.
    – Tim Post
    Feb 17, 2015 at 16:23
  • Probably fall-out from the downtime this morning. As Oded states: At this point, the websites are up and running, but some services are still spotty Feb 17, 2015 at 16:24
  • @Tim eh, this might be true! ;) Feb 17, 2015 at 16:25
  • 1
    @MartijnPieters yup, I clearly mentioned this in the very beginning of the post. Still, they might forget about those services so this can be used to remind them. Feb 17, 2015 at 16:25
  • @ShadowWizard: yeah, you are quite right. It wouldn't be the first time SEDE was left behind (or left disconnected after a database server move..). Feb 17, 2015 at 16:28
  • SRE team has been informed and have reproduced the issue(s).
    – Oded
    Feb 17, 2015 at 16:32
  • Hmm, we should probably have a better error page huh?
    – Tim Stone
    Feb 17, 2015 at 17:08
  • 3
    @Oded this SRE team? ;-) Feb 17, 2015 at 18:41
  • @Tim this, or add a read only mode too. If you add error page don't forget the lolcat! :-) Feb 17, 2015 at 18:42
  • 2
    @ShadowWizard you are on meta here, not in the Den...keep it civil please ;)
    – rene
    Feb 17, 2015 at 20:43
  • Oh, and it must be fixed now, Closey did fetch the latest tag in the Close vote room...
    – rene
    Feb 17, 2015 at 20:50
  • @rene yup, working again! Will post self answer soon if no dev would post first. Feb 17, 2015 at 20:52
  • Umm.. Several seconds ago I still get this error page when browsing through SEDE. The last time I used SEDE was eight hours ago and it was working normally :(
    – masegaloeh
    Feb 19, 2015 at 9:01
  • @masegaloeh weird indeed! Feb 19, 2015 at 9:02
  • Thanks for fixing @Marc, what happened there? Feb 19, 2015 at 12:40


You must log in to answer this question.

Browse other questions tagged .