5 replies
According to Microsoft article Q185198 titled, "Error 1000 and User Profiles", The problem has several common causes. The following are the most relevant causal scenarios.
Permissions on the local %system root%\Profiles have been modified. TheEVERYONE group needs Full Control to load the profile.
Lack of resources. If the system partition is low on space, or the registry size limit has been exceeded, the profile can fail to load.
The profile is corrupted. Either the local Ntuser.dat (or .man) or the roaming copy of Ntuser.dat is corrupted. When this occurs, there is usually an event indicating a RegLoadKey failure.
See this link for the appropriate resolution and further explanarion:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q185198
(REMOVE SPACES from the pasted URL.)
Maxwell
by gigelul
I assume that this is a standalone server and also you have a domain controller. I think that you must reestablish the trust relationship with your domain. For that remove from Server manager the ComputerName from list. Log on local with local admin rights and in network properties set as member of workgroup. Reboot computer. Log on again as local admin and set as member of domain and enable the option . Give the information about name and password of the Domain Admin. Reboot computer and check shares and permissions.
If I don?t understand correct your problem post a comment.
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending