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?
>

ODBC Driver error '80040e14'

We are using SQL7 and are experiencing this problem when trying to update
to the database. It is an intermitent problem. Any ideas? The error
code reads:
Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
[Microsoft][ODBC SQL Server Driver][SQL Server]The request for p
rocedure
'tblCompanySubCategory' failed because 'tblCompanySubCategory' is a table
object.
Message posted via http://www.droptable.com"L Adam via droptable.com" <forum@.droptable.com> wrote in message
news:8fbaff9acfc64ae38f5473689da09957@.SQ
droptable.com...
> We are using SQL7 and are experiencing this problem when trying to update
> to the database. It is an intermitent problem. Any ideas? The error
> code reads:
> Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
> [Microsoft][ODBC SQL Server Driver][SQL Server]The request for
procedure
> 'tblCompanySubCategory' failed because 'tblCompanySubCategory' is a table
> object.
> --
> Message posted via http://www.droptable.com
can you paste the sql that created the error?
cheers
lefty|||This is the sql code that is causing the error:
response.buffer=true
Dim Rs1, Con1, RedirectString
set Con1 = server.createobject("ADODB.Connection")
Con1.open( "dsn=*****;uid=******" )
set Rs1 = server.createobject("ADODB.recordset")
Rs1.open "tblCompanySubCategory", Con1,3,3
If not isnull(request.form("TheSubCatID")) then
if len(trim(request.form("TheSubCatID"))) then
Rs1.addnew
Rs1("LastAmendedBy") = request.Cookies("***")("UserID")
Rs1("LastAmendedDate") = date()
Rs1("CompanyID") = request.querystring("CompanyID")
Rs1("CatSubCatID") = request.form("TheSubCatID")
Rs1.update
end if
End If
Con1.close
set Con1 = Nothing
set Rs1 = Nothing
RedirectString = "SalesCompanyCategory.asp?CompanyID=" &
request.querystring("CompanyID") & "&method=save"
response.clear
response.redirect RedirectString
response.end
Thoughts?
Message posted via http://www.droptable.com|||"L Adam via droptable.com" <forum@.droptable.com> wrote in message
news:43509d3988f8454c9af8da35ebbe7f39@.SQ
droptable.com...
> This is the sql code that is causing the error:
> response.buffer=true
> Dim Rs1, Con1, RedirectString
> set Con1 = server.createobject("ADODB.Connection")
> Con1.open( "dsn=*****;uid=******" )
> set Rs1 = server.createobject("ADODB.recordset")
> Rs1.open "tblCompanySubCategory", Con1,3,3
> If not isnull(request.form("TheSubCatID")) then
> if len(trim(request.form("TheSubCatID"))) then
> Rs1.addnew
> Rs1("LastAmendedBy") = request.Cookies("***")("UserID")
> Rs1("LastAmendedDate") = date()
> Rs1("CompanyID") = request.querystring("CompanyID")
> Rs1("CatSubCatID") = request.form("TheSubCatID")
> Rs1.update
> end if
> End If
> Con1.close
> set Con1 = Nothing
> set Rs1 = Nothing
> RedirectString = "SalesCompanyCategory.asp?CompanyID=" &
> request.querystring("CompanyID") & "&method=save"
> response.clear
> response.redirect RedirectString
> response.end
> Thoughts?
> --
> Message posted via http://www.droptable.com
sorry but i haven't a clue.
Although why dont you watch the actual sql being sent to sql server with the
profiler, then compare a working sql to the sql that gave you the error.
That should show you were the problem lies
you could change it to a straight sql = "insert into etc.etc"
Best Regards
Lefty

ODBC Driver error '80040e14'

