Showing posts with label adotimeouts. Show all posts
Showing posts with label adotimeouts. Show all posts

Friday, March 30, 2012

ODBC Drivers error '80040e31'

We moved our SQL Server 2000 onto a Win 2003 box (with SQL
SP3a applied).
Lately, we have been experiencing intermittent ADO
timeouts on our webpages displaying the following error:
Microsoft OLE DB Provider for ODBC Drivers
error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expired
If anyone has any ideas as to possible reasons, it would be immensely apprec
iated?
Any help would be greatly appreciated.
Thank you.
- A l p e rMaybe some information here:
http://www.aspfaq.com/2287
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:3F1AC249-81D0-498F-AB81-E8F628A1F98C@.microsoft.com...
> We moved our SQL Server 2000 onto a Win 2003 box (with SQL
> SP3a applied).
> Lately, we have been experiencing intermittent ADO
> timeouts on our webpages displaying the following error:
> Microsoft OLE DB Provider for ODBC Drivers
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
> If anyone has any ideas as to possible reasons, it would be immensely
appreciated?
> Any help would be greatly appreciated.
> Thank you.
> - A l p e r
>|||Thanks Aaron!
I've changed the connection string and am connecting with OLE DB provider no
w...we'll see if it makes any difference...
But I have a feeling it will start throwing time outs any way... May be our
tables, queries, etc. need to be optimized...
Thanks,
- A l p e r
-- Aaron Bertrand - MVP wrote: --
Maybe some information here:
http://www.aspfaq.com/2287
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:3F1AC249-81D0-498F-AB81-E8F628A1F98C@.microsoft.com...
> SP3a applied).
> timeouts on our webpages displaying the following error:
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
appreciated?[vbcol=seagreen]
>sql

ODBC Drivers error '80040e31'

We moved our SQL Server 2000 onto a Win 2003 box (with SQL
SP3a applied).
Lately, we have been experiencing intermittent ADO
timeouts on our webpages displaying the following error:
Microsoft OLE DB Provider for ODBC Drivers
error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expired
If anyone has any ideas as to possible reasons, it would be immensely appreciated?
Any help would be greatly appreciated.
Thank you.
- A l p e r
Maybe some information here:
http://www.aspfaq.com/2287
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:3F1AC249-81D0-498F-AB81-E8F628A1F98C@.microsoft.com...
> We moved our SQL Server 2000 onto a Win 2003 box (with SQL
> SP3a applied).
> Lately, we have been experiencing intermittent ADO
> timeouts on our webpages displaying the following error:
> Microsoft OLE DB Provider for ODBC Drivers
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
> If anyone has any ideas as to possible reasons, it would be immensely
appreciated?
> Any help would be greatly appreciated.
> Thank you.
> - A l p e r
>
|||Thanks Aaron!
I've changed the connection string and am connecting with OLE DB provider now...we'll see if it makes any difference...
But I have a feeling it will start throwing time outs any way... May be our tables, queries, etc. need to be optimized...
Thanks,
- A l p e r
-- Aaron Bertrand - MVP wrote: --
Maybe some information here:
http://www.aspfaq.com/2287
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:3F1AC249-81D0-498F-AB81-E8F628A1F98C@.microsoft.com...[vbcol=seagreen]
> SP3a applied).
> timeouts on our webpages displaying the following error:
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
appreciated?
>