FIX: You cannot create new TCP/IP socket based connections after error messages 17882 and 10055 are written to the Microsoft SQL Server 2000 error log

This article describes the following about this hotfix release:

• The issues that are fixed by this hotfix package.
• The prerequisites for installing the hotfix package.
• Whether you must restart your computer after you install the hotfix package.
• Whether the hotfix package is replaced by any other hotfix package.
• Whether you must make any registry changes.
• The files that are contained in the hotfix package.

Issues that are fixed by this hotfix package

The following issue is fixed in this Microsoft SQL Server 2000 hotfix package:

• You experience all the following symptoms on a computer that is running Microsoft SQL Server 2000:
  • You cannot connect to SQL Server 2000 by using a TCP/IP socket based connection after error messages 17882 and 10055 are written to the SQL Server error log.
  • You cannot establish any new connections despite the message reporting.
  • An error message that is similar to the following is written to the SQL Server 2000 error log:
    
    server Error: 17882, Severity: 18, State: 1
    server Error accepting connection request via Net-Library 'SSNETLIB'. Execution continuing..
    server Error: 17059, Severity: 18, State: 0
    server Operating system error 10055: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full...

For a list of previous hotfixes, see the "Microsoft SQL Server 2000 Post-Service Pack 3 or Microsoft SQL Server 2000 Post-Service Pack 3a hotfixes" section in the following Microsoft Knowledge Base article:

This problem occurs because SQL Server does not allocate non-paged pool bytes. In this scenario, TCP stack allocates non-paged pool. This hotfix only implements a retry logic. The hotfix does not fix the underlying problem.

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

Prerequisites

This hotfix requires SQL Server 2000 Service Pack 3 (SP3). For information about how to obtain SQL Server 2000 SP3, see the following article in the Microsoft Knowledge Base: Additionally, this hotfix requires that you also have SQL Server 2000 hotfix build 2000.80.977 installed. For more information about SQL Server 2000 Post SP3a hotfix build 2000.80.977, click the following article number to view the article in the Microsoft Knowledge Base:

Restart information

You do not have to restart your computer after you apply this hotfix.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

SQL Server 2000 32-bit versions

SQL Server 2000 64-bit version

Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

To work around this problem, you can use one or both of the following methods:

• Connect to SQL Server by using another network protocol such as Named Pipes.
• Remove the following Windows Boot.ini file switches:
  • /3GB
  • /PAE
  • /USERVA
  Note Loading these switches decreases the amount of non-paged pool bytes available to SQL Server.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.

For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the terminology that Microsoft uses when correcting software after it is released, click the following article number to view the article in the Microsoft Knowledge Base: