Microsoft Knowledge Base Email Alertz

User profiles are corrupted after you log off from a remote desktop session to a Windows Server 2003 Terminal Server on which Symantec AntiVirus 10.1 is installed

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

User profiles are corrupted after you log off from a remote desktop session to a Windows Server 2003 Terminal Server on which Symantec AntiVirus 10.1 is installed

Article ID: 951029 - View products that this article applies to.
System TipThis article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you. Visit the Windows Vista Solution Center

SYMPTOMS

Consider the following scenario:
  1. You use a remote desktop session to access a Windows Server 2003 Terminal Server on which Symantec AntiVirus 10.1 is installed.
  2. You create a Group Policy setting to delete the user profile after you log off from the remote desktop session to Terminal Server.
In this scenario, after you log off from the remote desktop session to Terminal Server, changes to the user profile are not saved correctly on the profile server, and the user profile is corrupted.

Additionally, when you try to log on to Terminal Server again, you receive the following error message:
Windows cannot find the local profile and is logging you on with a temporary profile. Changes to this profile will be lost when you logoff
After you log on to the computer, the Windows operating system creates a temporary profile for your user account. Additionally, error messages that resemble the following may be logged in the Application log.

Message 1


Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1511
Date: Date
Time: Time
User: User_Name
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.

Message 2


Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1512
Date: Date
Time: Time
User: User_Name
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.

Message 3


Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1518
Date: Date
Time: Time
User: User_Name
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.

CAUSE

This problem occurs because of an issue in Symantec AntiVirus 10.1.

RESOLUTION

To resolve this problem, contact Symantec for help. For more information, see the following Symantec Web site:
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2006090708312648
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Properties

Article ID: 951029 - Last Review: April 15, 2008 - Revision: 1.0
APPLIES TO
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
Keywords: 
kbexpertiseinter kbtshoot kbprb KB951029
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate