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 (891311)
The information in this article applies to:
- Microsoft SQL Server 2000 Developer Edition
- Microsoft SQL Server 2000 Standard Edition
- Microsoft SQL Server 2000 Enterprise Edition
- Microsoft SQL Server 2000 Personal Edition
- Microsoft SQL Server 2000 Enterprise Evaluation Edition
- Microsoft SQL Server 2000 Workgroup Edition
- Microsoft SQL Server 2000 Desktop Engine (MSDE)
- Microsoft SQL Server 2000 Developer Edition 64 bit
- Microsoft SQL Server 2000 Enterprise Edition 64-bit
SUMMARYMicrosoft distributes SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release.SUMMARYThis 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.
IntroductionIssues that are fixed by this hotfix packageThe 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:
290211 How to obtain the latest SQL Server 2000 service pack
CAUSEThis 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. RESOLUTIONService 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: 290211 How to obtain the latest SQL Server 2000 service pack
Hotfix informationPrerequisitesThis 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:
290211 How to obtain the latest SQL Server 2000 service pack
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:
888007 You receive a "The product does
not have a prerequisite update installed" error message when you try to install a SQL Server 2000 post-Service Pack 3 hotfix
WORKAROUNDTo 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:
Note Loading these switches decreases the amount of non-paged pool
bytes available to SQL Server.
STATUSMicrosoft
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.REFERENCES 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: 822499
New naming schema for Microsoft SQL Server software update packages
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: 824684
Description of the standard terminology that is used to describe Microsoft software updates
Modification Type: | Minor | Last Reviewed: | 7/18/2006 |
---|
Keywords: | kbbug kbfix kbHotfixServer kbQFE KB891311 kbAudDeveloper |
---|
|