Article ID: 913560
Article Last Modified on 10/11/2007
APPLIES TO
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Web Edition
- 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, Standard x64 Edition
SYMPTOMS
When you use Microsoft Windows Server 2003-based domain controllers, the File Replication service (FRS) may experience a memory leak. Over time, the memory leak consumes lots of memory on busy domain controllers. You may experience failures in FRS.
CAUSE
This problem occurs because FRS does not release allocated memory after FRS reads from the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Access Checks
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
No prerequisites are required.
Restart requirement
You must restart FRS 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
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Updspapi.dll | 6.2.29.0 | 371,424 | 12-Oct-2005 | 23:13 | x86 |
| Ntfrs.exe | 5.2.3790.2621 | 792,064 | 19-Jan-2006 | 02:05 | x86 |
Windows Server 2003, Itanium-based versions
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Ntfrs.exe | 5.2.3790.2621 | 1,897,472 | 18-Jan-2006 | 14:33 | IA-64 |
| Wntfrs.exe | 5.2.3790.2621 | 792,064 | 18-Jan-2006 | 14:33 | x86 |
| Updspapi.dll | 6.2.29.0 | 638,688 | 18-Jan-2006 | 14:34 | IA-64 |
Windows Server 2003, x64-based versions
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Ntfrs.exe | 5.2.3790.2621 | 1,158,144 | 18-Jan-2006 | 14:32 | x64 |
| Wntfrs.exe | 5.2.3790.2621 | 792,064 | 18-Jan-2006 | 14:33 | x86 |
| Updspapi.dll | 6.2.29.0 | 462,048 | 18-Jan-2006 | 14:34 | x64 |
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 kbwinserv2003presp1fix kbhotfixserver kbwinserv2003sp2fix KB913560
