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.

#Septagon

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

  • I think it's gone for a bit.

    Posting in language:

     

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

  • It's looking to me like it's done. I'll include in the OP that the final occurrence of the problem was reported at 2:00 AM PST.

    Posting in language:

     

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

  • Stupid memory problems.

    Posting in language:

     

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

  • Today has been good so far, hopefully it's done.

    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] furiocity I seem to be experiencing this bug more on the Flood, maybe the forum activity might have something to do with it. I find that even if i do get the error after posting, my post will still deliver even though it fails to refresh correctly. [/quote] Seems to happen to me more in the Halo 2 forum than anywhere else.

    Posting in language:

     

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

  • I seem to be experiencing this bug more on the Flood, maybe the forum activity might have something to do with it. I find that even if i do get the error after posting, my post will still deliver even though it fails to refresh correctly. [quote][b]Posted by:[/b] DR WE1RD I have only had one issue with it today and that was around 2am Bungie time. The stupid thing didn't go away until I refreshed the page about 4 times. One thing is for sure, it has gotten me into the habit of copying my post before hitting the reply button.[/quote] [Edited on 07.13.2009 3:53 AM 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 have only had one issue with it today and that was around 2am Bungie time. The stupid thing didn't go away until I refreshed the page about 4 times. One thing is for sure, it has gotten me into the habit of copying my post before hitting the reply button.

    Posting in language:

     

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

  • Haven't had any problems today so far :D.

    Posting in language:

     

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

  • Great, it's attacking me furiously right now. No!!!!!!1111

    Posting in language:

     

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

  • I have been getting the error messages all day. In fact, I had to reload this thread twice just to reply to it.

    Posting in language:

     

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

  • They just came back for me.

    Posting in language:

     

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

  • Regardless of what the problem is, it needs to be fixed sooner than later. It has being going on for long enough. Very, very annoying.

    Posting in language:

     

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

  • So, it happens if you have access to the 'report spam' button, right? Just disable it for a while, let people PM the mods for problems.

    Posting in language:

     

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

  • LOL I thought I was banned or something since it happened whenever I tried to post. I want to be a moderator without the powers until it gets fixed so I don't have to deal with it hehe! :3

    Posting in language:

     

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

  • You don't have to wait until the page loads just to get the error message. Click refresh until you see the topic subject come up in your brower's menu bar thing.

    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] Gamer3427 He makes sense, if it doesn't delete old reports after a time it might be causing a slight overload that causes hiccups when you do certain things, which in turn causes the error, (just a thought).[/quote]^^^^^^^^ Tl:dr version. Thanks gamer3427.

    Posting in language:

     

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

  • He makes sense, if it doesn't delete old reports after a time it might be causing a slight overload that causes hiccups when you do certain things, which in turn causes the error, (just a thought).

    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] Lord Snakie [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.[/quote]Perhaps its a script problem, after being pressed repeatly the report button created unentended files and, much like a old coumputer. This old date added up and is now causing errors in the memory and prossesing, But thats as much as my computer knolege can help. probly no help at all.

    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] Gamer3427 Is that the actual error, or what causes the error?[/quote] If you wanted the technical mumbo-jumbo, follow the link in the OP to Achronos' post, it explains the exact reason for the error. For rudimentary purposes, all that need be known is that the error [i]stems[/i] from the report button.

    Posting in language:

     

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

  • Is that the actual error, or what causes the error?

    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] Gamer3427 If you're saying that about me, and the error has been explained on another page tell me a number, (I skipped pages 2-13)....[/quote] Yes, you did miss it, it's in the OP twice: the report button.

    Posting in language:

     

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

  • If you're saying that about me, and the error has been explained on another page tell me a number, (I skipped pages 2-13)....

    Posting in language:

     

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

  • Ah jeez, NOT AGAIN! Has Achronos ticked off N. Korea recently? [Edited on 07.12.2009 9:17 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'm sorry, but I still don't quite understand what the error is....

    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 almost every time i click a topic! Ugh!

    Posting in language:

     

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

  • Lol. I just got it for reporting a thread. It made me giggle.

    Posting in language:

     

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

1 2 3 4 5 6 7
You are not allowed to view this content.
;
preload icon
preload icon
preload icon