The user profiel service service failed the logon. User profile cannot be loaded

[bondbill2k2]

The message "The user profiel service service failed the logon. User profile cannot be loaded" for almost all users, I have a couple of accounts it appears to work on including my technician account a student account and a teacher account. We are using roaming profiles in a mainly XP enviroment and server 2003. Profiles must work between the two OS's as staff will be using both daily. All folders have been directed using RSAT on the 7 client and I have read around for this problem but almost all search results were related to the deleting of c:\users... and having to tidy the registry.

 

 

The event viewer shows 3 events:

Warning- The winlogon notificaation subscriber failed a critical notification event.

 

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 log off. This error may be caused by network problems or insufficient security rights.

Details- Access is denied.

 

Windows cannot log you on because your profile cannot be loaded.

 

 

 

So obiously for some reason it cannot find the roaming profile on the server, gives up looking and attempts to load a none existant local profile. What is puzzling me is why can't it find this profile? I can log on with my staff group logon fine, setup in the exact same way as all staff accounts with its profile and homepath in the exact same shared location and the same mapped drives setup in RSAT.

 

This is really bugging me now coming up to the end of term I was planning to build a 7 image and deploy it to our new workstations during the holidays but its not looking good!

Edited July 19, 2011 by bondbill2k2

[Michael]

Have a look at this article This should only affect Vista or 7 and not XP.

 

This problem appears to be related to corrupt profiles. It may be worth doing some disk checks on the server if you're using roaming profiles.

[bondbill2k2]

Have a look at this article This should only affect Vista or 7 and not XP.

 

This problem appears to be related to corrupt profiles. It may be worth doing some disk checks on the server if you're using roaming profiles.

Even when I create new accounts I have the same problem, ill give this a try tho thanks!

[DaveyPitch]

I've seen the same problem myself. Make sure that your users have the appropriate permissions to create profiles in whatever network share you've set up for them. I hadn't set that up properly when I first set up roaming profiles here and ran into the same error message you're getting.

[bondbill2k2]

I've seen the same problem myself. Make sure that your users have the appropriate permissions to create profiles in whatever network share you've set up for them. I hadn't set that up properly when I first set up roaming profiles here and ran into the same error message you're getting.

 

Both the share permissions and folder permissions are full for users required, the staffs profile and homepath areas both allow all staff group members full control, the same goes for students. System and domain administrators also have full control on all these folders.

[Michael]

You could also try unsharing the profiles$ share then re-share it and see if this helps.

[TheMan100]

http://www.edugeek.net/forums/windows-7/60642-user-profile-service-failed-new-users.html

Read the 2nd post, he fixed his problem by removing the $ from the share name.

[DaveyPitch]

Both the share permissions and folder permissions are full for users required, the staffs profile and homepath areas both allow all staff group members full control, the same goes for students. System and domain administrators also have full control on all these folders.

 

Don't know if it'll make a difference, but I've also got 'Creator Owner' with full permissions on the folder the profiles are stored in. You could add that and see if it makes a difference.

[jinnantonnixx]

The permissions are probably OK.

 

See if this works:

 

http://www.edugeek.net/forums/windows-7/78733-windows-7-user-profile-failed-error-again.html#post700415

[bondbill2k2]

You could also try unsharing the profiles$ share then re-share it and see if this helps.

No luck

 

http://www.edugeek.net/forums/windows-7/60642-user-profile-service-failed-new-users.html

Read the 2nd post, he fixed his problem by removing the $ from the share name.

The $ is used to hide a share and shouldn't make any difference, the working accounts are also using a share$

 

Don't know if it'll make a difference, but I've also got 'Creator Owner' with full permissions on the folder the profiles are stored in. You could add that and see if it makes a difference.

Just trying this *waits while it applys to all student folders*

 

The permissions are probably OK.

 

See if this works:

 

http://www.edugeek.net/forums/windows-7/78733-windows-7-user-profile-failed-error-again.html#post700415

I'll give it a go thanks!

[Firefox]

I assume you are using a completely different profile for XP and Win7? and that the profile ends in .V2? this is an inbuilt requirement of windows 7

 

We call our profiles UsernameW7.V2 then then add an environment variable via group policies preferences with a name of osver and the value W7.

 

Within AD we point the users to ProfileShareLocation\Username%osver% the variable that is then applied to Windows 7 will then work out which profile it needs to load.

 

Also clear down any local profiles the affected users might have, also look at HKLM\Software\Microsoft\Windows NT\CurrentVersion\Profilelist expand this key and check none of the SID's below match an affected user....delete if necessary

[Pete10141748]

I've had this happen several times in the past; sometimes it was remedied by using a different W7 machine to log on which then created the profile fine.

 

Other times I fixed it by pointing the user's Profile Path in AD to a folder called "[username]" and logging on to an XP machine, letting that populate the "[username]" folder, then logging on a W7 machine letting it create it's own "[username].V2" folder while pulling in info from the XP profile folder.

 

Other times I have had to delete the user from AD completely and create a new user and profile from scratch.

 

 

It's an annoying issue to be sure! [¬_¬]

[bondbill2k2]

Ok it looks like the the profiles and their paths are causing the issue I just tryed changing the test account profile to \server\profiles$\technicians.v2 in AD and logged on fine.

What is this %osver% your speak of oh wise one

[Firefox]

Within your AD path you put username%osver%

 

You then create profiles for each OS with the OS version in the profile name e.g usernameXP usernameW7.v2

 

Then on your XP machines you create an environment variable with the name osver and value XP

for Windows 7 machines do the same but the variable is W7 - these can be both set via GPO

 

Then when you logon, AD will put th ecorrect profile depending on your OS

[bondbill2k2]

Our profiles are set in a profile share then in folders for groups, 1 profile per group e.g. \students \staff \tech \admin.

Having managed to get some of each group to log in on a windows 7 machine now and the logon populating a .v2 folder for each some users from all groups are now able to logon but not others!

Edited July 21, 2011 by bondbill2k2

[Firefox]

For our servers we use accounts that don't actually have profiles attached (speeds up login) but you could add an environment variable to your servers should you so wish ;-)

[bondbill2k2]

For our servers we use accounts that don't actually have profiles attached (speeds up login) but you could add an environment variable to your servers should you so wish ;-)

Might just do this tbf, I've taken over from a previous technician and never had much to do with profiles until now as its all worked! Doesn't appear to be much there beside about 5mb of App data on any of the profiles, desktop icons and start menus are all done with redirection. Some profiles have NTUSER.man and NTUSER.dat files in some along with around 6 profiles of various names which dont appear to be in use, could I get away with just deleting all of these profiles or would I see numerous errors

[Firefox]

Our profiles are set in a profile share then in folders for groups, 1 profile per group e.g. \students \staff \tech \admin.

Having managed to get some of each group to log in on a windows 7 machine now and the logon populating a .v2 folder for each some users from all groups are now able to logon but not others!

 

To get what I said above to work effectively the users XP and W7 profiles would need to be in the same share, as obviously AD will only point to 1 location for each user

[bondbill2k2]

To get what I said above to work effectively the users XP and W7 profiles would need to be in the same share, as obviously AD will only point to 1 location for each user

All of our profiles are in the same share area \\server\profiles$

[bondbill2k2]

I havn't had much chance to sort this or play with windows 7 policys even yet, around 80% of our network will still be XP computers anyway, of which many will be renewed next summer hopefully, we also plan to upgrade our server as its outdated to say the least, about 6years old now without any upgrades so ill be downgrading our win7 machines for now and they will be upgraded site wide hopefully early next year on an 08 domain