Microsoft KB Archive/931282

From BetaArchive Wiki

Article ID: 931282

Article Last Modified on 10/11/2007



APPLIES TO

  • Microsoft Windows Server 2003 Service Pack 2, when used with:
    • 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, Web 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
    • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
  • Microsoft Windows Server 2003 SP1, when used with:
    • 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, Web Edition
    • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
    • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Datacenter x64 Edition



SYMPTOMS

When a client computer logs off from a Terminal Services session, you receive a Stop error message on the terminal server that resembles the following:

Stop 0x000000AB (SESSION_HAS_VALID_POOL_ON_EXIT)

This problem occurs when the terminal server is running Microsoft Windows Server 2003 with Service Pack 1 (SP1) or with Service Pack 2 (SP2). When this problem occurs, other clients that are logged on to the same terminal server may also stop responding.

CAUSE

This problem occurs because the Ussy tag leaks session pool memory in the Win32k.sys file.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only 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 Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer 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

To apply this hotfix, you must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed. For more information about how to obtain the latest service pack, 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 item in Control Panel.

Windows Server 2003 with Service Pack 2, x86-based versions
File name File version File size Date Time Platform SP requirement
Gdi32.dll 5.2.3790.4033 282,624 02-Mar-2007 06:41 x86 SP2
Win32k.sys 5.2.3790.4065 1,845,760 20-Apr-2007 14:28 x86 SP2
Windows Server 2003 with Service Pack 2, x64-based versions
File name File version File size Date Time Platform SP requirement Service branch
Gdi32.dll 5.2.3790.4033 619,520 20-Apr-2007 20:06 x64 SP2 Not applicable
Win32k.sys 5.2.3790.4065 4,530,688 20-Apr-2007 20:06 x64 SP2 Not applicable
Wgdi32.dll 5.2.3790.4033 290,816 20-Apr-2007 20:06 x86 SP2 WOW
Windows Server 2003 with Service Pack 2, Itanium-based versions
File name File version File size Date Time Platform SP requirement Service branch
Gdi32.dll 5.2.3790.4033 913,408 20-Apr-2007 20:07 IA-64 SP2 Not applicable
Win32k.sys 5.2.3790.4065 5,557,248 20-Apr-2007 20:07 IA-64 SP2 Not applicable
Wgdi32.dll 5.2.3790.4033 290,816 20-Apr-2007 20:07 x86 SP2 WOW
Windows Server 2003 with Service Pack 1, x86-based versions
File name File version File size Date Time Platform SP requirement
Gdi32.dll 5.2.3790.2892 284,160 02-Mar-2007 08:11 x86 SP1
Win32k.sys 5.2.3790.2921 1,854,976 20-Apr-2007 11:39 x86 SP1
Windows Server 2003, x64-based versions
File name File version File size Date Time Platform SP requirement Service branch
Gdi32.dll 5.2.3790.2892 617,472 20-Apr-2007 20:02 x64 SP1 Not applicable
Win32k.sys 5.2.3790.2921 4,537,344 20-Apr-2007 20:02 x64 SP1 Not applicable
Wgdi32.dll 5.2.3790.2892 287,744 20-Apr-2007 20:02 x86 SP1 WOW
Windows Server 2003 with Service Pack 1, Itanium-based versions
File name File version File size Date Time Platform SP requirement Service branch
Gdi32.dll 5.2.3790.2892 909,312 20-Apr-2007 20:02 IA-64 SP1 Not applicable
Win32k.sys 5.2.3790.2921 5,552,640 20-Apr-2007 20:02 IA-64 SP1 Not applicable
Wgdi32.dll 5.2.3790.2892 287,744 20-Apr-2007 20:02 x86 SP1 WOW


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

Other problems may cause similar symptoms. For more information about the "Stop 0x000000AB" error message, click the following article numbers to view the articles in the Microsoft Knowledge Base:

925919 Stop error message when a client computer logs off from a Terminal Services session on a server that is running Windows Server 2003 with S about the "Stop 0x000000AB" error message or with Ss: "Stop 0x000000AB (SESSION_HAS_VALID_POOL_ON_EXIT)"


928942 Error message when you log off a Terminal Services session on Windows Server 2003 Terminal Server with Service Pack 1 or with Service Pack 2: "Stop 0x000000AB"



901050 You may receive a "Stop 0x000000ab" error message when you log off a Terminal Services session on a Windows Server 2003 Service Pack 1-based Terminal Server



907242 You receive a "Stop 0x000000ab" error message when you log off from a Terminal Services session on a Windows Server 2003 Service Pack 1-based terminal server


910362 Error message when you log off from a Terminal Services session on a Windows Server 2003 Service Pack 1-based terminal server: "Stop 0x000000AB SESSION_HAS_VALID_POOL_ON_EXIT"


918673 You receive a "Stop 0x000000ab" error message when a Terminal Services client computer logs off from a Terminal Services session on a Windows Server 2003 Service Pack 1-based Terminal Services computer


923035 Stop error message when a Terminal Services client logs off from a session on a server that is running Windows Server 2003 with Service Pack 1: "Stop 0x000000AB (SESSION_HAS_VALID_POOL_ON_EXIT)"


924806 Stop error message when a client logs off a Terminal Services session on a server that is running Windows Server 2003 with Service Pack 1: "Stop 0x000000AB (SESSION_HAS_VALID_POOL_ON_EXIT)"


For more information about the terms that are used to describe software updates, 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



Additional query words: Stop 0xAB TS session hangs

Keywords: kbbug kbfix kbqfe kbpubtypekc kbexpertiseinter kbhotfixserver kbwinserv2003postsp2fix KB931282