Re: Locally Stored Profile

From: Tom Penharston (thinkpersuasion_at_netscape.net)
Date: 02/03/05


Date: 3 Feb 2005 13:14:53 -0800

Yes, this is exactly what I need to do. Thank you. Here are the most
recent userenv entries from a healthy login where no problems are
visable to the user, yet some errors are still shown:

USERENV(33c.340) 15:18:20:000 MyRegUnLoadKey: Failed to unmount hive
00000005
USERENV(33c.340) 15:18:20:015 DumpOpenRegistryHandle: 2 user registry
Handles leaked from
\Registry\User\S-1-5-21-1078081533-113007714-725345543-1008
USERENV(33c.340) 15:18:20:015 UnloadUserProfileP: Didn't unload user
profile <err = 5>
USERENV(33c.340) 15:18:20:765 UnloadUserProfile: UnloadUserProfileP
failed with 0
USERENV(33c.340) 15:19:10:750 CUserProfile::CleanupUserProfile: Ref
Count is not 0
USERENV(33c.340) 15:19:10:750 CUserProfile::CleanupUserProfile: Ref
Count is not 0
USERENV(33c.340) 15:19:10:750 CUserProfile::CleanupUserProfile: Ref
Count is not 0
USERENV(368.36c) 15:19:20:203 UnloadUserProfile: received a NULL
hProfile.

This computer has only local user profiles and is only on a workgroup.
The computer was previously joined to a domain but removed until
userenv problems can be debugged. I think I first need to understand
the errors that occur during a healthy (somewhat healthy) login, as
reported above. A hive is a piece of the registry stored in its own
file, but why does hive fail to unmount? How are user registry handles
"leaked"?

-Tom