RPC does not accept more than 1,234 concurrent connections to an auto-listen interface on a Windows Server 2003-based server (921412)
The information in this article applies to:
- Microsoft Windows Server 2003, Standard Edition
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Datacenter Edition
- Microsoft Windows Server 2003, Standard x64 Edition
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, Datacenter x64 Edition
- Microsoft Windows Server 2003 Enterprise Edition for Itanium-based Systems
SYMPTOMSYou use a Microsoft Windows Server 2003-based server to host a Microsoft remote procedure call (RPC) auto-listen interface. In this scenario, RPC does not accept more than 1,234 concurrent connections to the auto-listen interface. This problem occurs even when the server has available resources to accept more connections.CAUSEThis problem occurs because of a code defect in Windows Server 2003. When the MaxCalls parameter uses the 1234 setting, RPC is supposed to accept the maximum number of concurrent connections that are possible on the server. However, RPC accepts a maximum of 1,234 concurrent connections on the server when the MaxCalls parameter uses the 1234 setting.RESOLUTIONHotfix informationA 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, we recommend that you wait for the next Windows Server 2003 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 telephone 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. Prerequisites
No prerequisites are required. Restart requirement
You must restart your 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, 64-bit x64-based versions |
Rpcrt4.dll | 5.2.3790.2737 | 1,716,736 | 30-Jun-2006 | 16:53 | x64 | SP1QFE | Wrpcrt4.dll | 5.2.3790.2679 | 626,688 | 30-Jun-2006 | 16:53 | x86 | WOW |
Windows Server 2003, 64-bit Itanium-based versions |
Rpcrt4.dll | 5.2.3790.2737 | 2,464,256 | 30-Jun-2006 | 16:47 | IA-64 | SP1QFE | Wrpcrt4.dll | 5.2.3790.2737 | 626,688 | 30-Jun-2006 | 16:48 | x86 | WOW |
Windows Server 2003, 32-bit x86-based versions |
Rpcrt4.dll | 5.2.3790.2737 | 643,584 | 30-Jun-2006 | 15:33 | x86 | SP1QFE |
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Major | Last Reviewed: | 8/28/2006 |
---|
Keywords: | kbinfo kbfix kbQFE kbhotfixserver kbpubtypekc KB921412 kbAudITPRO |
---|
|