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. Error message and the terminal server roaming profile is not loaded when you log on to a Windows Server 2003-based terminal server

Error message and the terminal server roaming profile is not loaded when you log on to a Windows Server 2003-based terminal server

View products that this article applies to.

Symptoms

When you are configured to use a roaming profile, and you log on to a Microsoft Windows Server 2003-based terminal Server, your roaming profile may not be loaded. Additionally, the you receive an error message that resembles the following:
Windows cannot locate the server copy of your roaming profile and is attempting to log you on with your local profile. Changes to the profile will not be copied to the server when you logoff. Possible causes of this error include network problems or insufficient security rights. If this problem persists, contact your network administrator.
If user environment logging is turned on, the following message may be logged in the Userenv.log file:
USERENV(274.b80) 11:40:51:949 AbleToBypassCSC: Share \\mdfile11\PROFILES mapped to drive E. Returned Path E:\N003097
USERENV(274.b80) 11:40:51:949 ParseProfilePath: CSC bypassed. Profile path E:\N003097
USERENV(274.b80) 11:40:51:949 ParseProfilePath: GetFileAttributes failed with error 3
USERENV(274.b80) 11:40:51:949 CreateSecureDirectory: Entering with <E:\N003097>
USERENV(274.b80) 11:40:51:949 CreateNestedDirectory: Failed to create the directory with error 3.
USERENV(274.b80) 11:40:51:949 CreateSecureDirectory: Failed to created the directory <E:\N003097>
USERENV(274.b80) 11:40:51:949 ParseProfilePath: Failed to create user sub-directory. Error = 3
USERENV(274.b80) 11:40:51:949 ReportError: Impersonating user.
USERENV(274.b80) 11:40:51:949 ReportError: Logging Error <Windows cannot locate the server copy of your roaming profile and is attempting to log you on with your local profile. Changes to the profile will not be copied to the server when you logoff. Possible causes of this error include network problems or insufficient security rights. If this problem persists, contact your network administrator.
DETAIL - The system cannot find the path specified.

↑ Back to the top

Resolution

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.To resolve this issue, make sure that the value of the ProtectionMode registry entry that is on the terminal server computer is set to 1. To do this, follow these steps.

Note Before you follow these steps, determine whether the registry settings are applied by using a domain policy. If the registry settings are applied by using a default domain policy, you must change the value of the ProtectionMode registry entry by using the default domain policy. In this scenario, if you change the value of the ProtectionMode registry entry on a particular terminal server, the value may be reset after you restart the computer. If this value is reset, the issue may occur again.
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager
  3. In the details pane, double-click ProtectionMode, make sure that 1 appears in the Value Data box, and then click OK.
  4. Close Registry Editor.
  5. Restart the computer.

↑ Back to the top

Keywords: KB935642, kbprb, kberrmsg, kbtshoot, kbexpertiseinter

↑ Back to the top

Article Info
Article ID : 935642
Revision : 3
Created on : 5/10/2007
Published on : 5/10/2007
Exists online : False
Views : 228