From: IT Junkie on
I suffered a failure of the only DC in my domain and was forced to
rebulid the server.I've managed to restore from system state backup.
On reboot, I've experienced a few different errors, depending on the
method of restore.

The first error was a 0x0000007b stop error which i eliminated by re-
installing the scsi drivers throught windows setup and repair.

The second is a 0xc0000227 stop error after the previous error is
fixed. I am unable to log into DSRM after this as the stop error
recurs. Is there any way I can recover from this?

Thirdly, a 0xc00002e1 error saying the SAM couldn't initialize.

What is the surest way of a complete successful restore? My current
hardware config consists of a Dell poweredge 6450 & an external
Powervault 220s SAN.

All drives have been configured as before the failure.

Thanks
From: Florian Frommherz [MVP] on
Howdie!

IT Junkie wrote:
> I suffered a failure of the only DC in my domain and was forced to
> rebulid the server.I've managed to restore from system state backup.
> On reboot, I've experienced a few different errors, depending on the
> method of restore.
>
> The first error was a 0x0000007b stop error which i eliminated by re-
> installing the scsi drivers throught windows setup and repair.
>
> The second is a 0xc0000227 stop error after the previous error is
> fixed. I am unable to log into DSRM after this as the stop error
> recurs. Is there any way I can recover from this?
>
> Thirdly, a 0xc00002e1 error saying the SAM couldn't initialize.

Is that the same machine that failed or a different machine? How did you
recover the OS? New installation? I suggest setting up Windows (from
scratch) and then restore the system state/AD.

You'd better build another DC for that domain for just these downtime
purposes.

Cheers,

Florian
--
Microsoft MVP - Group Policy
eMail: prename [at] frickelsoft [dot] net.
blog: http://www.frickelsoft.net/blog.
Maillist (german): http://frickelsoft.net/cms/index.php?page=mailingliste
From: Meinolf Weber [MVP-DS] on
Hello IT,

Did you use the same hardware or different? Please give some more details
about the restore of the server and the additional steps you have done.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> I suffered a failure of the only DC in my domain and was forced to
> rebulid the server.I've managed to restore from system state backup.
> On reboot, I've experienced a few different errors, depending on the
> method of restore.
>
> The first error was a 0x0000007b stop error which i eliminated by re-
> installing the scsi drivers throught windows setup and repair.
>
> The second is a 0xc0000227 stop error after the previous error is
> fixed. I am unable to log into DSRM after this as the stop error
> recurs. Is there any way I can recover from this?
>
> Thirdly, a 0xc00002e1 error saying the SAM couldn't initialize.
>
> What is the surest way of a complete successful restore? My current
> hardware config consists of a Dell poweredge 6450 & an external
> Powervault 220s SAN.
>
> All drives have been configured as before the failure.
>
> Thanks
>


From: IT Junkie on
On Feb 6, 3:54 pm, "Florian Frommherz [MVP]"
<flor...(a)frickelsoft.DELETETHIS.net> wrote:
> Howdie!
>
> IT Junkie wrote:
> > I suffered a failure of the only DC in my domain and was forced to
> > rebulid the server.I've managed to restore from system state backup.
> > On reboot, I've experienced a few different errors, depending on the
> > method of restore.
>
> > The first error was  a 0x0000007b stop error which i eliminated by re-
> > installing the scsi drivers throught windows setup and repair.
>
> > The second is a 0xc0000227 stop error after the previous error is
> > fixed. I am unable to log into DSRM after this as the stop error
> > recurs. Is there any way I can recover from this?
>
> > Thirdly, a 0xc00002e1 error saying the SAM couldn't initialize.
>
> Is that the same machine that failed or a different machine? How did you
> recover the OS? New installation? I suggest setting up Windows (from
> scratch) and then restore the system state/AD.
>
> You'd better build another DC for that domain for just these downtime
> purposes.
>
> Cheers,
>
> Florian
> --
> Microsoft MVP - Group Policy
> eMail: prename [at] frickelsoft [dot] net.
> blog:http://www.frickelsoft.net/blog.
> Maillist (german):http://frickelsoft.net/cms/index.php?page=mailingliste

I'm using same spec, but different hardware. All my restores are from
scratch. And the restores are all system state. I only need to get
this DC operational for a short while as I was about to virtualize
just before the failure. Murphy's Law.

I've referenced this article (http://support.microsoft.com/?
kbid=263532) as a guide but with a different result. When doing the
repair of the existing installation, once I've selected all the
optional components, it installs all of them, but comes to a grinding
halt when installing COM+. Any reason for this?

BTW. By restoring through DSRM, I also end up at the same scenario.
Can I eliminate the boot error by rre-installing the SCSI driver in
DSRM, or will the restore only take effect post-reboot after the
restore?
From: IT Junkie on
On Feb 6, 4:01 pm, Meinolf Weber [MVP-DS] <meiweb(nospam)@gmx.de>
wrote:
> Hello IT,
>
> Did you use the same hardware or different? Please give some more details
> about the restore of the server and the additional steps you have done.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!!http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
>
> > I suffered a failure of the only DC in my domain and was forced to
> > rebulid the server.I've managed to restore from system state backup.
> > On reboot, I've experienced a few different errors, depending on the
> > method of restore.
>
> > The first error was  a 0x0000007b stop error which i eliminated by re-
> > installing the scsi drivers throught windows setup and repair.
>
> > The second is a 0xc0000227 stop error after the previous error is
> > fixed. I am unable to log into DSRM after this as the stop error
> > recurs. Is there any way I can recover from this?
>
> > Thirdly, a 0xc00002e1 error saying the SAM couldn't initialize.
>
> > What is the surest way of a complete successful restore? My current
> > hardware config consists of a Dell poweredge 6450 & an external
> > Powervault 220s SAN.
>
> > All drives have been configured as before the failure.
>
> > Thanks- Hide quoted text -
>
> - Show quoted text -

I'm using same spec, but different hardware. All my restores are from
scratch. And the restores are all system state. I only need to get
this DC operational for a short while as I was about to virtualize
just before the failure. Murphy's Law.

I've referenced this article (http://support.microsoft.com/?
kbid=263532) as a guide but with a different result. When doing the
repair of the existing installation, once I've selected all the
optional components, it installs all of them, but comes to a grinding
halt when installing COM+. Any reason for this?


BTW. By restoring through DSRM, I also end up at the same scenario.
Can I eliminate the boot error by rre-installing the SCSI driver in
DSRM, or will the restore only take effect post-reboot after the
restore?