{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
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]
-
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.
-
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.
-
I find it funny that I got the error for the first time when I clicked on this thread. I blame you, Snakie.
-
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]
-
im geting it to but if i refresh when i get it i get though.
-
[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]
-
[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.
-
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]
-
Hasn't happened for a few refreshes to me too, yeah...
-
[quote][b]Posted by:[/b] Another one 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.[/quote] do you think we should email bungie to report this? [Edited on 06.23.2009 8:34 PM PDT]
-
Snakie, I got it also when I entered this thread the second time. There must be some weird issue with you and the Bungie servers. Half the people that have posted in this thread got the error only when entering your thread. It took me 3 refreshes to get in here. OMG SNAKIE IS A HACKAR! [Edited on 06.23.2009 8:37 PM PDT]
-
Eh. It's waning and waxing. In and out.
-
[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] Same thing happened to me. Server gremlins have a sense of humour.
-
That's what she said. [quote][b]Posted by:[/b] burritosenior Eh. It's waning and waxing. In and out.[/quote]I blame stosh for letting the Webmaster out of his cage.
-
I keep getting it, a lot. I even got it when trying to answer a poll. It takes 4-5 refreshes for it to finally work.
-
I got it trying to open this thread.
-
Well for me, I get it more in the ODST forum than anywhere. Every time I click on a thread there it happens. It could just be a coincidence though.
-
It seems like a ton of people are getting this when they try to open this thread. I'm infecting everyone! OH NOES!!!
-
*Is also annoyed...* lol But yeah I started getting this error just recently maybe in the past hour... On nearly every other link I click.
-
I have to refresh a few times before I can even get on a thread. Let alone make a post. Let alone even edit a post. Let alone even preview a post. Edit: I had to when I submitted this post. I'm going to go insane. [Edited on 06.23.2009 8:42 PM PDT]
-
[quote][b]Posted by:[/b] Lord Snakie It seems like a ton of people are getting this when they try to open this thread. I'm infecting everyone! OH NOES!!![/quote] Damn it Snakie, now I keep getting it. Last time I post in one of your threads... Maybe this is like a simulated pandemic outbreak but instead of an illness, it is this weird glitch. We have to kill the infected... *kills everyone in the thread* *cries* *kills self*
-
For the last five minutes or so it hasn't let me into any threads at all. But now it seems to have gone away, at least for a while.
-
[quote][b]Posted by:[/b] DeathBringer669 [quote][b]Posted by:[/b] Lord Snakie It seems like a ton of people are getting this when they try to open this thread. I'm infecting everyone! OH NOES!!![/quote] Damn it Snakie, now I keep getting it. Last time I post in one of your threads... Maybe this is like a simulated pandemic outbreak but instead of an illness, it is this weird glitch. We have to kill the infected... *kills everyone in the thread* *cries* *kills self*[/quote] Maybe we only need to kill the first one infected..........
-
I have yet to get one of these messages, but people in #bungienet are getting it.
-
[quote][b]Posted by:[/b] Helveck *Is also annoyed...* lol But yeah I started getting this error just recently maybe in the past hour... On nearly every other link I click. [/quote] i was about to say that
-
I'm seeing it a ton, too. Almost every time I load a page. Maybe because of maintenance, or maybe a massive glitch?
