20

Server Error in '/' Application.


Runtime Error

Description: An exception occurred while processing your request. Additionally, another exception occurred while executing the custom error page for the first exception. The request has been terminated.

enter image description here

This is happening as I'm posting this question.

  • 5
    Any site, except meta.stackexchange.com – bummi Oct 11 '17 at 5:59
  • 1
    meta.stackoverflow.com is fine too. – johnchen902 Oct 11 '17 at 5:59
  • Was just about to report this here as well. i.imgur.com/yWNIDQv.png . Looks like someone didn't run all their unit tests before pushing live ^.^. It is all sites except this one which are affected. – Kraang Prime Oct 11 '17 at 6:02
  • Everyone I asked IRL have no issues. QAQ – johnchen902 Oct 11 '17 at 6:10
  • Looks like IPS is back up. – apaul Oct 11 '17 at 6:17
  • Most of my usual sites seem to work for me ._. MSE's likely unaffected cause (ironically?) its where stuff gets tested first I suspect. – Journeyman Geek Oct 11 '17 at 6:19
  • It's not really back yet, I get "host can't be resolved" every few requests. – ShaWiz Oct 11 '17 at 6:46
9

(copied from my answer on meta.so)

The servers where the errors happened just got patched. The running theory is that that in some cases, when app domains that existed before that patching tried to load new assemblies after the patching, there was some conflict that prevented that from working.

Exception type: FileLoadException 
Exception message: Loading this assembly would produce a different grant set
    from other instances. (Exception from HRESULT: 0x80131401)

This is so low-level that you didn't even get our custom error page if you hit an affected server (which wasn't all of them, so not everybody saw any issues).

We'll look deeper into the causes later, but the issue is fixed for now and it's late at night for our SREs in the U.S.

  • So the "host can't be resolved" I now get often isn't related? – ShaWiz Oct 11 '17 at 7:12
  • 1
    @ShaWizDowArd No, that would be a DNS issue (and the usual cause for something like that is a blip in your internet connection). – balpha Oct 11 '17 at 7:13

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .