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 connection call failed

I moved a sql 2000 database to a sql 2005 server. I have a front end in access 2003. I manually created an ODBC data source system DSN using the ODBC Data Source Administrator just like it was on the other server. I can connect fine but users are saying their getting an odbc call fail. I created the connection and relinked the tables to the new server with the moved database. I completed the same task with another database and the user can connect fine. What could be the problem?

You will have to look at the additional information of the ODBC call / error message. I guess they are not priviledged to access the database or even connct to the server.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

ODBC Call Fail/Record locked

I have recently moved some native Access tables to SQL Server 7. These tables are updated in code. When the update is done via a SQL statement, I get
"This record is being modified by another user. . . Save, Copy to Clipboard, Drop Changes"

When the record is being updated via DAO code, I get,
"ODBC Call Fail"

Both errors are most irritating and I desperately need to find a way around this. Any suggestions would be greatly appreciated.

CrystalHi there,

Maybe this information helps you on the way...

-- Microsoft Knowledge Base Article - 128809

-- Zoek in de Google nieuwsgroepen naar Onderwerp:
"auto_increment fields and #Deleted in MS Access?"
Nieuwsgroep:
-> mailing.database.myodbc

Greetz,
DePrins
:)

odbc

I have moved my Sql2000 and the database to a new server. It works fine on the server but when I try to attach from a workstation odbc fails it tells me the server is unavailable.Hi,
Have you changed the ODBC driver on the workstation to
point to the new server?
Take a look at the account your using to connect to the db
on the new server? The account you are using must exist on
the new db server as well.
You could have orphaned users?
Possible that your new server is NOT on the same network
as the old one or your workstation.
hth
DeeJay
>--Original Message--
>I have moved my Sql2000 and the database to a new server.
It works fine on the server but when I try to attach from
a workstation odbc fails it tells me the server is
unavailable.
>.
>|||Hi,
Just by putting the users name in Enterprise Manager may
not be enough. It seems like you have orphaned users. Try
these scripts one at a time from the server or a client
machine that can connect to the new server:
1.
Use database_name
exec sp_change_users_login 'report'
This scripts reports any orphaned users in the database.
2.
Use database_name
exec
sp_change_users_login 'update_one', 'login_name', 'login_na
me_in_db'
Use this script to update all users one at a time. You
should run script for each user only if script 1 reported
a result.
If you have orphaned users and 'dspusers' was a user in
the old server, it will be returned as a result of script
1.
The other thing:
Are you able to ping this new server from the workstation?
When you configured the ODBC driver, did the server name
show-up in the drop-down list of SQL Servers?
hth
DeeJay
>--Original Message--
> Hi Deejay
>thanks for getting me started , yes I changed the Odbc
driver to point to the new server.
>I have an account called dspusers that I put into
enterprise manger and checked to be sure that my server is
on the same network. The workstation will attach to the
old server by just changing the server name in odbc, for
the new server I have used the name in odbc and when it
did not work I tried the address with the same results.
Anything else I can try.
> -- DeeJay Puar wrote: --
> Hi,
> Have you changed the ODBC driver on the workstation
to
> point to the new server?
> Take a look at the account your using to connect to
the db
> on the new server? The account you are using must
exist on
> the new db server as well.
> You could have orphaned users?
> Possible that your new server is NOT on the same
network
> as the old one or your workstation.
> hth
> DeeJay
>
> >--Original Message--
> >I have moved my Sql2000 and the database to a new
server.
> It works fine on the server but when I try to attach
from
> a workstation odbc fails it tells me the server is
> unavailable.
> >.
> >
>.
>|||Yes I can ping the server from the workstation, by name or by address. Script 1 shows all my users but dspusers, I am having trouble with script 2 getting syntax errors|||If Script 1 is returning results, all those users are
orphaned users. Orphaned users WILL NOT be able to connect
this database. I am wondering why dspusers in not showing?
Was this user already on the new server?
Script 2 should look like this:
EXEC sp_change_users_login 'Update_One', 'Mary', 'NewMary'
Where Mary is the name currently in the db and 'NewMary'
is the new name added in the Enterprise Manager.
I need some more info:
Was the dspuser in the old server as well? Or did you just
create it in on the new server? If you created on the new
server, did you grant dspusers access in the database.
Also, look in the db users and see if name is there? To do
this: Expand the db in question, and click on users.
How did you move the database?
I am sure if mentioned already or not, are you able to
connect to the database from the server? or anyother
workstation?
You did not answer the other question: When you configured
the ODBC driver, did the server name
show-up in the drop-down list of SQL Servers?
DeeJay
>--Original Message--
>Yes I can ping the server from the workstation, by name
or by address. Script 1 shows all my users but dspusers, I
am having trouble with script 2 getting syntax errors
>.
>