Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

runtime error -21472717871 (80040e31) timeout expired

3,029 views
Skip to first unread message

Eric Hosier

unread,
Dec 18, 2001, 11:12:32 AM12/18/01
to
I have a custom VB 6.0 application useing ADO with an OLEDB connction to a
SQL Server 2000 database. A single stored procedure is called 200 times per
minute to populate a table in SQL Server. The program runs for anywhere
between 4 and 12 hours and then provides this error "runtime
error -21472717871 (80040e31) timeout expired". This kicker is that the
error kills my VB application.

I have updated SQL Server 2000 to SP2 and have MDAC 2.6 running on my client
computer where the VB application exists. I have searched the Microsoft
website over and over to find this error, but have not found an article that
relates to my problem.


Michael Visintin

unread,
Dec 18, 2001, 5:04:10 PM12/18/01
to
Eric,

Is this a trappable error?

If it is, then you could clear it and keep processing.

In some of my programs, errors are generated by the server that do not
affect my processing or the quality of my data. In those cases, I merely
write the error to a log, clear it, and keep on going.

If you are unfamiliar with error handling then the help topic "Designing an
Error Handler" in the msdn help may be of use.

Michael

"Eric Hosier" <eho...@wyan.org> wrote in message
news:#Qk8nA#hBHA.2568@tkmsftngp03...

HC

unread,
Jan 25, 2002, 1:16:10 PM1/25/02
to
I am having the same problem and just wonder if you found
the solution.

Thanks

>.
>

agrawal...@gmail.com

unread,
Oct 20, 2012, 3:41:09 AM10/20/12
to Eric Hosier
Hi...

"create your connection"

Global Db as New ADODB.Connection
put this property
Db.CommandTimeout = 0

That's all. this should take care of your query time out issue.

asa...@gmail.com

unread,
Jan 29, 2014, 11:06:52 AM1/29/14
to
I'm not sure if this will help, but I was getting this error this morning on an insert/update stored procedure. Rebuilding the indexes on the related table seemed to do the trick.

aman.b...@gmail.com

unread,
Jan 6, 2016, 12:38:51 AM1/6/16
to
This helped. It worked for me. After implementing this the timeout error disappeared.

hriti...@gmail.com

unread,
Feb 8, 2017, 10:58:56 AM2/8/17
to

Please tell how to set index

ralph

unread,
Feb 9, 2017, 12:23:40 AM2/9/17
to
On Wed, 8 Feb 2017 07:58:55 -0800 (PST), hriti...@gmail.com wrote:

>
>Please tell how to set index
>

https://msdn.microsoft.com/en-us/library/office/jj249241.aspx

0 new messages