ODBC Native State S1T00: timeout expired

ODBC Native State S1T00: timeout expired

Post by AT » Mon, 09 Jun 2003 07:06:52



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.

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

Adigga

 
 
 

1. ODBC Native State S1T00: timeout expired

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.

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

Adigga

2. US-TX: Dallas-Oracle Enterprise Database Administrator

3. Warning State: S1T00,Native:0, Origin: [Microsoft][ODBC SQL Server Driver] timeout expired

4. parameter in stored procedure

5. category:odbc,source:odbc sql server driver,number:s1t00(timeout expired)

6. result stream separation

7. S1T00: [Microsoft][ODBC SQL Server Driver] Timeout Expired

8. ParityReplace runs when Parity=N?????

9. S1T00[Microsoft][ODBC SQL Server Driver]Timeout expired

10. S1T00 [Microsoft] [ODBC SQL driver] timeout expired

11. S1T00 [Microsoft] [ODBC SQL driver] timeout expired.

12. S1T00[Microsoft][ODBC SQL Server Driver]Timeout expired

13. S1T00[Microsoft][ODBC SQL SERVER DRIVER] TIMEOUT EXPIRED ????