RE: Windows 2003 SP1
- From: LThibx <lthibx@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 28 Apr 2005 07:46:06 -0700
I thought I would share my solution to this problem.
I too received the 0x51 error after applying W2k3 SP1 to a newly setup Dell
PowerEdge 2850 server.
Dell does have a fix for this, If you have already installed SP1 and are
receiving the 0x51 error. The link is:
http://support.dell.com/support/topics/global.aspx/support/kb/en/document?dn=1092326&c=us&l=en&s=gen&cs=
Also, there is a patch that can be installed prior to installing SP1 to
prevent this situation. (My situation was post SP1 installation, so I cannot
verify this solution). The link is:
http://support.dell.com/support/downloads/format.aspx?releaseid=R98878&c=us&l=en&s=gen&cs=
Alternately, you can go to support.dell.com and search Technical Support for
'regfix' or 'regprep'.
I hope this information is useful in solving your issue.
Disclaimer
Provided for informational purposes only. No guarantee is made that this
information directly applies or will resolve your issue.
--
LThibx
"RobertM" wrote:
> Have contacted Dell re this problem and they are now advising all users not
> to install SP1 until at least JUNE until they have sorted out what the
> problem is.
> I 'm just glad that the two servers in my main site upgraded Ok, otherwise I
> would be well in the pooh.
> Apparently the regprep.iso is just a workaround for the moment.
>
> My other two 1750s are in smaller sites so was not such a problem, but
> enough to give me palpitations !!
> Thanks for all the posts.
>
> "JMC421" wrote:
>
> > I sent a support e-mail to Dell last night and they called me this morning.
> >
> > They have a fix. You download a CD image and boot with the CD created from
> > the image. It loads Win XP Pro and runs a program to modify the regisrty.
> > After the program runs, the server reboots. As the server reboots, remove
> > the CD and you are back in - no hassle (other than having to run the CD). I
> > shut the DC down serveral times and each time it came back up like it did
> > originally.
> >
> > I ran the fix on one DC this morning and will try the CD on a second DC
> > tomorrow.
> >
> > Dell indicated they started getting calls yesterday (4/5) and that they and
> > Microsoft were working on the problem. The tech said it was to early to say
> > if other vendors had the same problem or if Dell models other than the 1750
> > were impacted.
> >
> > I did apply SP1 to a Dell 1750 successfully, but it was not a domain
> > controller.
> >
> > "RobertM" wrote:
> >
> > > This post maybe helpful to others re. SP1
> > > We have 4 Dell servers in a single domain acting as DCs
> > > We updated two of the DCs to SP1 without a problem.
> > > The other two got trashed when we installed SP1.
> > > Installation completed successfully but on reboot the registry was corrupted
> > > with a STOP message and Registry_Error and error code 0x00000051.
> > > Reboot in Safe mode and last known good config gave same result.
> > > Both DCs are in different geographic sites on different subnets but the
> > > error was the same in both cases.
> > > This neccessitated a complete reinstall of Windows 2003 server.
> > > Then had to seize the FMSO roles, remove DC objects from AD using NTDSUTILS
> > > and run metadata cleanup, before recreating the DCs.(DCPROMO)
> > >
> > > I certainly did'nt want to spend all of last night and early morning doing
> > > this, so thanks alot Bill.
> > > Any MS pros out there who can throw some light on this?
> > >
> > > Moral - really check SP1 out and watch it like a hawk.
.
- References:
- Windows 2003 SP1
- From: RobertM
- RE: Windows 2003 SP1
- From: JMC421
- RE: Windows 2003 SP1
- From: RobertM
- Windows 2003 SP1
- Prev by Date: Re: Cannot access Previous versions from Win2K
- Next by Date: Solution for W2k3 SP1 0x00000051 error on Dell PowerEdge Server
- Previous by thread: RE: Windows 2003 SP1
- Next by thread: Problems with underscores in Computer Name for Server 2000
- Index(es):
Relevant Pages
|
Loading
