Article ID: 905865
Article Last Modified on 10/11/2007
APPLIES TO
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, Standard x64 Edition
- Microsoft Windows Server 2003, Datacenter x64 Edition
SYMPTOMS
When you use Terminal Services to log on to or to log off from a computer that is running Microsoft Windows Server 2003, the sizes of the working sets of all the processes in the console session may be trimmed to the sizes just after the computer started up. This reduction in the sizes of the working sets may be temporary. The reduction occurs whether the computer is a workgroup computer, a member server, or a domain controller.
As the working sets are trimmed, data in memory may be written to the page file. This behavior increases disk activity. Eventually, you may receive a "Virtual memory minimum too low" error message.
Sometimes, all the bytes in the page file may be used. The performance of the computer may decrease until the working sets return to their cached state. The working sets may be trimmed even if there is enough physical memory to satisfy current memory demands. Or, the working sets may be trimmed even if there is enough physical memory to cache the whole contents of file-based stores. These file-based stores may include the Active Directory directory service database and Microsoft SQL Server databases.
This problem affects the working sets of all the services that are running on the computer. These services include services that are running on behalf of the core operating system and programs that are running on the local server. The services that improve their performance by caching file-based stores are most affected by the trimming of working sets.
This problem occurs when you use Terminal Services to connect to a computer that is running Windows Server 2003 with Service Pack 1 or with hotfix 834293 applied.
Note When you log on or log off the physical console of the computer, the working set is not trimmed.
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
To resolve this problem, apply this hotfix to all computers that are running Windows Server 2003 with Service Pack 1. Then, add the hotfix to the build server installation process so that the hotfix is included in future installations of Windows Server 2003 with Service Pack 1.
Prerequisites
Because of file dependencies, this hotfix requires Microsoft Windows Server 2003 Service Pack 1. 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
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 tool in Control Panel.
Windows Server 2003, 32-bit versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Msgina.dll | 5.2.3790.2525 | 1,211,904 | 08-Sep-2005 | 05:21 | x86 | SP1 | SP1QFE |
Windows Server 2003, x64-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Msgina.dll | 5.2.3790.2525 | 1,193,472 | 07-Sep-2005 | 15:14 | x64 | SP1 | SP1QFE |
| Wmsgina.dll | 5.2.3790.2525 | 1,211,904 | 07-Sep-2005 | 15:14 | x86 | SP1 | WOW |
Windows Server 2003, Itanium-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Msgina.dll | 5.2.3790.2525 | 1,465,856 | 07-Sep-2005 | 15:13 | IA-64 | SP1 | SP1QFE |
| Wmsgina.dll | 5.2.3790.2525 | 1,211,904 | 07-Sep-2005 | 15:13 | x86 | SP1 | WOW |
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 Microsoft Windows Server 2003 Service Pack 2.
MORE INFORMATION
Notes
- No event or log file tracks Terminal Services logons to a remote Windows Server 2003-based computer. The Security event log tracks logon and logoff transactions, but does not distinguish Terminal Services logons.
- The Qwinsta utility interactively detects Terminal Services sessions on a local or remote computer. To obtain syntax information, type qwinsta /? at a command prompt.
- To see the memory drop that is associated with this problem, use System Monitor to track a process's working set. Or, use Task Manager to view memory usage.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
834293 Window states may not be restored correctly when you disconnect and then reconnect to Remote Desktop
Additional query words: Winx64 Windowsx64 64bit 64-bit
Keywords: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver kbwinserv2003presp2fix kbwinserv2003sp2fix KB905865
