Some of my clients cannot access an application, and it seems there is
a communication issue(?). The application server is a bit slow, the
database server (MS SQL Server 2000, SQL SP4) is brand new and fast.
Users that have the problem are behind a firewall that allows
everything from the client network to the server network. I have
configured the ODBC DSN, tested it, and the test succeeds. When
starting the application however, they get an error, [Microsoft][ODB
C
SQL Server Driver]Timeout expired. I have traced the startup, and the
log file is pasted below:
Vbus 100-938 ENTER SQLAllocEnv
HENV * 013FC478
Vbus 100-938 EXIT SQLAllocEnv with return code 0
(SQL_SUCCESS)
HENV * 0x013FC478 ( 0x02031540)
Vbus 100-938 ENTER SQLAllocConnect
HENV 02031540
HDBC * 01AC4ED0
Vbus 100-938 EXIT SQLAllocConnect with return code 0
(SQL_SUCCESS)
HENV 02031540
HDBC * 0x01AC4ED0 ( 0x020315e8)
Vbus 100-938 ENTER SQLDriverConnectW
HDBC 020315E8
HWND 001902C6
WCHAR * 0x74329A38 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x74329A38
SWORD 2
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>
Vbus 100-938 EXIT SQLDriverConnectW with return code -1
(SQL_ERROR)
HDBC 020315E8
HWND 001902C6
WCHAR * 0x74329A38 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x74329A38
SWORD 2
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>
DIAG [S1T00] [Microsoft][ODBC SQL Server Driver]Timeout expired
(0)
Vbus 100-938 ENTER SQLErrorW
HENV 02031540
HDBC 020315E8
HSTMT 00000000
WCHAR * 0x00208B48 (NYI)
SDWORD * 0x01AC4EDC
WCHAR * 0x00208748
SWORD 512
SWORD * 0x0020F08C
Vbus 100-938 EXIT SQLErrorW with return code 0
(SQL_SUCCESS)
HENV 02031540
HDBC 020315E8
HSTMT 00000000
WCHAR * 0x00208B48 (NYI)
SDWORD * 0x01AC4EDC (0)
WCHAR * 0x00208748 [ 50] "[Microsoft][ODBC SQL
Server Driver]Timeout expired"
SWORD 512
SWORD * 0x0020F08C (50)
It seems that the SQLDriverConnectW is what generates the error, but I
am not a database administrator, nor developer, and knows nothing about
what it is or means.
The ODBC-driver (odbc32.dll) version on the machines that get this
error, is identical to those that don't.
Can anyone interpret this trace for me? What goes on, what is the
ODBC-driver (or anything else) complaining about? Would be highly
appreciated!
Bjorn Henrik Formo.Any luck on this issue. I am running into the same error. The ODBC test
connects fine but from my application I cannot.
-Markus
markusr
---
markusr's Profile: http://www.dbtalk.net/m568
View this thread: http://www.dbtalk.net/t169537
Showing posts with label expired. Show all posts
Showing posts with label expired. Show all posts
Friday, March 9, 2012
Wednesday, March 7, 2012
odbc sql server driver timeout expired
Hi,
Has anyone ever had trouble using the query analyzer tool through a vpn
client? I'm able to connect outside of work to a sqlserver db on my
company lan with enterprise mgr, but the query analyzer times out every
time I try to connect from outside of work. Both utilities work fine at
work (no vpn tunnel).
The exact error is:
Unable to connect to server blahblahblah:
ODBC: Msg 0, Level 16, State 1
[Microsoft][ODBC SQL Server Driver] Timeout expired
I've tried increasing the sqlserver odbc driver's CPTimeout without success.
Appreciate any advice.
Eric"efinney" <efinney@.mitre.org> wrote in message
news:cjvgck$a1f$1@.newslocal.mitre.org...
> Hi,
> Has anyone ever had trouble using the query analyzer tool through a vpn
> client? I'm able to connect outside of work to a sqlserver db on my
> company lan with enterprise mgr, but the query analyzer times out every
> time I try to connect from outside of work. Both utilities work fine at
> work (no vpn tunnel).
> The exact error is:
> Unable to connect to server blahblahblah:
> ODBC: Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver] Timeout expired
> I've tried increasing the sqlserver odbc driver's CPTimeout without
> success.
> Appreciate any advice.
> Eric
Assuming there are no name resolution issues, then you need to make sure the
correct ports are open over the VPN:
http://support.microsoft.com/defaul...2&Product=sql2k
Simon|||Hi Eric
Can you do
Telnet <SQL Server's name or IP address> 1433
If it connects to port 1433 through VPN then it means your connection
is good then you can start diagnosing why you are getting timeouts,
perhaps slow connection or flakey VPN connection.
Regards
Shehzad
efinney <efinney@.mitre.org> wrote in message news:<cjvgck$a1f$1@.newslocal.mitre.org>...
> Hi,
> Has anyone ever had trouble using the query analyzer tool through a vpn
> client? I'm able to connect outside of work to a sqlserver db on my
> company lan with enterprise mgr, but the query analyzer times out every
> time I try to connect from outside of work. Both utilities work fine at
> work (no vpn tunnel).
> The exact error is:
> Unable to connect to server blahblahblah:
> ODBC: Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver] Timeout expired
> I've tried increasing the sqlserver odbc driver's CPTimeout without success.
> Appreciate any advice.
> Eric
Saturday, February 25, 2012
ODBC SQL Driver Timeout Expired from MS Access
Hi
I'm running a machine with windows xp pro sp2. I have a MS Access 2000 database on that machine. The database contains 1 odbc linked table
and 1 Access query.
The odbc linked table is connected to a MS SQL Server 2000 database with a ODBC SQL Server System DSN.
The table on SQL Server to which the table in Access is linked has about
3 million + rows.
When I open the ODBC linked table in Access, it opens without a problem.
However, if I use even so much as one criterion such as "where company = ABC" for example, then it "thinks" for a while and returns the dreaded:
[Microsoft][ODBC SQL Driver] Timeout Expired (#0).
I have to use MS Access 2000 as the front end for this SQL Database table.
How do I get around the timeout issue. Is there a setting in SQL?
Please keep in mind that
I can't write the queries as Store procs because the requirement of the client is that there be one Linked Access table that the users can use
to write various access queries. No user are not techies.
please helpread this post:
http://www.mcse.ms/message1582144.html
I don't test.
Tell me.
Bye.
I'm running a machine with windows xp pro sp2. I have a MS Access 2000 database on that machine. The database contains 1 odbc linked table
and 1 Access query.
The odbc linked table is connected to a MS SQL Server 2000 database with a ODBC SQL Server System DSN.
The table on SQL Server to which the table in Access is linked has about
3 million + rows.
When I open the ODBC linked table in Access, it opens without a problem.
However, if I use even so much as one criterion such as "where company = ABC" for example, then it "thinks" for a while and returns the dreaded:
[Microsoft][ODBC SQL Driver] Timeout Expired (#0).
I have to use MS Access 2000 as the front end for this SQL Database table.
How do I get around the timeout issue. Is there a setting in SQL?
Please keep in mind that
I can't write the queries as Store procs because the requirement of the client is that there be one Linked Access table that the users can use
to write various access queries. No user are not techies.
please helpread this post:
http://www.mcse.ms/message1582144.html
I don't test.
Tell me.
Bye.
ODBC Native State S1T00: timeout expired
Hello :
I am very new to ODBC connectivity, but i know sql fairly
well:
What can generate a Native State Error: Native State
S1T00: timeout expired on a SQL 2000 database; NT4 OS
Server??
I am running sql database dependent applications on this
server: 3 to be exact.
e.g. I have an application which transports data that was
entered to the SQL database located on this Server via a
LAN user. This application then dynamically takes this
data and transports it to another device located on the
same sub-net as the Server for data recognition and other
functionalities. This is performed in milliseconds hence
it may be utilizing the (winmm.dll) file to accomplish
this. But the error message:
"Warning State: S1T00,Native:0, Origin: [Microsoft][ODBC
SQL Server Driver] timeout expired"
causes this process to fail along with other ODBC and SQL
dependent applictions. also my maintenance plans failed as aresult of this message..
Can someone please help/ inform me what can cause this and
how to prevent this??
Can a modem dial-in access cause this?? though it was
running fine with modem access in the past, and no change
in its configs.??
Thank you in advance
AdiggaMay check this KBA (http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q175/2/64.asp&NoWebContent=1) .
I am very new to ODBC connectivity, but i know sql fairly
well:
What can generate a Native State Error: Native State
S1T00: timeout expired on a SQL 2000 database; NT4 OS
Server??
I am running sql database dependent applications on this
server: 3 to be exact.
e.g. I have an application which transports data that was
entered to the SQL database located on this Server via a
LAN user. This application then dynamically takes this
data and transports it to another device located on the
same sub-net as the Server for data recognition and other
functionalities. This is performed in milliseconds hence
it may be utilizing the (winmm.dll) file to accomplish
this. But the error message:
"Warning State: S1T00,Native:0, Origin: [Microsoft][ODBC
SQL Server Driver] timeout expired"
causes this process to fail along with other ODBC and SQL
dependent applictions. also my maintenance plans failed as aresult of this message..
Can someone please help/ inform me what can cause this and
how to prevent this??
Can a modem dial-in access cause this?? though it was
running fine with modem access in the past, and no change
in its configs.??
Thank you in advance
AdiggaMay check this KBA (http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q175/2/64.asp&NoWebContent=1) .
Subscribe to:
Posts (Atom)