We are using SQL7 and are experiencing this problem when trying to update
to the database. It is an intermitent problem. Any ideas? The error
code reads:
Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
[Microsoft][ODBC SQL Server Driver][SQL Server]The request for procedure
'tblCompanySubCategory' failed because 'tblCompanySubCategory' is a table
object.
Message posted via http://www.sqlmonster.com
"L Adam via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:8fbaff9acfc64ae38f5473689da09957@.SQLMonster.c om...
> We are using SQL7 and are experiencing this problem when trying to update
> to the database. It is an intermitent problem. Any ideas? The error
> code reads:
> Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
> [Microsoft][ODBC SQL Server Driver][SQL Server]The request for procedure
> 'tblCompanySubCategory' failed because 'tblCompanySubCategory' is a table
> object.
> --
> Message posted via http://www.sqlmonster.com
can you paste the sql that created the error?
cheers
lefty
|||This is the sql code that is causing the error:
response.buffer=true
Dim Rs1, Con1, RedirectString
set Con1 = server.createobject("ADODB.Connection")
Con1.open( "dsn=*****;uid=******" )
set Rs1 = server.createobject("ADODB.recordset")
Rs1.open "tblCompanySubCategory", Con1,3,3
If not isnull(request.form("TheSubCatID")) then
if len(trim(request.form("TheSubCatID"))) then
Rs1.addnew
Rs1("LastAmendedBy") = request.Cookies("***")("UserID")
Rs1("LastAmendedDate") = date()
Rs1("CompanyID") = request.querystring("CompanyID")
Rs1("CatSubCatID") = request.form("TheSubCatID")
Rs1.update
end if
End If
Con1.close
set Con1 = Nothing
set Rs1 = Nothing
RedirectString = "SalesCompanyCategory.asp?CompanyID=" &
request.querystring("CompanyID") & "&method=save"
response.clear
response.redirect RedirectString
response.end
Thoughts?
Message posted via http://www.sqlmonster.com
|||"L Adam via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:43509d3988f8454c9af8da35ebbe7f39@.SQLMonster.c om...
> This is the sql code that is causing the error:
> response.buffer=true
> Dim Rs1, Con1, RedirectString
> set Con1 = server.createobject("ADODB.Connection")
> Con1.open( "dsn=*****;uid=******" )
> set Rs1 = server.createobject("ADODB.recordset")
> Rs1.open "tblCompanySubCategory", Con1,3,3
> If not isnull(request.form("TheSubCatID")) then
> if len(trim(request.form("TheSubCatID"))) then
> Rs1.addnew
> Rs1("LastAmendedBy") = request.Cookies("***")("UserID")
> Rs1("LastAmendedDate") = date()
> Rs1("CompanyID") = request.querystring("CompanyID")
> Rs1("CatSubCatID") = request.form("TheSubCatID")
> Rs1.update
> end if
> End If
> Con1.close
> set Con1 = Nothing
> set Rs1 = Nothing
> RedirectString = "SalesCompanyCategory.asp?CompanyID=" &
> request.querystring("CompanyID") & "&method=save"
> response.clear
> response.redirect RedirectString
> response.end
> Thoughts?
> --
> Message posted via http://www.sqlmonster.com
sorry but i haven't a clue.
Although why dont you watch the actual sql being sent to sql server with the
profiler, then compare a working sql to the sql that gave you the error.
That should show you were the problem lies
you could change it to a straight sql = "insert into etc.etc"
Best Regards
Lefty

OCIEnvNlsCreate failed with return code -1

Hi. We're experiencing the exact same problem described in this post: http://tinyurl.com/ynqv7o
We've tried the 11 steps described there and it didn't fix the problem -- just as it didn't fix it for that person.

Help!! Thank you.Anyone have any thoughts on what's causing this problem? Your help is much appreciated

Obtaining Hotfix

We're experiencing the problem describe in MS Knowledge
Base Article - 812915 "Performance monitor shared memory
setup failed: -1" error message when you start SQL
Server. The article states there is a support hotfix
available through Microsoft Product Support Services.
We're currently evaulating SQL server so we're using the
Enterprise Evaluation Edition. We like to obtain the
hotfix ( preferably for free ), but since we have
evaluation edition we don't know how to go about this.
Can we get the hotfix?
(a) I don't think you can apply patches and hotfixes to the evaluation
edition, but I'm not 100% positive. Did you install the latest release of
the evaluation edition, or have you been running it for a while?
(b) you can't just bypass product support and download a hotfix "for
free"... if it's a bug, and you can demonstrate to PSS that you are affected
by it, then you will be provided the file and refunded the cost of the call.
http://www.aspfaq.com/
(Reverse address to reply.)
"J" <anonymous@.discussions.microsoft.com> wrote in message
news:886b01c49606$7e287f90$a501280a@.phx.gbl...
> We're experiencing the problem describe in MS Knowledge
> Base Article - 812915 "Performance monitor shared memory
> setup failed: -1" error message when you start SQL
> Server. The article states there is a support hotfix
> available through Microsoft Product Support Services.
> We're currently evaulating SQL server so we're using the
> Enterprise Evaluation Edition. We like to obtain the
> hotfix ( preferably for free ), but since we have
> evaluation edition we don't know how to go about this.
> Can we get the hotfix?