qvfps
asked on
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?
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?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
hi
set permissions full control in the remote profiles folder
set permissions full control in the remote profiles folder
ASKER
The permissions on the remote profile folder are currently set to full
ASKER
The answers were helpful in checking permissions but the problem was the profiles being stored on a remote server
ASKER
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.