JSI Tip 0547 - Common causes of profile error - Event ID: 1000 - Source: Userenv.

Jerold Schulman

May 26, 1998

3 Min Read
ITPro Today logo in a gray background | ITPro Today


If you receive an error concerning the loading of your profile and Event ID 1000 - Source: Userenv appears in the Application Event Log, chances are:

1. You changed Permissions on the local %system root%Profiles folder. The EVERYONE group needs Change permissions to load the profile. You also need at least Read on the system root and drive root.

2. If the system partition is low on space, or the registry size limit has been exceeded, the profile can fail to load.

3. The profile is corrupted. Either the local Ntuser.dat, Ntuser.man or the roaming copy of Ntuser.dat is corrupted. When this occurs, there is usually an event indicating a RegLoadKey failure.

4. The %system root%ProfilesDefault User folder is missing and the account does NOT have a cached local profile and is NOT configured for a roaming profile.

When you look at the Application Event Log, Event ID 1000 will have one of the following details where %s is the UserName and %d is the system error:

 - The operating system was unable to load your profile. Please contact your Network Administrator. (%d) - You do not have permission to access your central profile located at %s. The operating system is attempting to log you on with your local profile. Please contact your Network Administrator. - The operating system was unable to create a profile directory %s. Another file exists with the same name. You will be logged on with a local profile only. Please contact your Network Administrator. - The operating system was unable to create profile directory %s. You will be logged on with a local profile only. Please contact your Network Administrator. (%d) - Your roaming profile is not available. You will be logged on with the locally stored profile. (%d) - The operating system was unable to create a temporary profile directory %s. Please contact your Network Administrator. (%d) - The operating system was unable to load the locally stored profile. A new local profile will be created. (%d) - The operating system was unable to set security on your registry. Please contact your Network Administrator. (%d) - The update of your roaming profile failed. Please contact your Network Administrator. (%d) - Your profile was not successfully loaded, but you have been logged on with the default system profile. Please correct the problem and log off. (%d) - Your roaming profile is not available, the operating system is attempting to log you on with your local profile. (%d) - Your roaming mandatory profile is not available, the operating system is attempting to log you on with your local profile. (%d) - The operating system is unable to log you on because your roaming mandatory profile is not available. Please contact your Network Administrator. (%d) - This computer is in manual policy mode, but the policy file can not be found. You will be logged on without policy. (%d) - RegLoadKey failed with error %d for %s  


Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.

You May Also Like