Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.
One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.
Accounts not shown in USRMGR ?
I run a standalone NT Server 4.0 SP3.
Suddenly ALL accounts are no longer visible within the GUI in USRMGR.
I can still create new accounts, but afterwards they don't show up in the GUI.
I still see all the groups, and I can add/remove accounts to them.
Note that since that point "Adduser /d" is looping. "Net Users" doesn't show accounts anymore.
The system still works fine. The only thing is I can't look at and manage existing accounts !
I've also checked their existence and security within registry. But there is no difference to another
system of mine which has no problems with USRMGR.
Any help is welcome.
Thanks in advance
Jürgen
Suddenly ALL accounts are no longer visible within the GUI in USRMGR.
I can still create new accounts, but afterwards they don't show up in the GUI.
I still see all the groups, and I can add/remove accounts to them.
Note that since that point "Adduser /d" is looping. "Net Users" doesn't show accounts anymore.
The system still works fine. The only thing is I can't look at and manage existing accounts !
I've also checked their existence and security within registry. But there is no difference to another
system of mine which has no problems with USRMGR.
Any help is welcome.
Thanks in advance
Jürgen
Asked:
-
6
-
2
-
2
- +2
1 Solution
If you have emergency repair disk which you prepared before coming this problem. . You can try to repair user database with the help of ERD.If you are having erd you can try this...
I enabled auditing (success/failure on 'use of rights' and 'user/group mgmt') .. but there
is nothing usefull in the eventlog.
I also used REGMON: I see that usrmgr/lsass are scanning the registry (for all accounts) and all the reads are successfull, but no account data is displayed. The funny thing is
that account related dialogs within USRMGR (i.e add/remove from group, add/remove
user rights) work fine i.e they display all the users
is nothing usefull in the eventlog.
I also used REGMON: I see that usrmgr/lsass are scanning the registry (for all accounts) and all the reads are successfull, but no account data is displayed. The funny thing is
that account related dialogs within USRMGR (i.e add/remove from group, add/remove
user rights) work fine i.e they display all the users
I don't have an uptodate repair disk.
Well, it's not an important or a production system, therefore I can easily reinstall and recreate the accounts.
But I wan't to find out what's wrong. A system only does what it has been told to, unless
something is really corrupt.
Well, it's not an important or a production system, therefore I can easily reinstall and recreate the accounts.
But I wan't to find out what's wrong. A system only does what it has been told to, unless
something is really corrupt.
Since other apps are showing users correctly, I would go for the following:
- run chkdsk on your system partition and see if this turns up anything
- check all usrmgr files against the original NT cd and/or SP3 installation. Any changes there?
This is indeed a very strange problem.. I would love to know what has gone wrong here too.. ;-)
- run chkdsk on your system partition and see if this turns up anything
- check all usrmgr files against the original NT cd and/or SP3 installation. Any changes there?
This is indeed a very strange problem.. I would love to know what has gone wrong here too.. ;-)
Chkdsk runs without complaining about anything.
I connected via another machines USRMGR to this very node... same effect.. no accounts
I connected via another machines USRMGR to this very node... same effect.. no accounts
I believe the sam is corrupted and can only be fixed by with repair disk or by running winnt32.exe and selecting repair, there are default repair files on the harddrive and it can be put back to normal with them. This is only a begining problem and I believe it would get worse over time.
I found a solution, but I don't really know why this happened. I focused on the
looping "addusers /d" and monitored it with regmon and found out that it was reading
the same keys over and over again.I went into REGEDIT and found that HKLM\sam\sam\domains\accou
key named 000003EB. The same key was found in sam\sam\domains\account\us
along with some others. But the contents of the 'others' looked a little bit different
and therefore i simply did a cut&paste of the contents of the key !
Guess what ! It was a good try. The accounts are back. visible. manageable ...
Thanks for all your hints.
looping "addusers /d" and monitored it with regmon and found out that it was reading
the same keys over and over again.I went into REGEDIT and found that HKLM\sam\sam\domains\accou
key named 000003EB. The same key was found in sam\sam\domains\account\us
along with some others. But the contents of the 'others' looked a little bit different
and therefore i simply did a cut&paste of the contents of the key !
Guess what ! It was a good try. The accounts are back. visible. manageable ...
Thanks for all your hints.
I'm posting the solution found by jkrautner so it can be saved in the PAQ.
Linda Gardner
Customer Service @ Experts Exchange
Solution:
I focused on the
looping "addusers /d" and monitored it with regmon and found out that it was
reading
the same keys over and over again.I went into REGEDIT and found that
HKLM\sam\sam\domains\accou
key named 000003EB. The same key was found in
sam\sam\domains\account\us
along with some others. But the contents of the 'others' looked a little bit
different
and therefore i simply did a cut&paste of the contents of the key !
Guess what ! It was a good try. The accounts are back. visible. manageable
...
Linda Gardner
Customer Service @ Experts Exchange
Solution:
I focused on the
looping "addusers /d" and monitored it with regmon and found out that it was
reading
the same keys over and over again.I went into REGEDIT and found that
HKLM\sam\sam\domains\accou
key named 000003EB. The same key was found in
sam\sam\domains\account\us
along with some others. But the contents of the 'others' looked a little bit
different
and therefore i simply did a cut&paste of the contents of the key !
Guess what ! It was a good try. The accounts are back. visible. manageable
...
I suggested you to try erd(emergency repair disk) I think It would have done the same thing automatically which you have done manually. Please tell me you really tried with ERD.
Thanking You
Surinder Chugh
Thanking You
Surinder Chugh
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.
One of a set of tools we're offering as a way to say thank you for being a part of the community.
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
(available on any BDC or the PDC of your domain in the %systemroot%\system32 directory.)