The sizes of the working sets of all the processes in a console session may be trimmed when you use Terminal Services to log on to or log off from a computer that is running Windows Server 2003

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.

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:

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.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:

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

Windows Server 2003, x64-based versions

Windows Server 2003, Itanium-based versions

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.

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: