3

2/19/2009 4:05:13 PM

i haven't had these troubles as often... perhaps because it is spring break and people aren't using Tdub as much?

3/7/2009 2:07:34 PM

bttt

4/10/2009 8:39:49 AM

bttt

[Edited on April 18, 2009 at 12:03 AM. Reason : .]

4/17/2009 11:39:27 PM

ttt

4/26/2009 10:22:52 PM

i haven't had this problem for a good while now until today. what changed?

4/28/2009 1:51:43 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> "

OH SHIT!!!

(while trying to post this...)

Quote :

"OH SHIT! Internal Server Error! An error has occured on the server while processing the page. We have logged the error, but may not have all of the information we need to fix the error. It would help us if you could explain the circumstances of the error to us. Please contact us! "

6/8/2009 3:39:40 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>

6/12/2009 3:32:49 PM

Quote :

"/"

well there's your problem

6/12/2009 6:32:46 PM

ttt...stats is messed up

6/20/2009 10:56:10 PM

I like how the Online Users box on the main page fades in and out of existence from time to time.

6/21/2009 3:02:10 AM

thanks whoever fixed stats

6/21/2009 10:39:50 AM

stats messed up

6/24/2009 4:37:20 AM

dont know what the deal was...tww got buggy for about 8 minutes and then it came back but stats was messed up. wish i could meet qtmnfred irl and be like "so whats happening when tww goes slow for 8 minutes...like a server messing up or what? what causes something like that to randomly happen?"

7/7/2009 1:37:03 PM

ttt

7/17/2009 11:11:49 PM

SWEET! 15 OH SHIT'S IN A ROW!

7/20/2009 9:32:15 PM

They're happening a lot now.

7/27/2009 7:30:33 AM

yeah shitter's gettin full

7/27/2009 8:37:11 AM

i, too, am having this problem.

7/27/2009 1:25:06 PM

Site is running terribly today.

7/27/2009 9:00:10 PM

.

7/27/2009 9:04:58 PM

bttt, been shite for 2 days now

7/29/2009 6:48:52 PM

5
0
0

7/29/2009 9:31:33 PM

woot I'm not the only one

8/1/2009 10:07:25 PM

my buddies appears to be broken

as does the search for anything complex (keyword thread by user for instance)

8/7/2009 10:22:08 PM

TWW has the Oh Shits! again

10/5/2009 1:33:45 PM

i think qfred broked it when he tried to run a report on smileys in threads

10/5/2009 5:22:19 PM

THIS SHIT'S BROKE!

10/7/2009 10:55:48 AM

Quote :

"my buddies appears to be broken"

again

10/7/2009 4:06:29 PM

so I just checked another FF thread I posted in yesterday. I was getting pretty pissed @ qKen because he deleted my post then I remember that it Oh Shit'd a few times and I just gave up on the post.

[Edited on October 9, 2009 at 6:32 AM. Reason : .]

10/9/2009 6:32:20 AM

Runtime Error

10/9/2009 6:36:39 PM

here we go again

10/9/2009 9:23:43 PM

brentroad.com seems to work fine

thewolfweb.com is all kinds of jacked up

10/9/2009 9:49:11 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>

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>

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>

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>

THIS IS HOW MANY TIMES IT TOOK ME TO LOG IN

10/10/2009 5:43:46 PM

i've been trying to get on here for days... i had a couple of student tickets to give away. i didn't think to get on brentroad.com instead of tww.com

10/10/2009 9:51:45 PM

i'm on http://thewolfweb.com

i never ever get errors. except the ocassional /server down error system is down blah blah blah

I'm AstrallAdvent and i approved this message

10/10/2009 11:23:00 PM

i use thewolfweb.com. i've been getting the errors a lot over the past week or so.

10/11/2009 8:41:30 AM

terrible

site is getting to be more trouble than its worth

10/12/2009 11:03:00 AM

Got the runtime error 6 times before finally getting in.

10/12/2009 11:36:21 AM

FIx it soon - or no one wil comeback.

Who in charge - come on.

10/12/2009 12:49:42 PM

Quote :

"i use thewolfweb.com. i've been getting the errors a lot over the past week or so."

Quote :

"site is getting to be more trouble than its worth"

10/12/2009 10:46:48 PM

Come on - its foolish how long it is taking to fix this.

10/13/2009 1:59:42 PM

FIX IT PLEASE!!!!

10/13/2009 2:05:10 PM

the people in charge don't read feedback forum or use the site at all.

i relay messages to them, but i'll also suggest site_contact.aspx as a way to pester them into caring. they probably won't respond to your message, but they do read them

10/13/2009 2:08:14 PM

owners are fuckin morons, i am so sick of waiting and trying to log on 10 times that i just dont even come here anymore

10/13/2009 4:10:46 PM

yeah i think this might be the end of TWW.

10/13/2009 10:41:28 PM

after qntmfred posted the site contact info i sent them a message and now it magically works every time.

hmm...so it doesn't work for only certain users?

10/14/2009 8:33:08 AM

It appears that they figured out to apply a forward slash properly

but I didn't contact them

10/14/2009 9:58:51 AM

Eh, I think it's still doing it - though not as bad.

10/15/2009 2:03:38 AM

annnndddd it's broken again

10/15/2009 8:26:52 AM