lets fix this shit ok?

12/1/2008 11:21:41 PM

message_topic.aspx?topic=550633

12/1/2008 11:23:55 PM

yeah but it's more than just tonight. it has been every day lately.

12/1/2008 11:33:22 PM

Quote :

"attempt to address the issues "

12/1/2008 11:34:07 PM

k. thank u

12/1/2008 11:34:52 PM

it's still doing it.

12/7/2008 6:07:05 PM

we know

12/7/2008 7:03:13 PM

this is THE slowest website to load that i usually visit. back in the day it used to be THE fastest.

12/7/2008 10:42:27 PM

When I hop on the computer, I usually open up a TWW tab along with a whole bunch of others (like slickdeals, etc). by the time i get done checking all of those (3 or 4 websites) TWW has usually loaded.

12/7/2008 11:03:34 PM

RUNTIME ERROR

OH SHIT

12/14/2008 6:14:57 PM

this happens on both brentroad and thewolfweb after it takes like 45 secs to log in

12/15/2008 12:02:01 AM

i'm getting it too, every time. who can i bitch at more to make this go away?

12/19/2008 11:56:29 PM

Nael

12/20/2008 2:54:57 PM

I get it just about everytime I log in.

12/20/2008 3:12:03 PM

I've gotten a couple of them today, between trying to log in and trying to post replies to topics.

1/2/2009 2:12:52 AM

I usually only get these things in the wee hours of the morning... and sometimes the site is totally unusable around 5AM or so.

1/2/2009 2:13:58 AM

everytime i post, except right now

nevermind it was just being weird

1/14/2009 6:14:26 PM

i'm getting this shit constantly

[Edited on January 14, 2009 at 6:55 PM. Reason : 3 times before this post went through]

1/14/2009 6:55:37 PM

every time i get on TWW this happens.


but OMFG I'M JUST WEARING THE SMATH TROLL HAT AGAIN

1/14/2009 7:04:52 PM

get the error usually at least once every day... i guess it's the perpetual downhill motion t-dub has had for a long time now

1/14/2009 8:45:39 PM

get that or just chrome crashing when i attempt to post in http://www.thewolfweb.com/message_topic.aspx?topic=555178 from chrome. seems to work fine in IE, not sure why but i might stick to IE for a while

1/15/2009 12:41:18 AM

failure is imminent.
no usernames will be spared.
heads crash into platters.
multi-bit errors. ecc is useless.
the fans are locked up. coated in dust. temps are rising.
the motherboard has tin whiskers.
the kernel is fucked.
we're all going to disappear soon.
it's a genocide of the users.

1/15/2009 1:48:24 AM

look i'm cool with most atrocities

but user genocide i will not stand for

1/15/2009 2:09:38 AM

it'd probably be better for all of us in the long run if this whole thing went up in smoke

1/15/2009 9:41:06 PM

OH SHIT

1/16/2009 7:48:16 PM

OH SHIT! Internal Server Error!

1/17/2009 3:15:48 PM

FIX THIS SHIT

1/18/2009 5:34:09 PM

Quote :

"Server Error in '/' Application. Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off". <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration> Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL. <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration> "

Quote :

"Server Error in '/' Application. Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off". <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration> Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL. <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration> "

Quote :

"Server Error in '/' Application. Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off". <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration> Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL. <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration> "

Quote :

"Server Error in '/' Application. Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off". <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration> Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL. <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration> "

(yes, 4 times in a row.)

1/18/2009 5:37:36 PM

i don't dare close my tww window anymore b/c it takes 10 minutes to log in.

1/18/2009 10:14:48 PM

OH SHIT! Internal Server Error!

1/19/2009 10:26:48 PM

OH SHIT! Internal Server Error!

1/19/2009 11:17:49 PM

Quote :

"Server Error in '/' Application. Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off". <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration> Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL. <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration> "

Quote :

"Server Error in '/' Application. Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off". <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration> Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL. <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration> "

Quote :

"Server Error in '/' Application. Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off". <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration> Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL. <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration> "

Quote :

"Server Error in '/' Application. Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off". <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration> Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL. <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration> "

(yes, 4 times in a row.)

