Link to home
Start Free TrialLog in
Avatar of j_crow1
j_crow1

asked on

"Windows cannot log you on because your profile cannot be loaded" error trying to connect through Terminal Services.

I just installed a new terminal server, I copied all of the profiles from the old server to the new server, but I have ONE user that gets this error message when she connects:

Windows cannot log you on because your profile cannot be loaded.  Check that you are connected to the network or that your network is functioning correctly.

I installed UPHClean and ran it with no results. I have also completely deleted the profile and tried to log in again to have it recreate everything, all I get is the same error message.

Any suggestions?

Thanks in advance.
Avatar of MentorJay
MentorJay

Delete the profile, then delete the folder under c:\documents and settings
Recreate the profile, then copy the files back, but not the .DAT files, which are registry extensions.

Only copy my documents, favorites, local settings, etc.
Check that user's account in ADUC and make sure their profile path is set correctly.

eb
In ADUC there are two profile paths, one for the terminal server profile, make sure that BOTH are setup correctly.  It is likely to be a typo in the second profile path for that user.
Avatar of Cláudio Rodrigues
The only one needed for TS is the Terminal Services Profile Path. If both are set TS will use the TS specific one. If only the generic one is set it will use that (what is not a good idea).
Make sure the user has rights to the share where the profile is AND NTFS rights as well.

Cláudio Rodrigues

Microsoft MVP
Windows Server - Terminal Services
Avatar of j_crow1

ASKER

I do not have any of the users TS paths set, it usually just creates the profile automatically. Mentor: what do you mean the profile? I have just been deleting the profile folder the entire time.
Avatar of j_crow1

ASKER

Ok i copied her old profile from the old TS and it is still giving me the same error message. Although I am looking at the Documents and Settings directory and when i try to log in it creates another folder with USERNAME.DOMAIN

I am also now having this problem with the Presidents profile - need help quick!
Avatar of j_crow1

ASKER

Just thought I would post the info from event log:

Event Type:       Error
Event Source:    Userenv
Event Category: None
Event ID:           1500
Date:                4/8/2008
Time:                2:18:43 PM
User:                DOMAIN\username
Computer:         TS-SERV
Description:
Windows cannot log you on because your profile cannot be loaded. Check that you are connected to the network, or that your network is functioning correctly. If this problem persists, contact your network administrator.

 DETAIL - Access is denied.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Avatar of j_crow1

ASKER


EB:
It has SP2 on it - Could this still be an issue even though SP2 is installed?
Avatar of j_crow1

ASKER

Something else that is interesting:

When i tried to log on with my newly created test account, it gives the same error message. Could the default User profile be messed up or something? How would i fix something like this?

ASKER CERTIFIED SOLUTION
Avatar of j_crow1
j_crow1

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Try reassigning ownership to the new user which you've just created, not the user with the same name who no longer exists.
I had the exact same problem as Jcrow.  I created a test user in ADUC and made him a member of the remote desktop users group.  Then I tried to login to a terminal server running 2k3.  I received the error: windows can not log you in because your profile can not be loaded.  check that you are connected to your network and that your network is functioning correctly.  If the problem persists contact your network administrator.  Details - Access Denied.

I never saw the details section before, because you have to scroll down.  But, when I did finally see it, i immediately logged in under my domain admin account and looked at the ntfs permissions for the documents and settings folder.  I quickly saw that it was not inheriting permissions.  All it had was users and system.  When I inherited permissions, it added creator owner, administrators.  

All users were immediately able to log in at that point.  Hope this helps.