2PM & i CAN’T LOG ON TO ANY THREADS!!! KEEP GETTING THE “TIME OUT” NOTICE!!! I THOUGHT THAT WAS ONLY FOR BAD KIDS!!![:(!]
NOTHING IS WRONG - WORKS FINE FOR ME!!!
ITS A LITTLE SLOW, WEEKEND, PROBABLY MINOR MAINTENANCE
NO BIG DEAL
You must lead a wonderful life…the biggest problem you seem to have is to come here and crab about the forum everyday. I’m glad I have many more real problems in my life to keep me busy.
Try rebooting your PC the next time you run into the Time Out errors…
Don Z.
When we first got this new system, we were advised that work was continuing on the software, and that when we got such notices of errors, the thing to try first was to delete cookies and to log back in.
No matter, after an hour off line it seems to be doing fine. I didn’t need to do anything…just be patient and find other things to do in the meantime. T’weren’t hard.
-Crandell
I was having the same problem today for a while. (chill pills help![swg])
Same here. I just waited it out.
Here is a good site to go to whenever you have a question about a website’s availability: Down For Everyone or Just Me? I’ve always headed for my favorite beverage whenever a website goes down. It tends to lower the frustration level.
Me too. Couldn’t get on this morning, so I went to the Roseville train show–didn’t find anything except a couple of neat Bragdon large rock castings–and when I got back, everything is up and running again.
Tom [:)]
IT’S CALLED DIAL-UP [:D]
I used to experience this a bit around the time of the change over from the old forum to this new(ish) version.
Ivanhen, I think what you refer to is just their default message that every so often busts out to cover what are probably several - “loss of service” situations. The web-bosses, or maintainance crew, are probably just having a bit of a fiddle with a screw-driver or wrench around the back of the switch board[;)]
Cheers
Bruce
It’s about time someone finally stated the obvious.
Dial up sucks, and the content rich web we all now enjoy is designed
FOR HIGH SPEED CONNECTIONS!!!
Fair or not that is the way it is so quit complaining every d**m time YOU have a problem.
Heres another bit of information, on Feb 2 of 2009, your TV is going to stop working as well.
GS
Before we go and send uninformed people in a panic about the TV thing, let’s shed some light for them: http://www.dtv.gov/index.html
Right. Broadcast signals that you would pick up with an antenna will be going to digital and many analog sets probably won’t be able to pick them up. There are digital converters already on the market for use with analog sets on antennas. Sets receiving signals on satellite or cable won’t be effected.
Actually it is Feb 17 for tv, but I have road runner high speed, and I had same problem with time out message this afternoon. Working fine now. Guess it is not only dial up. Sometime servers go down. Sometimes gremlins wake up. When we had problems with aircraft radios in Air Force, us maintenance guys just blamed it on sunspots. Pilots didnt know any better.
This kind of problem could be the result of any number of issues, including a problem anywhere between the computer and the server. I’ve experienced the same problem with some sites (not all) that only required me to reset my modem, or empty my browser cache, or some such.
Working with servers, we often find people can’t access our servers through issues unrelated to the servers themselves. Just the nature of the internet–a technology designed many years ago when its designers couldn’t imagine all the ways we use it now, yet it (mostly) works.
If you get one of the error messages below , it is very definitely serverside, not clientside
Grin,
Stein
Text copied out of the little too “smart” forum web application, pasted into notepad to remove unneccesary formatting, and then copied and pasted into the forum web application again …
Server Error in ‘/trccs’ Application.
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
The statement has been terminated.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
The statement has been terminated.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
The statement has been terminated.]
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +925466
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +800118
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +186
System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsPar
If you get one of the error messages below , it is very definitely serverside, not clientside
Grin,
Stein
Text taken out of the forum web application, pasted into notepad to remove unneccesary formatting, and then copied and pasted into the forum web application again …
Server Error in ‘/trccs’ Application.
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
The statement has been terminated.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
The statement has been terminated.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
The statement has been terminated.]
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +925466
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +800118
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +186
System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, Bul
Yep, that’s what I get from time to time.
Those SQL error messages indicate that Kalmbach’s web application is getting slow (or no) replies from Kalmbach’s database. Might be maintenance on database, might be an error.
Stein