Re: Windows 2003 SP1

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

same thing happened here with a dell 1750 the 2650 upgraded fine but the
1750 gives the0x51 error. and recovery console will not accept the admin
password. hope someone finds an answer soon.
"JMC421" <JMC421@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A809D29B-1CE2-4537-A6C5-D421B474F557@xxxxxxxxxxxxxxxx
>I have the exact same problem. I updated several Dell 2650's / 6650's and
> 1750's (all running w2K3 but NOT domain controllers). When I updated one
> of
> the Dell 1750 that was a domain controller, it blue screened on reboot
> with
> the 0x0000051 error code also. When I tried to repair W2K3, it also did
> not
> prompt for repair and put the new install on the "D:" drive.
> When I did the DCPROMO to install AD, I put AD on the "D:" since it had
> more space. Prior to the SP1 upgrade, I had the Dell 1750 at the latest
> level of BIOS / Firmware / etc. W2K3 was also at the latest patch level.
>
>
> "Kerry Brown" wrote:
>
>> "RobertM" <RobertM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:E1E4D51F-B187-4712-BEB9-E924BB4353FC@xxxxxxxxxxxxxxxx
>> > 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.
>>
>> The moral really is: deploy major changes in stages. Why would you
>> upgrade
>> four servers at different geographic sites at the same time? It would
>> make a
>> lot more sense to deploy SP1 on one server. Wait until you are sure that
>> site is OK (possibly a week or two) then do each of the others in turn.
>> 0x51
>> can also indicate hardware incompatibility, low disk space, or file
>> corruption. Do all the servers have the same hardware?
>>
>> Kerry
>>
>>
>>


.

Relevant Pages

  • Re: Windows 2003 SP1
    ... Prior to the SP1 upgrade, I had the Dell 1750 at the latest ... >> We have 4 Dell servers in a single domain acting as DCs ... >> Installation completed successfully but on reboot the registry was ... >> with a STOP message and Registry_Error and error code 0x00000051. ...
    (microsoft.public.windows.server.general)
  • Errors after Upgrading to SP1 for Server 2003
    ... After Approving the updates in SUS for Both Nodes i decided to reboot one of ... reboot the Active cluster just to confirm the update was at fault only to ... where i removed Sp1 the MSDTC service failed to start So i had to forcefully ... Both Servers are Domain Controllers / File Servers Application Servers (DNS, ...
    (microsoft.public.windows.server.security)
  • Re: QFE for Exchange SP1 Compatability is now available
    ... Chad A. Gross - SBS MVP ... >>> installed both SP1 and then the QFE on my SBS2003 servers. ... >>> Although neither required a reboot, ...
    (microsoft.public.windows.server.sbs)
  • Re: QFE for Exchange SP1 Compatability is now available
    ... I've gone ahead and installed both SP1 ... > and then the QFE on my SBS2003 servers. ... > Although neither required a reboot, following my usual modus operandi, I ...
    (microsoft.public.windows.server.sbs)
  • Re: SP1 risk/reward
    ... Why is this thread titled SP1 risk/reward? ... Those of us having NON DELL ... Some of us had SP1 break production servers and are reading ... > Have you been in contact with Dell about OpenManage? ...
    (microsoft.public.windows.server.sbs)