Microsoft KB Archive/937535

= Event ID 1053 is logged when you use the &quot;Gpupdate /force&quot; command, or you restart a Windows Server 2003-based domain controller =

Article ID: 937535

Article Last Modified on 6/6/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)

-



Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
When you use the Gpupdate /force command on a Microsoft Windows Server 2003-based domain controller, or you restart a Windows Server 2003-based domain controller, the following error message may be logged in the Application log:

Event Type: Error

Event Source: Userenv

Event Category: None

Event ID: 1053

Date:

Time:

User: NT AUTHORITY\SYSTEM

Computer:

Description:

Windows cannot determine the user or computer name. (Not enough storage is available to complete this operation. ). Group Policy processing aborted. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Additionally, if you enable USERENV logging, the following entries may be logged in the Userenv.log file:

USERENV(1b4.eb4) 13:30:54:531 MyGetUserName: GetUserNameEx failed with 14.

USERENV(1b4.eb4) 13:30:54:531 MyGetUserName: Retrying call to GetUserNameEx in 1/2 second.



RESOLUTION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this problem, add the MaxTokenSize registry entry and the MaxUserPort registry entry on the affected domain controllers. To do this, follow these steps:  Click Start, click Run, type regedit, and then click OK. Locate and then right-click the following registry subkey:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\Kerberos\Parameters

Note If the  key is not available, you must create it. To create the  key, follow these steps:  Click the following registry subkey:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\Kerberos

 On the Edit menu, click New, and then click Key. Type Parameters, and then press ENTER.  Click the Parameters key, click New on the Edit Menu, and then click DWORD Value.</li> Type MaxTokenSize, and then press ENTER.</li> Right-click MaxTokenSize, and then click Modify.</li> In the Value data box, type 65535, click Decimal, and then click OK.</li> Locate and then right-click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

</li> On the Edit menu, click New, click DWORD Value, type MaxUserPort, and then press ENTER.</li> In the Value data box, type a value between 5000 and 6534, click Decimal, and then click OK.

Note The default value for the MaxUserPort registry entry is 5000.</li> Exit Registry Editor.</li> Restart the computer.</li></ol>

Keywords: kbtshoot kbexpertiseadvanced kbprb KB937535

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.