SQL Search Error ’80040e31’
Printed From: Web Wiz Forums
Category: Web Wiz Web App Support Forums
Forum Name: Web Wiz Forums
Forum Description: Support forum for Web Wiz Forums application.
URL: https://forums.webwiz.net/forum_posts.asp?TID=10211
Printed Date: 04 April 2026 at 11:08pm
Software Version: Web Wiz Forums 12.08 - https://www.webwizforums.com
Topic: SQL Search Error ’80040e31’
Posted By: klr3
Subject: SQL Search Error ’80040e31’
Date Posted: 29 April 2004 at 4:47am
|
Very time some one try to search in message body on the serach pages, I always get following error: Timeout expired /forum/search.asp, line 356 |
Replies:
Posted By: WebWiz-Bruce
Date Posted: 29 April 2004 at 7:11am
|
Increase the timeout property in the common.asp file.
------------- https://www.webwiz.net/web-wiz-forums/forum-hosting.htm" rel="nofollow - Web Wiz Forums Hosting https://www.webwiz.net/web-hosting/windows-web-hosting.htm" rel="nofollow - ASP.NET Web Hosting |
Posted By: klr3
Date Posted: 29 April 2004 at 7:27am
|
Thanks Borg, but that does not work. Timeout is now set 180, but the result is still the same. I think my provider has a default timeout...  But i donīt understand why the error only displays when searching in the message body??? |
Posted By: WebWiz-Bruce
Date Posted: 29 April 2004 at 7:50am
|
Maybe your web host can shed light on this. I have seen this error before when the SQL server is located at a different geographical location to the web server, thus the data was taking time to travel across the Internet. ------------- https://www.webwiz.net/web-wiz-forums/forum-hosting.htm" rel="nofollow - Web Wiz Forums Hosting https://www.webwiz.net/web-hosting/windows-web-hosting.htm" rel="nofollow - ASP.NET Web Hosting |
Posted By: klr3
Date Posted: 29 April 2004 at 8:04am
|
Thatīs not the problem here as the servers are located i the same server room, and in same country... |
Posted By: michael
Date Posted: 29 April 2004 at 9:09am
|
If your server is somewhat busy and your database for the forum somewhat large it can easily timeout. There had to be a sacrifice made in SQL performance to make the search more interoperable between access and sql versions. if you understand a little about sql, t-sql etc. it is easily possible for you to improve search performance. The reason why it times out only in body search is, that it is going through text fields which naturally takes longer then some short char fields. ------------- http://baumannphoto.com" rel="nofollow - Blog | http://mpgtracker.com" rel="nofollow - MPG Tracker |
Posted By: klr3
Date Posted: 11 May 2004 at 3:33pm
Now I have opgraded the forum to 7.8, got our own expensive server with SQL along, on the same machine... |
klr3 wrote:
Posted By: klr3
Date Posted: 24 May 2004 at 9:09am
Still no answers??? Please help - I donīt know what to do??? I tried to copy the data from the SQL to Access, and guess what... Now itīs possible to search in the body field (in Access), but still this search returns the mentioned error code... Please note, that the database is NOT an option! What am I, and my web host, doing wrong??? To Borg: If you in any way can give some exclusive support, Iīm accepting you invioce! |
Posted By: WebWiz-Bruce
Date Posted: 24 May 2004 at 1:11pm
|
There shouldn't be anything on line 356 which is throwing up the error. Either the file is modified or corrupted, try reuploading the original file again and see if that improves the search. ------------- https://www.webwiz.net/web-wiz-forums/forum-hosting.htm" rel="nofollow - Web Wiz Forums Hosting https://www.webwiz.net/web-hosting/windows-web-hosting.htm" rel="nofollow - ASP.NET Web Hosting |
Posted By: klr3
Date Posted: 05 November 2004 at 4:33pm
|
Have allready tryed that, and: Creating a new fresh database - result= NONE Overwritten all files with untouche ones - result= NONE Absolutly nothing words! :O( The database size is around 226 MB, could it be the the size, which is messing it up? If so, are there any ways to limit the search in the fiels message??? PLZ help me! Everything else works 100% perfect!!! I really do NOT want to give this forum up!!! Thanks in advance! :O) |
Posted By: Shatz
Date Posted: 07 November 2004 at 3:17am
|
Hi, FWIW, I found the following http://support.microsoft.com/default.aspx?scid=kb;en-us;305635 - MSDN article which describes a scenario in which the "autogrow" feature of SQL databases can yield timeout errors. Hopefully this helps in some way. :) Take Care, ------------- Take Care, Shatz Pro Racing Series Developer/Administrator http://www.ProRacingSeries.com - http://www.ProRacingSeries.com |
Posted By: bjobra
Date Posted: 26 January 2005 at 4:15am
| I have just got the same problem after 1 year without. THe database is no more than 60 MB. I did lenghten the timeout settings to 180. My server host deny any wrongs. |
Posted By: WebWiz-Bruce
Date Posted: 26 January 2005 at 5:40am
|
Hosts usually do deny there is something wrong, get back to your host and hassel them till they sort it out or move host.
------------- https://www.webwiz.net/web-wiz-forums/forum-hosting.htm" rel="nofollow - Web Wiz Forums Hosting https://www.webwiz.net/web-hosting/windows-web-hosting.htm" rel="nofollow - ASP.NET Web Hosting |
Posted By: bullish1
Date Posted: 19 September 2005 at 2:19pm
|
Actually the solution is pretty simple.
You need to add a Index to the tblTopic using Last_entry_date.
Since the query is ORDER BY Last_entry_date and the table is not indexed by this field, the sort is being done at the time of the query.
Jeffrey Hines
HairBoutique.com
|
Posted By: Mojo_Risin
Date Posted: 20 September 2005 at 9:41pm
I was quite hopeful that this was the solution. I've had this problem for some time. The database has over 100,000 messages and growing rapidly. It's been quite some time since members have been able to do a search without timing out. ------------- Dave |
Posted By: Mojo_Risin
Date Posted: 20 September 2005 at 9:42pm
|
I forgot to mention in my last post that I in fact added the index to my SQL server database, but still no go. ------------- Dave |