Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Profile Issue

Status
Not open for further replies.

Kiwica

IS-IT--Management
Feb 26, 2003
102
US
W2KSP4 running on a domain, using local profiles.
The user is trying to log in and is getting a log user enviroment message,that says in part " Windows cannot copy file c:\documents and settings\default user\local setting\application data\PCHealth\Error Rep\Q signoff\ to location c:\documents and settings\xxxuser\local setting\application data\PCHealth\Error Rep\Q signoff - contact network admin

this message stays for about 30 secs and then is replaced by another error message: Windows cannot log you on because the profile cannot be loaded.

Anybody have any ideas why this has suddently occurred today. There have been no recent updates applied.

"Have you ever imagined a world with no hypothetical situations?
 
It sounds like there's some corruption happened. If its trying to copy from Default User profile, that suggests its creating a new profile, rather than loading existing - which suggests existing is corrupt.

Might be worth running chkdsk. Also, try logging on as another (admin) user and then rename the profile for the problem user. Log back on as problem user - see if it creates new profile correctly. If it does, log back on as admin user and copy the relevant bits (my documents, favourites, email , start menu etc from the old [profile to the new and just carry on with the new).

describes this for XP - 2k much the same.
 
Thanks for the suggestion Wolluf, the profile isnt corrupt, I checked the default profiles of other machines and none of them had PCHealth\Error Rep\Q signoff\ under the local settings in their paths. I made a copy of the users profile and then deleted the above path from the default profile and it started working fine. I need to look into this PCHealth sub folder that was created, perhaps it was something to do with an internal diag programme that detected and issue and was trying to write the log file some where it couldnt.



"Have you ever imagined a world with no hypothetical situations?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top