How do I do this?
Main Topics
Browse All TopicsWhen I run an online report sometimes I get the following error pointing to my ASP page
How can I stop this from happening....This happens when the user requests lots of data.
Is there any way to make the time unlimited?
Microsoft OLE DB Provider for ODBC Drivers (0x80040E31)
[Microsoft][ODBC SQL Server Driver]Timeout expired
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Yes true.... above is just a code for what you need to do....... use 0 just for testing.
In a simple description the reason the Timeout is there is because some end users don't have patience. They see that the report is taking a long time so they click on refresh again and again not knowing that it is has lots of data. This backs up the SQL server. and when you have it set to 0 it will run all the way. When you have Timeout it kills it if it is taking to long
Those solutions should help with the actual timeout problem.
I would suggest spending some time and looking at the underlying cause of the timeout problem. Look at the performance of your server, look at the amount of data being sent, look at the way in which the data is being rounded up. Are your queries the most efficient, is there a lot of activity on your server? How are your indexes arranged, is there another way to write your queries, etc. etc.
Increasing the timeout will just stop the timeout from happening after the default, but your users will still have to wait that much time for the report to generate, 60 seconds is a lifetime to some users out there ;)
I don't know if you've solved this yet - but I just had the same problem on an Access XP form hitting a SQL 2000 box. Only one table was timing out, and only on updates and inserts (the data displayed OK on the form)...
Update on linked table "tblCustomer" failed. [ODBC SQL Server Driver] Timeout Expired (0)"
Recreating the table from scratch, a little bit at a time, uncovered the problem: three (3) ntext fields. Changing these to nvarchar(4000) solved the problem. Changing them back to ntext confirmed that this was indeed the issue.
I had a similar issue but with a much smaller database.
In the end I had to copy the database to a new name and update my site accordingly. Apparently the table was somehow damaged. I had already tried compact and repair and it made no difference. This is probably not a guaranteed fix but using the answer above only caused the page to never load.
Business Accounts
Answer for Membership
by: SRigneyPosted on 2003-10-28 at 09:59:26ID: 9635536
There is a connection timeout and a CommandTimeout property that both have default values of 60 seconds. You probably need to modify the CommandTimeout to be longer.