Profile error on Windows Server 2008

I recently setup a windows 2008 Terminal Server.  I connected fine and another person connected successfully.  I then received a complaint that a third user could not logon.  It would hang on his profile when he tried to connect.   I looked at the event log and found the following message in the Application log

Windows cannot load the locally stored profile. Possible causes of this error include insufficient security rights or a corrupt local profile.

 DETAIL - The configuration registry database is corrupt.

Log Name: Application
Source:      User Profile Service
Event ID: 1502
Level: Error
User: MyDomain\Fred
OpCode: Info
Task Category: None
Keywords: Classic
Computer: s3.MyDomain.local

I checked another Terminal Server running Windows Server 2008 and I could not find the error in the logs.

This is a new installation which I just added to the domain this past Thursday.  Both users who have tested this server generate the error in the Application log but one hangs and the other can log on successfully.  When I logon with a local profile I generate no errors.  

I checked the settings for the users and their default profile and personal folder are set in their user settings to a separate server.  

Is there a way to resolve this issue without starting over?




qvfpsAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Sector5Commented:
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
joenswCommented:
hi

"According To Microsoft:"
Explanation:
This error can occur if the user profile registry hive gets corrupted or if permissions are set incorrectly on the profile folders.

User Action:
To troubleshoot this problem, try the following:
1. Review the Event Viewer logs and look for related profile (userenv) events to obtain additional details about this error.
2. If the user profile registry hive (ntuser.dat, the user profile registry hives supporting file) is corrupted, replace ntuser.dat with a backup copy of this file.
3. Verify that permissions are set correctly on the local user profile folders. On a computer that has a clean installation (with no previous operating system) of Windows Server 2003, Windows XP, or Windows 2000 operating system, the user profile folders are stored in system_drive\Documents and Settings; for example, C:\Documents and Settings.

follow this link:

http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows%20Operating%20System&ProdVer=5.2&EvtID=1502&EvtSrc=Userenv&LCID=1033
0
qvfpsAuthor Commented:
The error is generated when using remote profiles.   Both users who have tested this server have their profiles stored on a remote server and the path is set under Active Directery users/ and omputers.   The one user who has a local profile only logs on with no issues and no errors in the logs.  

It should not be a permissions error on the profile folder since they have been using this setup to connect to two other Terminal Servers one running Windows Server 2003 and one running Windows Server 2008.  I have checked the logs on the  current Windows 2003 server and the WIndows 2008 server and I do not find the error in the application logs.  
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

joenswCommented:
hi
set permissions full control in the remote profiles folder
0
qvfpsAuthor Commented:
The permissions on the remote profile folder are currently set to full
0
qvfpsAuthor Commented:
The answers were helpful in checking permissions but the problem was the profiles being stored on a remote server
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.