小马

现在是零将来是无限

导航

FIX: Socket Initialization Does Not Succeed if Your Computer Has More Than 50 Network Bound Protocols

 

SYMPTOMS

If you use the Microsoft .NET Framework 1.1, and if your computer has more than 50 network bound protocols, you may receive the following error message:
System.Net.Sockets.SocketException: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.

Reducing the number of network adapters may resolve the problem.

CAUSE

This problem occurs because the System.Net.Socket constructor does not succeed if your computer has more than 50 network bound protocols. This problem occurs if you have any combination of network adapters and protocols that causes your computer to have more than 50 network bound protocols. For example, if the computer has 11 network adapters, and if five protocols are bound to each adapter, the System.Net.Socket constructor will not succeed.

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next .NET Framework 1.1 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this hotfix has the file attributes (or later) 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.
   Date         Time   Version       Size       File name
   -----------------------------------------------------------------------
   16-May-2003  00:49                   34,150  InstallSqlState.sql
   16-May-2003  00:49                   33,522  InstallPersistSqlState.sql
   16-Sep-2003  03:06                   14,472  WebUIValidation.js
   16-Sep-2003  03:11  1.1.4322.946     32,768  Aspnet_wp.exe
   16-Sep-2003  03:11  1.1.4322.946     20,480  Aspnet_regiis.exe
   16-Sep-2003  03:11  1.1.4322.946    258,048  Aspnet_isapi.dll
   16-Sep-2003  17:29  1.1.4322.946  1,253,376  System.Web.dll
   16-Sep-2003  17:28  1.1.4322.946  1,216,512  System.dll
   16-Sep-2003  03:02  1.1.4322.946     94,208  PerfCounter.dll
   16-Sep-2003  17:28  1.1.4322.946    323,584  System.runtime.remoting.dll
   16-Sep-2003  17:29  1.1.4322.946  1,253,376  System.web.dll
   16-Sep-2003  17:29  1.1.4322.946    819,200  System.web.mobile.dll
   16-Sep-2003  17:29  1.1.4322.946    569,344  System.web.services.dll
   16-Sep-2003  17:29  1.1.4322.946  1,335,296  System.xml.dll

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

APPLIES TO
Microsoft .NET Framework 1.1

posted on 2004-12-10 13:04  mahope  阅读(826)  评论(0编辑  收藏  举报