We have seen cases where no service account is using the id, the user is not
logged in, but the ntuser.dat still show up in use. A reboot of the box
seems to fix this. Seems to be a bug in NT.
Wanda - are you sure that you can fully recover if you don't have a copy of
the ntuser.dat. We did a restore test once where we had been exluding the
ntuser.dat for one of our service accounts (NAV for Exchange). We did have
a full backup of everything else (including the registry). NAV did not
start, and the ntuser.dat files were missing from the profile directories.
When we copied the ntuser.dat from the original box, all worked fine.
Tim Rushforth
City of Winnipeg
-----Original Message-----
From: Prather, Wanda [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 18, 2001 3:29 PM
To: [EMAIL PROTECTED]
Subject: Re: HELP! Logged off, BUT ntuser.dat still "in use by another
pro cess" ???!
Services.
Each service runs under a logon id.
The default for most NT services is to use the SYSTEM id.
But sometimes services are set up with another id, espeically if the serivce
needs network or domain authority to access files. Go into Services, and
look at the PROPERTIES of each. You will see the logon id.
If any of the services runs under the user's id, then the user IS logged on,
and NTUSER.dat will still be in use!
BTW, while the ntuser.dat message is annoying, it isn't really a problem.
The logical contents of the NTUSER.DAT are backed up anyway as part of the
registry backup. You can restore the user customization if you have EITHER
a backup copy of NTUSER.dat, or a good copy of the registry. And you never
need to restore NTUSER.log.
-----Original Message-----
From: Keith Kwiatek [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 18, 2001 7:19 PM
To: [EMAIL PROTECTED]
Subject: HELP! Logged off, BUT ntuser.dat still "in use by another
process" ???!
Hello,
With respect to the ntuser.dat and ntuser.dat.log files, we have noticed
that our clients are getting: "the object is in use by another process"
entries in their log files. BUT they have logged off, and there are no other
users logged into the machine....
Any ideas what else could be locking ntuser.dat and ntuser.dat.log files?
thanks!
Keith
