The information in this article applies to:
SYMPTOMS
When you Use Sybase Open Client applications, you can connect to Microsoft
SQL Server using TCP/IP sockets. If you have experienced any unexpected
client disconnection problems from these applications, you can avoid them
by reconfiguring the TCP/IP transport.
when you attempt to run queries after the idle. Depending on the operating system platform, you may also receive other error messages, such as:
on a UNIX client. Running sp_who on the SQL Server, you can confirm that the connection was dropped. CAUSEIn Windows NT, when a TCP/IP connection idles for a certain period, TCP/IP generates "keep-alive" traffic. When TCP/IP determines that no activity has occurred on the connection within the specified time (default 120 seconds), it generates keep-alive traffic to probe the connection. After it tries the configured number of times to deliver the keep-alive traffic without success, it marks the connection as down, and the SQL Server connection is dropped. WORKAROUND
You can add the registry entry:
or modify it if you already have one, in the following path:
and set it to the number (in seconds) that you prefer. To keep the connection alive forever, you should set the value to zero. For example,
NOTE: You need to reboot Windows NT after making this change. MORE INFORMATION
The disconnection problem may not occur with your particular SQL
application if the application can automatically reconnect after the
connection is dropped.
Additional query words: 4.20 Windows NT connectivity
Keywords : kb3rdparty SSrvLAN |
Last Reviewed: March 17, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |