Computer Profile errors after migration to AD

From: Teo Chee Yang (anonymous_at_discussions.microsoft.com)
Date: 05/31/04


Date: Sun, 30 May 2004 23:23:28 -0700

I've have had some profile errors after the users are
migrated to the AD domain. The errors as logged in the
Event Viewer are as follow:

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1502
Date: 2004-5-22
Time: 16:05:37
User: NT AUTHORITY\SYSTEM
Computer: <computer name>

Description:

Windows cannot load the locally stored profile. Possible
causes of this error include insufficient security rights
or a corrupt local profile. If this problem persists,
contact your network administrator.

 DETAIL - The process cannot access the file because it
is being used by another process.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1508
Date: 2004-5-22
Time: 16:05:32
User: NT AUTHORITY\SYSTEM
Computer: <computer name>
Description:

Windows was unable to load the registry. This is often
caused by insufficient memory or insufficient security
rights.

 DETAIL - The process cannot access the file because it
is being used by another process. for C:\Documents and
Settings\<username>.<nt domain>\ntuser.dat

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1511
Date: 2004-5-22
Time: 15:25:28
User: AP\<username>
Computer: <computer name>

Description:

Windows cannot find the local profile and is logging you
on with a temporary profile. Changes you make to this
profile will be lost when you log off.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1515
Date: 2004-5-22
Time: 15:25:25
User: AP\<username>
Computer: <computer name>

Description:

Windows has backed up this user's profile. Windows will
automatically try to use the backed up profile the next
time this user logs on.

For more information, see Help and Support Center

The weird thing is that if the user login to NT4 domain,
instead of AD domain, there is no profile issue.
Therefore, i think the profile is not corrupted, but
rather "locked" by another apps/services. I've even tried
to stop all non-MS services but to no avail.

So far, I solve all the profile issues by manual rebuild.
Any idea how to solve this once and for all?



Relevant Pages

  • Re: How do you all manage employee workstations? Looking for sugge
    ... When enabled roaming profiles, users have same profiles ... been authenticated within the directory service, the user profile, ... You can use group policy to assign software to all workstations. ... How to use Group Policy to remotely install software in Windows Server 2003 ...
    (microsoft.public.windows.server.sbs)
  • RE: NTUser.Dat error when translatin profiles on workstation
    ... as Administrator and adding the Windows 2003 user w/Full Control ... or the User State Migration Tool for Windows 2000/XP clients. ... Microsoft Online Partner Support ... The roaming profile cannot be ...
    (microsoft.public.windows.server.migration)
  • Account Unknown User Profile
    ... see Help and Support Center at ... Windows cannot load the locally stored profile. ... the administrator account I get this following error: ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Problem Loading Profiles
    ... Windows 2000 Adv with Terminal Services. ... Event Source: Userenv ... Windows cannot log you on because the profile cannot be loaded. ... logs that relate to it. ...
    (microsoft.public.windows.terminal_services)
  • Re: Windows Server 2003 Service Pack 1 will not install
    ... You can try to install the Windows 2003 ... Expand to Windows Logs -> Application and right-click to select Save ... of the public folder database files. ... domain to the new SBS 2003 installation, way is to create a local profile, ...
    (microsoft.public.windows.server.sbs)