FIX: SYBASE CT-Library Clients Cannot Connect to Microsoft SQL Server 7.0

ID: Q239883

The information in this article applies to:

Microsoft SQL Server version 7.0

BUG #: 55964 (SQLBUG_70)
BUG #: 55787 (SQLBUG_70)

SYMPTOMS

SYBASE clients using a CT-Library based on Tabular Data Stream (TDS) 5.0 (including Open Client 10.0.4 and 11.1.1) cannot connect to Microsoft SQL Server 7.0.

These clients may encounter one of the following SYBASE CT-Library errors reported by SYBASE Isql.exe:

CT-LIBRARY error: ct_connect(): network packet layer: internal net library error: Net-Library operation terminated due to disconnect

CT-LIBRARY error: ct_connect(): protocol specific layer: internal Client Library error: There is a tds state machine error. An illegal tds token sequence was received.

The Microsoft SQL Server 7.0 errorlog reports the following error:

ods Error: 17832, Severity: 18, State: 7
ods Connection opened but invalid login packet(s) sent. Connection closed..

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

The English version of this fix should have the following file attributes or later:


   Version      File name   Platform
   ---------------------------------------------------------

   7.00.723     s70723i.exe Intel
                s70723a.exe Alpha

NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 7.0.

MORE INFORMATION

Microsoft SQL Server 6.5 and 7.0 are designed for backward compatibility to support TDS 4.2 clients, including TDS 4.2 clients from SYBASE. However, some of Microsoft's customers have traditionally been able to connect their SYBASE TDS 5.0 clients and perform basic queries against a Microsoft SQL 6.5 server. This configuration is not supported by Microsoft, although some customers have been using it.

Changes were made in SQL 7.0 to provide more TDS protocol checks that prevented these SYBASE TDS 5.0 clients from making the same connection as in SQL 6.5. Therefore, a change has been introduced in SQL 7.0 that allows SYBASE TDS 5.0 clients to connect. However, this does not mean the configuration is officially supported by Microsoft. TDS 4.2 is the only level of compatibility that is supported for SYBASE TDS based clients. TDS 5.0 is a SYBASE specification and it is not supported by Microsoft.

NOTE: Microsoft will not include these changes in future versions of Microsoft SQL Server. These changes will remain during the lifetime of the SQL 7.0 product, including service packs. Limited testing has been performed by Microsoft regarding the functionality of SYBASE TDS 5.0 clients with this change. Only basic connectivity is ensured.

Anyone requiring this functionality should seek a different solution for connecting SYBASE clients to Microsoft SQL Server such as using an ODBC driver or OLE-DB provider.

Additional query words:

Keywords : kbSQLServ700bug
Version : winnt:7.0
Platform : winnt
Issue type : kbbug