Article ID: 937535 - Last Review: June 6, 2007 - Revision: 1.3
Event ID 1053 is logged when you use the "Gpupdate /force" command, or you restart a Windows Server 2003-based domain controller
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:Additionally, if you enable USERENV logging, the following entries may be logged in the Userenv.log file:
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. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
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. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
RESOLUTION
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
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:
322756
(http://support.microsoft.com/kb/322756/
)
How to back up and restore the registry in Windows
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\ParametersNote If the Parameters key is not available, you must create it. To create the Parameters 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 following registry subkey:
- Click the Parameters key, click New on the Edit Menu, and then click DWORD Value.
- Type MaxTokenSize, and then press ENTER.
- Right-click MaxTokenSize, and then click Modify.
- In the Value data box, type 65535, click Decimal, and then click OK.
- Locate and then right-click the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
- On the Edit menu, click New, click DWORD Value, type MaxUserPort, and then press ENTER.
- In the Value data box, type a value between 5000 and 65534, click Decimal, and then click OK.
Note The default value for the MaxUserPort registry entry is 5000. - Exit Registry Editor.
- Restart the computer.
Note: This article is from Microsoft Knowledage Base
Related problems posted by other users | |
| more... |

