Win2k setup resume problem

[Guest]

Help. If anyone knows how to stop W2k-AS setup from trying to resume after a
failed re-install, please, please let me know.

After trying to remove a mangled Exchange 2k from my W2k-Adv-Srv Dom
Controller on a small test network, the directory service went haywire. As
it's only a test server and subject to frequent changes, it doesn't get
backed up & the ERD rarely gets updated. Unfortunately, it's current s/w
configuration needs preserving so I thought I could fix things by doing an
in-place repair upgrade to W2k.

I boot from CDROM and select manual repair with no ERD on c:\winnt and
everything goes OK until the system reboots. At this point it bombs out with
a lsass.exe system error because the SAM initialisation failed due to the
directory service failing to start. (error status: 0xc00002e1) and tells me
to reboot into Dir Srvc repair mode to fix things.

I reboot into DSR mode, it comes up into safe mode, checks all the disks are
OK.... and then tries to resume setup !! It prompts for a series of .CAT
files, most of which are in unexpanded form on the CDROM, before coming up
with the same lsass.exe system error message. And then we're back to the
start again. It doesn't matter what I try, safe modes or not, the same thing
happens. Can't go backwards, can't go forwards - GOTCHA ;-)

What I can do though is a parallel installation onto a spare partition. 10
minutes later and, hey, I'm back in control again. Only thing is, I don't
know how to stop the original installation from trying to resume setup again.
If I could do that then maybe, just maybe, I could get to work on the
Directory.

I've scanned Robert Oppegaard's excellent webcast transcript "Recovering
from Microsoft Windows 2000 Server Start Problems" but whilst I would
recommend this article to everyone, it didn't contain the key to my prison
door.

Like the man said, it's driving me knucking futs /:-|


tia stefan thatcher

 

[Guest]

Hi

just check this article http://support.microsoft.com/?id=830574. you might
need to call MS support to get the hotfix to resolve the issue. And if the
computer is not booting you can copy the files after extracting the hotfix to
the required location using recovery console.

 

[Guest]

Thanks, but this article refers to w2k3, I'm running w2k. It did send me
towards 258062 though, which looks as though it will help with the directory
problem, but I will need to get into DSR mode to do anything. Can't get
there 'cos setup keeps trying to resume - so it's back to square one again.
}:-(

Stefan

 

[Guest]

It may or may not work but what you can do is load the registry hives
(primarily he system hive) of the crashed operating system in the parallel
install and in that there must be a key which is starting the setup while
booting. If we can identify that key we can stop the setup from resuming
again. I am trying to do this in my lab or you can search too on this if
possible.

 

[Guest]

Found the key, it's in HK-LM ->SYSTEM ->SETUP -> SYSTEMSETUPINPROGRESS.

Couldn't decode the crashed one but it's certainly different from that of
the parallel system. That one shows value 0 in regedt so I guess a non-zero
value ( 1 ?) will resume setup.

Whilst I was searching the posts, what I did find was a reference to the
registry REPAIR folder which I couldn't remember. When I looked in it I
found a reg backup I'd done about a month ago and forgotten about. I renamed
the faulty reg files, copied the backups over, rebooted and up she came :^)

I've still got the lsass system error from the directory, but I'm into DSR
mode now so I can get to work on it.

Thanks very much for your help.

Stefan