Microsoft KB Archive/917114

= Error code when you use the Winsock Select function on a Windows Server 2003-based multiprocessor computer: &quot;WSAENOBUFS (10055)&quot; =

Article ID: 917114

Article Last Modified on 10/11/2007

-

APPLIES TO

 Microsoft Windows Server 2003 R2 Enterprise x64 Edition Microsoft Windows Server 2003 R2 Enterprise Edition (32-Bit x86) Microsoft Windows Server 2003 R2 Standard x64 Edition Microsoft Windows Server 2003 R2 Standard Edition (32-bit x86) Microsoft Windows Server 2003 R2 Datacenter x64 Edition Microsoft Windows Server 2003 R2 Datacenter Edition (32-Bit x86) Microsoft Windows Server 2003 SP1, when used with:  Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems</li></ul>

<ul> Microsoft Windows Server 2003, Enterprise Edition</li></ul>

<ul> Microsoft Windows Server 2003, Standard Edition (32-bit x86)</li></ul>

<ul> Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems</li></ul>

<ul> Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)</li></ul> </li></ul>

-

<div class="symptoms_section">

SYMPTOMS
Consider the following scenario. You run a custom Winsock network program that uses the Winsock Select function. You run this program on a Microsoft Windows Server 2003-based multiprocessor computer. In this scenario, the following error code is returned:

WSAENOBUFS (10055)

Note This error code translates to the following:

An operation on a socket cannot be performed because the system lacks sufficient buffer space or because a queue is full.

Additionally, System Monitor displays a steady increase in non-paged pool memory usage. When you run the Memsnap.exe tool or use the Memory Pool Monitor utility, you discover that the AfdP tag causes this increase in non-paged pool memory usage.

Also, when this behavior occurs, the following event may be logged in the System logs: Event ID 2019

Description: The server was unable to allocate from the system nonpaged pool because the pool was empty.

<div class="resolution_section">

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

889100 How to obtain the latest service pack for Windows Server 2003

Prerequisites
To apply this hotfix, you must have Windows Server 2003 Service Pack 1 (SP1) installed.

Restart requirement
You must restart the computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
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 item in Control Panel.

Windows Server 2003, Itanium-based versions
<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section. This problem was first corrected in Microsoft Windows Server 2003 Service Pack 2.

<div class="moreinformation_section">

MORE INFORMATION
For more information about the terms that are used to describe software updates, 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

Keywords: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver kbwinserv2003presp2fix kbwinserv2003sp2fix KB917114

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.