Quote :

"OH SHIT! Internal Server Error!"

1/20/2009 5:18:29 PM

I was so elated this morning. I logged in twice, yes twice, with no delay, OH SHITs, etc. But since, I have not had the same experience.

FIX TEH SHIT

1/20/2009 7:15:56 PM

Server Error in '/' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>


Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

1/20/2009 9:22:49 PM

I missed a question on ReceiveDeath's Name that NES Tune because of this

UNACCEPTABLE

1/21/2009 6:20:15 PM

Server Error in '/' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>


Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

1/21/2009 7:01:37 PM

Quote :

"Server Error in '/' Application. -------------------------------------------------------------------------------- Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off". Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's configuration tag to point to a custom error page URL. "

Just received this message AT LEAST 10 times, and that's not an exaggeration. I have tried to load the site off an on for over 30 minutes now. Luckily this most recent attempt I was able to get straight through to the TWW-Home page instead of the usual OH SHIT! page.

This shit has been going on for MONTHS. Is it really that hard to fix? I mean we have several resident computer geniuses that I'm sure could fix this probably minor issue. This site has consistently overlooked any issues that arise though, and it's only gotten worse as the years go by. I for one will not be surprised if the site doesn't load at all in a few more months.

1/21/2009 9:28:12 PM

^agreed

its gotten to the point where I just leave the page open all the time, because it takes at least 5-10 minutes to load if I open a new window

1/21/2009 9:56:45 PM

most people are going to get to the point where they just leave it closed.

1/21/2009 10:17:29 PM

people have offered to help and the owners seem not to want that help.

its really frustrating on our end

1/22/2009 9:14:17 AM

Quote :

"I have tried to load the site off an on for over 30 minutes now. Luckily this most recent attempt I was able to get straight through to the TWW-Home page instead of the usual OH SHIT! page."

damn it never takes me more than 1-2 minutes to open tww, even in the worst of times (with 3-4 errors)

Quote :

"its gotten to the point where I just leave the page open all the time, because it takes at least 5-10 minutes to load if I open a new window"

probably not a bad idea to leave a tww window open if the errors annoy you

1/22/2009 9:19:06 AM

probably not a bad idea to fix the errors

1/22/2009 10:05:03 AM

probably not a bad idea to fix the errors

1/22/2009 10:09:57 AM

hahaha you guys are such bitches

we already told you there is no one to fix the errors

but keep on bitching and whining like a bunch of 3 year olds. NOTHING BUT SUNSHINE BABY!!!!!!!!!!!!!!!!!!!!!!1

1/22/2009 10:37:27 AM

1/22/2009 10:49:03 AM

so you, the other mods, and whoever is running this piece of shit now admittedly have no plans in place to correct the errors now, or at any time in the future?

fucking amazing.

and I fail to see how pointing out errors with the site can be constituted as whining and bitching like a 3 year old, especially considering i've made less than 5 posts on the issue i'm sure. i'm simply pointing out a valid concern with the site, an error that is affecting multiple users.

i'm not coming in here asking for you to ban/suspend/terminate anyone for an asinine comment in chit chat, i'm providing FEEDBACK, in the FEEDBACK forum, dick.

And before it's even called into question...

Sweden,


Nope, just pointing out the obvious.

1/22/2009 11:04:08 AM

i wonder why there's no new users on here...

1/27/2009 9:46:07 AM

Quote :

"so you, the other mods, and whoever is running this piece of shit now admittedly have no plans in place to correct the errors now, or at any time in the future? fucking amazing"

WE HAVE NO CONTROL OVER THIS

THE ADMINS REFUSE TO COMMUNICATE REGARDING THESE ISSUES

IF WE COULD FIX IT WE WOULD BUT WE CANT SO WE WONT

ITS NOT LIKE WE ENJOY THESE ERRORS EITHER BUT AGAIN, WE HAVE NO CONTROL OVER THE

SITUATION

1/27/2009 10:51:10 AM

quntmfred doesnt have unfettered access to the inner workings of the place?

1/27/2009 10:59:56 AM

no, chance
he doesnt

ken only has the permissions to work on certain things

1/27/2009 11:01:36 AM