Error message with long Twist thread
12-25-2006 | 01:47 PM
#1
Thread Starter
Senior Member
Joined: Sep 2005
Posts: 160
Likes: 0
Received 0 Likes
on
0 Posts
From: Bofferdange, LUXEMBOURG
Error message with long Twist thread
I'm getting this error message when I use the "Go to first unread post button" on the Twist thread at http://www.rcuniverse.com/forum/m_1674813/tm.htm:
I can access specific pages in the thread, which makes me wonder if perhaps the length of the thread is causing problems for the server.
Thanks very much, and merry Christmas to whoever reads this.
Matthew
Microsoft OLE DB Provider for SQL Server error '80040e31'
Timeout expired
/forum/fb.asp, line 72
Timeout expired
/forum/fb.asp, line 72
Thanks very much, and merry Christmas to whoever reads this.
Matthew
12-26-2006 | 10:09 AM
#2
Banned
RE: Error message with long Twist thread
This thread should probably be locked and a part II created. The length could be causing issues as the system parses all the posts on a per user basis to find the new post since last visit. I will split it and put reference to the original thread in the first post. this only happens in the largest threads in our system it seems and our upgrade next quarter we hope will address this bug
marc
marc
12-26-2006 | 04:23 PM
#3
Thread Starter
Senior Member
Joined: Sep 2005
Posts: 160
Likes: 0
Received 0 Likes
on
0 Posts
From: Bofferdange, LUXEMBOURG
RE: Error message with long Twist thread
ORIGINAL: RCadmin
This thread should probably be locked and a part II created. The length could be causing issues as the system parses all the posts on a per user basis to find the new post since last visit. I will split it and put reference to the original thread in the first post. this only happens in the largest threads in our system it seems and our upgrade next quarter we hope will address this bug
marc
This thread should probably be locked and a part II created. The length could be causing issues as the system parses all the posts on a per user basis to find the new post since last visit. I will split it and put reference to the original thread in the first post. this only happens in the largest threads in our system it seems and our upgrade next quarter we hope will address this bug
marc
Matthew
