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.

Hotfix is available that corrects "User�s SID" in event ID 6035 in Windows Server 2008 R2


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You are a member of more than 1,015 groups in a domain environment.
  • You try to log on to Active Directory and the logon authentication fails.
  • Event ID 6035 is logged on the Windows Server 2008 R2-based domain controller.
In this scenario, the system SID is displayed in the event message instead of the user�s SID.

For example, the following event displays the "User�s SID" information in the form of 53002D0031002D00:

During a logon attempt, the user's security context accumulated too many security IDs. This is a very unusual situation. Remove the user from some global or local groups to reduce the number of security IDs to incorporate into the security context.
User's SID is 53002D0031002D00


However, the expected event message resembles the following:

During a logon attempt, the user's security context accumulated too many security IDs. This is a very unusual situation. Remove the user from some global or local groups to reduce the number of security IDs to incorporate into the security context.
User's SID is DomainName\UserName

↑ Back to the top


Cause

This issue occurs because of an incorrect string format.

↑ Back to the top


Resolution

Administrators can do a test on the global catalog in a lab environment before applying the hotfix in a production environment. Run the following PowerShell script to find potential users who have large number of group memberships:

Note The script may run for multiple hours in a very large Active Directory.
cls
Get-Date -format F
$ADUsers = Get-AdUser -Filter * -ResultPageSize 1000 -ResultSetSize $null
ForEach ($ADUser in $ADUsers)
{
$UserAccount = [ADSI]"LDAP://$ADUser"
$UserAccount.GetInfoEx(@("tokengroupsglobalanduniversal"),0)
$Groups = $UserAccount.Get("tokengroupsglobalanduniversal")
If ($Groups.Count -ge 1000)
{
Write-Host "[" $ADUser.distinguishedName "] belongs to " $Groups.Count " groups."
}
}
Write-Host "`n###################`n " $ADUsers.Count " AD users checked."
Get-Date -format F
The following is an example of the output that this script generates:
Monday, January 28, 2013 5:04:34 PM
[ CN=tester1,OU=Test,DC=TestDomain,DC=com ] belongs to 1024 groups.
[ CN=tester22,OU=Test,DC=TestDomain,DC=com ] belongs to 1024 groups.
[ CN=tester1022,OU=Test,DC=TestDomain,DC=com ] belongs to 1024 groups.

###################
10002 AD users checked.
Monday, January 28, 2013 5:06:15 PM

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 the problem described in this article. 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 website: 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 be running Windows Server 2008 R2 Service Pack 1 (SP1).

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760 1.22xxxWindows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Cng.sys6.1.7601.22076458,70406-Dec-201223:02x64
Ksecdd.sys6.1.7601.2227695,59208-Mar-201305:28x64
Ksecpkg.sys6.1.7601.22276154,47208-Mar-201305:28x64
Lsasrv.dll6.1.7601.222761,446,40008-Mar-201305:23x64
Lsass.exe6.1.7601.2227630,72008-Mar-201303:00x64
Secur32.dll6.1.7601.2227628,16008-Mar-201305:25x64
Sspicli.dll6.1.7601.22276135,68008-Mar-201305:26x64
Sspisrv.dll6.1.7601.2227628,67208-Mar-201305:26x64
Ncrypt.dll6.1.7601.22276307,20008-Mar-201305:24x64
Schannel.dll6.1.7601.22276341,50408-Mar-201305:25x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Cng.sys6.1.7601.22076789,02406-Dec-201222:55IA-64
Ksecdd.sys6.1.7601.22276179,54408-Mar-201304:33IA-64
Ksecpkg.sys6.1.7601.22276316,24808-Mar-201304:33IA-64
Lsasrv.dll6.1.7601.222762,657,28008-Mar-201304:32IA-64
Lsass.exe6.1.7601.2227656,32008-Mar-201304:31IA-64
Secur32.dll6.1.7601.2227648,64008-Mar-201304:32IA-64
Sspicli.dll6.1.7601.22276275,45608-Mar-201304:32IA-64
Sspisrv.dll6.1.7601.2227646,08008-Mar-201304:32IA-64
Ncrypt.dll6.1.7601.22276551,93608-Mar-201304:32IA-64
Schannel.dll6.1.7601.22276711,68008-Mar-201304:32IA-64

↑ 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

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.22276_none_04bb2fa88cb7619a.manifest
File versionNot applicable
File size101,128
Date (UTC)08-Mar-2013
Time (UTC)13:09
PlatformNot applicable
File nameAmd64_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.22276_none_bc4efa7821883807.manifest
File versionNot applicable
File size2,741
Date (UTC)08-Mar-2013
Time (UTC)13:10
PlatformNot applicable
File nameAmd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.22276_none_8086eff4852f0025.manifest
File versionNot applicable
File size12,921
Date (UTC)08-Mar-2013
Time (UTC)13:12
PlatformNot applicable
File nameWow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.22276_none_0f0fd9fac1182395.manifest
File versionNot applicable
File size87,695
Date (UTC)08-Mar-2013
Time (UTC)13:13
PlatformNot applicable
File nameWow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.22276_none_8adb9a46b98fc220.manifest
File versionNot applicable
File size6,945
Date (UTC)08-Mar-2013
Time (UTC)13:12
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.22276_none_a89e381ad457f960.manifest
File versionNot applicable
File size101,126
Date (UTC)08-Mar-2013
Time (UTC)13:15
PlatformNot applicable
File nameIa64_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.22276_none_603202ea6928cfcd.manifest
File versionNot applicable
File size2,739
Date (UTC)08-Mar-2013
Time (UTC)13:15
PlatformNot applicable
File nameIa64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.22276_none_2469f866cccf97eb.manifest
File versionNot applicable
File size12,920
Date (UTC)08-Mar-2013
Time (UTC)13:17
PlatformNot applicable
File nameWow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.22276_none_0f0fd9fac1182395.manifest
File versionNot applicable
File size87,695
Date (UTC)08-Mar-2013
Time (UTC)13:13
PlatformNot applicable
File nameWow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.22276_none_8adb9a46b98fc220.manifest
File versionNot applicable
File size6,945
Date (UTC)08-Mar-2013
Time (UTC)13:12
PlatformNot applicable

↑ Back to the top


Keywords: kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced, KB2824066

↑ Back to the top

Article Info
Article ID : 2824066
Revision : 3
Created on : 4/16/2013
Published on : 4/16/2013
Exists online : False
Views : 1776