I created a Windows Domain account that works on MYDOMAIN. All computers attached to MYDOMAIN can use the credentials I have created for log on except for one.
On PROBLEMSERVER01 when I try to log in with MYDOMAIN \ myuser I get the following error (other accounts previously created are working):
User Profile Service service failed the sign-in.
User Profile cannot be loaded.
OK
When I log on to the server and check C:\Users I do not see a folder associated with the account I created. When I check each registry's S-1-5 folders under the the ProfileImagePath entry there is no entry for my user. http://support.microsoft.com/kb/947215
If I try to create the account locally on the machine it appears to work upon creation (no errors there), but if I try to log in I get the same message and no entries are added to the registry.
User Profile Service service failed the sign-in.
User Profile cannot be loaded.
OK
Event log data after trying to sign in:
User Logoff Notification for Customer Experience Improvement Program
User Logon Notification for Customer Experience Improvement Program
The Windows Error Reporting Service service entered the stopped state
The Windows Error Reporting Service service entered the running state
A LDAP connection with domain controller DC01.MYDOMAIN.localhost for
domain MYDOMAIN is established
I have also tried copying the C:\Users\Default folder from a known good server to this one with no change in results.
Best Answer
If you are using Server 2012 R2 with April 2014 update (KB2919355) and also seeing Event ID 1500 in Application log ("Windows cannot log you on because your profile cannot be loaded. Check that you are connected to the network, and that your network is functioning correctly.") as well as Event ID 1509 ("Windows cannot copy file \?\UNC\contoso.com\Users\Profiles\User1.V4\AppData\Roaming\ApplicationName\Program Settings\0000.ex to location \?\C:\Users\User1\AppData\Roaming\ApplicationName\Program Settings\0000.ex. This error may be caused by network problems or insufficient security rights.") then it is known issue with available coldfix from Microsoft:
https://support.microsoft.com/en-us/kb/2985344