BUG: SQL Server May Fail to Listen On DecNet

 Last reviewed: May 2, 1997
Article ID: Q138943

The information in this article applies to:
  • Microsoft SQL Server, version 6.0
BUG# NT: 11872 (6.00)

SYMPTOMS

When Microsoft SQL Server is set up to listen on DecNet as the only Winsock- based IPC (Inter-Process Communication), the following error may occur in the SQL Servers error log or the Windows NT event log: 

   Error : 17826, Severity: 18, State: 0
   Unable to set up ListenOn connection '#150'.
   OS Error : 10093, ConnectionListen ((null)()).
If you try to connect from a DecNet client, the connection will fail with the following error: 

   DB-Library: Unable to connect: SQL Server is unavailable or does not
      exist.  Specified SQL server not found.
   Net-Library error 10022: ConnectionOpen (dnet_conn()).
However, if you set up SQL Server to listen on both DecNet and TCP/IP sockets, the above error will not occur, and the DecNet connection will work fine.

WORKAROUND

You can easily avoid this problem by setting up SQL Server to listen on TCP/IP Sockets at the same time.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: sql6 ssmsde60 server-side netlibs ODS Pathworks
Keywords : kbbug6.00 kbnetwork SSrvLan SSrvNet_Lib
Version : 6.0
Platform : WINDOWS
Issue type : kberrmsg

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.

Last reviewed: May 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.