Microsoft KB Archive Search

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.

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

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

View products that this article applies to.

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 <CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=lcds,DC=lab> <The file must be present at the location>\\server name\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:
$Account NameConflict0
$Account NameConflict1

↑ Back to the top

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.

↑ Back to the top

Resolution

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

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 883271
Revision : 3
Created on : 10/30/2006
Published on : 10/30/2006
Exists online : False
Views : 444