7 replies
by darkstar
Here are some possibilities to investigate. When this happens, does the system event log indicate an Error 1000? If so, the error log detail will indicate the general reason for the failure. Also, does the server copy of profile become corrupted? Orjust doesn't load right at user workstation?
Some possibilities: the registry size limit has been reached and the profile data cannot be loaded; not enough room on the system partition to create a temporary local copy of ntuser.dat or profile directory.
by ahomoly
by darkstar
Are you looking at the registry size and drive space availability on the workstations? I have seen cases where the roaming profile did not load up properly on the workstation. Unfortunately, the corrupted local copy was then written back to the server when user logged out. Shouldn't happen, but sometimes...
Also, any evidence of other file transfer corruption on the server? I saw something similar in a NW system last year. Was a bad NIC in the server. Good luck tracking this down.
by ahomoly
by robbinsr
by ahomoly
by ahomoly
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending