Knowledge Base

BUG: Multi-Protocol Connection Fails with SQL 6.5 and Integrated Security Using 7.00.623 Netlib

Article ID: 236334

Article Last Modified on 2/23/2004

APPLIES TO

Microsoft SQL Server 6.5 Standard Edition
Microsoft SQL Server 7.0 Standard Edition

This article was previously published under Q236334

BUG #: 56042 (SQLBUG_70)

SYMPTOMS

If a client attempts a Multi-Protocol connection using dbLibrary or ODBC to a SQL Server 6.5 server using Microsoft Windows NT Integrated Security, the connection fails with this message:

6.5 ISQL Client:

Possible network error: Write to SQL Server Failed.
Unable to connect: SQL Server is unavailable or does not exist.

6.5 ODBC Client with MDAC 2.1 SQL Server Driver version 3.70.623:

Connection failed.
SQLState 01000
SQL Server Error 0
[Microsoft][ODBC SQL Server Driver][Multi-Protocol]
Connection failed.
SQLState 08S01
SQL Server Error 0
[Microsoft][ODBC SQL Server Driver] Communication link failure

7.0 ISQL Client:

Possible network error: Write to SQL Server Failed. General Network error. Check your documentation.
NetLibrary error 1722: ConnectionOpen(RpcEpResolveBinding() )

Unable to connect: SQL Server is unavailable or does not exist. General network error. Check your documentation.
NetLibrary error 1722: ConnectionOpen(RpcEpResolveBinding() )

7.0 ODBC Client:

[Microsoft][ODBC SQL Server Driver]
Communication link failure.
[Microsoft][ODBC SQL Server Driver][Multi-Protocol]

WORKAROUND

Change the security on the SQL 6.5 Server from Microsoft Windows NT Integrated to Mixed Security.

STATUS

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

Additional query words: MDAC Trusted authenticated

Keywords: kbbug kbpending KB236334

Microsoft KB Archive/236334

Contents