BUG: "Too Many Open File Handles" Error Using Named Pipes

Last reviewed: September 23, 1997
Article ID: Q161169
The information in this article applies to:
  • Microsoft SQL Server version 6.5
BUG #: 16113 (6.50)

SYMPTOMS

When more than three named pipe connections are made per application to the computer running SQL Server, the Net-Library returns the following errors on the client computer:

   Connection Failed:
   SqlState : '01000'
   SQL Server Error: 24
   [Microsoft][ODBC SQL Server Driver][SQL
   Server][DBNMP3]ConnectionOpen(sopen())

   Connection Failed:
   SqlState : '08001'
   SQL Server Error: 16
   [Microsoft][ODBC SQL Server Driver][SQL Server][DBNMP3]Too many open
   file handles.

The SQL Server errorlog reports the following information:

   Unable to read login packet(s)
   Error:17832, Severity:18, State:0

This behavior occurs on computers running Windows 3.x or Windows for Workgroups 3.11 running Visual Basic 3.0 or Microsoft Access 2.0 applications that access a computer running SQL Server 6.5.

WORKAROUND

To work around this problem, do either of the following:

  • Use the Multiprotocol network protocol, or any interprocess communications (IPC) method other than Named Pipes.

    -or-

  • Replace the 6.5 version of the Dbnmp3.dll file with the 6.0 version.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server 16-bit Named Pipes Net-Library version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

This problem does not occur if the Dbnmp3.dll file version 6.5 is replaced with the 6.0 version of Dbnmp3.dll. The problem also does not occur with the 32-bit Named Pipes Net-Library.


Additional query words: netlib netlibrary
Keywords : kbbug6.50 SSrvErr_Log SSrvNet_Lib kbinterop kbnetwork
Version : 6.5
Platform : WINDOWS


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: September 23, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.