Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

A memory leak occurs every time that you use a smart card to authenticate against a Windows Server 2003-based domain controller


View products that this article applies to.

Symptoms

A memory leak occurs when you use a smart card to authenticate against a Windows Server 2003-based domain controller. If many users authenticate by using smart cards, the domain controller may run out of memory. Therefore, the domain controller stops responding to authentication requests until you restart the domain controller.

Additionally, the following events are logged in the Application log.

Event ID 1097

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1097
Date: Date
Time: Time
User: NT AUTHORITY\SYSTEM
Computer: ComputerName
Description:
Windows cannot find the machine account, Not enough memory is available to complete this request.

Event ID 1053

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1053
Date: Date
Time: Time
User: NT AUTHORITY\SYSTEM
Computer: ComputerName
Description:
Windows cannot determine the user or computer name. (Not enough storage is available to complete this operation. ). Group Policy processing aborted.

Event ID 1015

Event Type: Error
Event Source: Winlogon
Event Category: None
Event ID: 1015
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
A critical system process, SystemRoot\system32\lsass.exe, failed with status code c0000005. The machine must now be restarted.

↑ Back to the top


Resolution

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.

Prerequisites

To apply this hotfix, you must have the following prerequisites installed on the computer:
  • Active Directory directory service
  • Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2

    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 item in Control Panel.
Windows Server 2003 with Service Pack 1, x86-based versions
File nameFile versionFile sizeDateTimePlatform
Kdcsvc.dll5.2.3790.3173220,16011-Jul-200817:11x86
Windows Server 2003 with Service Pack 2, x86-based versions
File nameFile versionFile sizeDateTimePlatform
Kdcsvc.dll5.2.3790.4332220,16011-Jul-200817:06x86
Windows Server 2003 with Service Pack 1, Itanium-based versions
File nameFile versionFile sizeDateTimePlatform
Kdcsvc.dll5.2.3790.3173615,93611-Jul-200815:03IA-64
Windows Server 2003 with Service Pack 2, Itanium-based versions
File nameFile versionFile sizeDateTimePlatform
Kdcsvc.dll5.2.3790.4332615,93611-Jul-200815:06IA-64
Windows Server 2003 with Service Pack 1, x64-based versions
File nameFile versionFile sizeDateTimePlatform
Kdcsvc.dll5.2.3790.3173419,84011-Jul-200815:03x64
Windows Server 2003 with Service Pack 2, x64-based versions
File nameFile versionFile sizeDateTimePlatform
Kdcsvc.dll5.2.3790.4332419,84011-Jul-200815:08x64

↑ Back to the top


Status

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

↑ Back to the top


More information

For more information about software update terminology, 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

↑ Back to the top


Keywords: kbautohotfix, kbexpertiseinter, kbwinserv2003postsp2fix, kbbug, kbfix, kbqfe, KB955410

↑ Back to the top

Article Info
Article ID : 955410
Revision : 2
Created on : 10/8/2011
Published on : 10/8/2011
Exists online : False
Views : 324