Article ID: 913957
Article Last Modified on 10/11/2007
APPLIES TO
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
- Microsoft Windows Server 2003, Datacenter x64 Edition
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Standard x64 Edition
SYMPTOMS
Consider the following scenario. You quickly make multiple remote procedure calls (RPCs) to a server that is running Microsoft Windows Server 2003. The multiple RPCs are on the same endpoint. In this scenario, a 0x6be exception may occur.
CAUSE
This problem occurs because an RPC can reuse a TCP connection that the server has already asked to close. When the RPC does this, the server responds by using an ACK/RST packet. Additionally, the server causes the 0x6be exception to occur on the client computer.
RESOLUTION
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
Hotfix information
Prerequisites
There are no prerequisites for this hotfix.
Restart information
You do not have to restart the computer after you apply this hotfix.
Registry information
You do not have to change the registry.
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 32-bit versions
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Rpcrt4.dll | 5.2.3790.2684 | 645,632 | 18-Apr-2006 | 03:19 | x86 |
| W03a2409.dll | 5.2.3790.2684 | 24,576 | 18-Apr-2006 | 01:38 | x86 |
Windows Server 2003 64-bit version
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Rpcrt4.dll | 5.2.3790.2684 | 1,720,832 | 18-Apr-2006 | 03:12 | x64 |
| W03a2409.dll | 5.2.3790.2684 | 25,088 | 18-Apr-2006 | 03:12 | x64 |
Windows Server 2003 Itanium-based versions
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Rpcrt4.dll | 5.2.3790.2684 | 2,470,912 | 18-Apr-2006 | 03:12 | IA-64 |
| W03a2409.dll | 5.2.3790.2684 | 23,552 | 18-Apr-2006 | 03:12 | IA-64 |
STATUS
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 Windows Server 2003 Service Pack 2.
MORE INFORMATION
For more information, 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 KB913957
