Knowledge Base

The Local Profile Loads Instead of Your Roaming Profile

Article ID: 315763

Article Last Modified on 2/18/2007

APPLIES TO

Microsoft Windows 2000 Service Pack 1
Microsoft Windows 2000 Service Pack 2
Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Service Pack 1
Microsoft Windows 2000 Service Pack 2

This article was previously published under Q315763

SYMPTOMS

When you use a Windows 2000-based computer, the local profile may load instead of the roaming profile. If you use the steps in the following article to install Userenv logging

221833 How to Enable User Environment Debug Logging in Retail Builds of Windows

you may receive error 53:

ParseProfilePath: Entering, lpProfilePath = \\server\share
ParseProfilePath: Tick Count = 0
PingComputer: First time: 0
Fast link. Exiting.
ParseProfilePath: FindFirstFile failed with error 53
ParseProfilePath: Did not create the sub-directory. Generating a new name.
ParseProfilePath: Entering name generating code working with a path of \\server\share.
ParseProfilePath: FindFirstFile failed with error 53
ParseProfilePath: Central profile is unreachable to due error 53, switching to local profile only.

CAUSE

This problem occurs after you install the hotfix in the following Microsoft Knowledge Base article:

304719 DFS Client Does Not Select the Share on a DFS Server in the Same Site

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

WORKAROUND

To work around this problem, install a hotfix that includes a copy of The Userenv.dll file that is dated on or after 14-AUG-2001, such as the hotfix that is referenced in the following Microsoft Knowledge Base article:

314560 SetActiveWindow on Default IME Window Creates an Endless Loop

resolves the issue

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.

MORE INFORMATION

To verify that this is the problem that you are receiving, add a folder name to your profile path, and then add the folder on the server where the profile is located. For example, if the profile path is \\server\share, add a folder to the path so that the user profile is \\server\share\profile. Move all of the user profile data from \\server\share to \\server\share\profile. If the profile loads correctly after you add the folder to the path, you may be experiencing the problem that is described in the Symptoms section in this article.

Additional query words: kbMgmtAdmin

Keywords: kbbug kbfix kbsysadmin kbwin2000sp3fix kbenv KB315763

Microsoft KB Archive/315763

Contents