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

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:Note This error code translates to the following: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.

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:

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

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, x86-based versions

Windows Server 2003, x64-based versions

Windows Server 2003, Itanium-based versions

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 Windows Server 2003 Service Pack 2.

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: