On Mon, Nov 29, 1999 at 02:36:55PM -0800, Greg Kornatowsky wrote:
> Has anyone successfully connected their Radiator running on a Linux box to
> Microsoft SQL 7. If you have would you mind sharing the details. We are
> running SQL 6.5 and have no problems with the Sybase drivers but we are
> thinking of upgrading to 7.
>
6.5->7 breaks the Sybase libraries. Microsoft has recognised this as a bug
(ie lost sales) and issue a patch to make it work again.
SYBASE CT-Library Clients Cannot Connect to SQL Server
----------------------------------------------------------------------------
---
The information in this article applies to:
- Microsoft SQL Server version 7.0
----------------------------------------------------------------------------
---
BUG #: 55964 (SQLBUG_70)
SYMPTOMS
========
SYBASE clients using 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.
Some 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 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.
Keywords : kbSQLServ700bug
Version : winnt:7.0
Platform : winnt
Issue type : kbbug
Solution Type : kbfix
THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS
IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER
EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS
SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT,
INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN
IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR
LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE
FOREGOING LIMITATION MAY NOT APPLY.
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
