JavaScript is required to use Bungie.net

Service Alert
All Destiny releases will be temporarily offline tomorrow for scheduled maintenance. Please stay tuned to @BungieHelp for updates.

#Community

6/24/2009 4:27:37 AM
383

System.Web.HttpException

[b][u]Brief Summary of the Error[/b][/u]: The first outbreak of the error was late June 23. The error then stopped for most and slowed down intensely for all others, although Achronos posted [url=http://www.bungie.net/Forums/posts.aspx?postID=34068728&postRepeater1-p=6#34081317]this[/url] before it started again, revealing the nature of the issue (the report button). The error began again en mass shortly after Achronos posted (on June 24), but was then not seen again until early in the morning July 3. It has re-appeared July 9 and 10 in the early morning and on July 12 in the early evening. The July 12 event was reported to be the worst yet, and lasted from around 4:00 PM PST to (at least) 2:00 AM PST on the 13. Early in the afternoon on the 13, Achronos posted [url=http://www.bungie.net/Forums/posts.aspx?postID=34068728&viewreplies=true&postRepeater1-p=15#34699411]this[/url], confirming that the error was fully known and that a fix was on the way. [b][u]What we know[/u][/b]: - The error stems from the report button, which is why the moderators do not have the error and why the error does not appear in private groups. - No sub-domains of bungie.net offer protection from the error. - Refreshing a page [i]will[/i] get rid of the error, but there have been reports of a page being refreshed over 100 times and the error still not going away. Also keep in mind that, if you post and get the error, the post might have gone through. [i]Do not[/i] post again until you get through and see if the post was made! - A fix is set for late on the 13 or 14 of July: no more errors! [b][u]How to get rid of the Error[/b][/u]: - Hit the report button until it goes away. - If you use FireFox, download [url=http://macro-halo.110mb.com/GreaseGrunty%20-%200.6.4.7-fx.xpi]GreaseGrunty[/url] (a specialty version of GreaseMonkey by PKF_647) and then download the [url=http://userscripts.org/scripts/show/52298]Friendly B.net System.Web.HttpException Re-direct[/url] script, also by PKF_647. For best effect, go to Tools->Greasemonkey->Manage User Scripts and place the Friendly B.net System.Web.HttpException Re-direct script at the very top of the list, so it will load first and re-direct ASAP. [Edited on 07.13.2009 12:54 PM PDT]

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Weird, I came here to see if anyone else was getting the same problem. Every thread I clicked on for a while had that happen. Like Snakie said though, it seems to have gone away. EDIT: Or not, I got it as soon as I posted this reply. [Edited on 06.23.2009 8:32 PM PDT]

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • [quote][b]Posted by:[/b] SonicJohn I find it funny that I got the error for the first time when I clicked on this thread. I blame you, Snakie.[/quote]Me too.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • [quote][b]Posted by:[/b] DeathBringer669 I get it once every other day on average. Just refresh the page and it goes away. But 75% of the time? That must be some issue on your end.[/quote] It seems to have gone away there for a few minutes, but it's starting up again now. I think it's one or two servers that're doing it, but it's pretty damn bad when it flares up. [Edited on 06.23.2009 8:30 PM PDT]

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • im geting it to but if i refresh when i get it i get though.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • OMG haha I just got it when I was trying to sign in to reply to this thread. [url=http://i42.tinypic.com/2naisuw.jpg]Notice the url on this one.[/url] [url=http://i43.tinypic.com/2je5hc6.jpg] and this one.[/url] [Edited on 06.23.2009 8:32 PM PDT]

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • I find it funny that I got the error for the first time when I clicked on this thread. I blame you, Snakie.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Dammit Snakie.I was just about to post this thread Yeah I'm getting them every other page. I had to try twice to get to this thread. Gotta be a bug.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • I get it once every other day on average. Just refresh the page and it goes away. But 75% of the time? That must be some issue on your end.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon