Discussion Locked

Roaming User Profile won't copy to serve

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Let me give a brief history. We have a 100% win2k network. We had Domain A and Domain B. A few months ago, we changed all user/computer accounts to Domain A. The domain membership change went as smooth as clockwork. Recently, we bought a new server and I have installed it as a DC in the site that used to be Domain B. THe Site settings are working great. All users at this site are using the correct DC for authentication. Everything looks fine. That is until,I setup RUP's. Most Users profiles are working very nicely, but there are about 10-15 that will not copy to the new server. It is NOT a permissions issue. I can make them temp Domain Admins and I still get an Event ID 1000 error. I can create a profile directory on any otherDC (across the WAN) and their profiles copy just fine. I have never seen anything like this. Simple logic seems of no use here?!? I simply cannot get some profiles to copy locally onto the new DC. Most are fine. Please help! Could this be somesort of SID problem? I did delete one of the users profile and re-create it and this method seemed to have helped. BUT I would like a simpler method if anyone has experienced this problem. All help appreciated.

5 replies

by d.walker5

I've had Event ID 1000 occur when an application calls a missing or corrupt dll. I have have Winword.exe and explorer.exe cause this error. However, in your case see MS Knowledge Base Article 248368.

by nettek

I can find 15 distinct error messages associated with profiles and Event ID 1000. Since you do not say what the event description is, these are the following solutions I have been able to find:
1. This is a known problem with Win2K that was corrected with SP2.
2. The EVERYONE group needs Change permissions on c:\profiles to load the profile. You also need at least Read on the system root and drive root.
3. If the system partition is low on space, the profile can fail to load.
4. If the registry size limit has been exceeded, the profile can fail to load.
5. The roaming copy of Ntuser.dat is corrupted. When this occurs, there is usually an event indicating a RegLoadKey failure.
6. The c:\Profiles\Default User folder is missing and the account does NOT have a cached local profile and is NOT configured for a roaming profile.

Perhaps you will get more exact answers if you post the event description. Good luck.

This discussion is closed to new replies.