Microsoft KB Archive/883271

= Event ID 1053 and 1058 appear in the Application log after you upgrade to Windows 2000 Server or Windows Server 2003 with Active Directory =

Article ID: 883271

Article Last Modified on 10/30/2006

-

APPLIES TO


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

-





SYMPTOMS
After you upgrade from Microsoft Windows NT 4.0 to Microsoft Windows 2000 Server or to Microsoft Windows Server 2003, group policies are not applied to some users. The following events appear in the Application log:

Source: Userenv

Category: None

Type: Error

Event ID: 1053

Description:

Windows cannot determine the user or computer name. (No mapping between account names and security IDs was done). Group Policy processing aborted.

Event Type: Error

Event Source: Userenv

Event ID: 1058

User: NT AUTHORITY\SYSTEM

Description:

Windows cannot access the file gpt.ini for GPO  \\ \Policies\{31B2F340-016D-11D2-945F-00C04FB984F9} (Access is denied). Group Policy processing aborted.

Event Type: Error

Event Source: Userenv

Event Category: None

Event ID: 1030

User: N/A

Description:

Windows cannot query for the list of Group Policy objects. A message that describes the reason for this was previously logged by the policy engine.

After you upgrade to Active Directory, some user accounts are renamed. For example, the following user accounts are renamed:

$ Conflict0

$ Conflict1



CAUSE
This issue may occur if you have account names that use non-ASCII characters, such as ö and é. Windows 2000 Server and Windows Server 2003 do not distinguish between non-ASCII and ASCII characters in account names.

Windows NT 4.0 distinguishes between ASCII and non-ASCII characters in account names. For example, in a Windows NT 4.0-based domain, you can use Administrator and Administratör as separate account names. However, in Active Directory, both Administrator and Administratör effectively have the same logon credentials. This scenario causes the conflict.



RESOLUTION
To resolve this issue, you must either delete or rename the conflicting accounts.

Keywords: kbtshoot kbactivedirectory kberrmsg kbpolicy kblocalization kbevent kbuser kbupgrade kbinterop KB883271

-

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

© Microsoft Corporation. All rights reserved.