Multiple problems with Win2003 SP2

This SP seems to have quite a few problems. Have uncovered the following in
the first couple of hours of testing in our test environment:

1. Have successfully installed the SP via WSUS onto two 32-bit member
servers servers running Win2003 R2, but on a further two 32-bit member
servers, the install terminates part way through with a message saying
"Internal error" and no further information. On these servers
WindowsUpdate.log shows

2007-03-14 11:54:56 3364 be0 Handler : Updates to install = 1
2007-03-14 11:54:56 3364 be0 Handler : Installing update
{495DB630-5377-4690-8CCA-12E0AB5F5DD3}.104
2007-03-14 11:54:56 3364 1d4 Handler Installing with parameters=-q -z -er,
sandbox=C:\WINDOWS\SoftwareDistribution\Download\1e96bc398bff37614d7af6bcf809edf5.
2007-03-14 11:54:58 1140 ee8 AU AU setting client response for sessionId 0x1
to 'Active'
2007-03-14 11:58:14 3364 1d4 Handler Install completed with 0x87ff054f.
2007-03-14 11:58:14 3364 be0 Handler FATAL: UH: 0x87ff054f:
InstallOrUninstallThread failed
2007-03-14 11:58:14 3364 be0 Handler : WARNING: Install completed: result
type = 0x0, installer error = True, error = 0x87ff054f, disabled until
reboot = No, reboot required = No
2007-03-14 11:58:14 3364 be0 Handler FATAL: UH: 0x8024200b:
HandleSingleUpdate failed
2007-03-14 11:58:14 3364 be0 Handler :::::::::
2007-03-14 11:58:14 3364 be0 Handler :: END :: Handler: Windows Patch
Install
2007-03-14 11:58:14 3364 be0 Handler :::::::::::::
2007-03-14 11:58:14 1140 da4 AU >>## RESUMED ## AU: Installing update
[UpdateId = {9452503C-05BE-4A64-99ED-9A59F7D65398}]
2007-03-14 11:58:14 1140 da4 AU # WARNING: Install failed, error =
0x87FF054F
2007-03-14 11:58:14 1140 5b4 Agent *********
2007-03-14 11:58:14 1140 5b4 Agent ** END ** Agent: Installing updates
[CallerId = AutomaticUpdates]
2007-03-14 11:58:14 1140 5b4 Agent *************
2007-03-14 11:58:14 1140 5b4 AU # Install call complete for all calls,
reboot required = No
2007-03-14 11:58:14 1140 5b4 AU #########
2007-03-14 11:58:14 1140 5b4 AU ## END ## AU: Installing updates [CallId
= {7454A8F3-FDF2-4332-AC77-FE13918B876D}]
2007-03-14 11:58:14 1140 5b4 AU #############
2007-03-14 11:58:19 1140 49c Report REPORT EVENT:
{82C14C32-F401-458C-B186-6DC9403E6887} 2007-03-14 11:58:14+1100 1 182 101
{9452503C-05BE-4A64-99ED-9A59F7D65398} 104 87ff054f AutomaticUpdates Failure
Content Install Installation Failure: Windows failed to install the
following update with error 0x87ff054f: Windows Server 2003 Service Pack 2
(32-bit x86).

I also tried installing the SP again on one of these servers after a reboot
by going to the i386\update directory for the SP under
c:\windows\sotwaredistribution\download and running update.exe manually, but
it failed again with a message about an internal error, and the system event
log has an error event from NTServicePack saying "Windows Server 2003
Service Pack 2 installation failed. An internal error occurred."

2. Installation via WSUS onto two Win2003 R2 x64 member servers succeeded,
but installation to an x64 R2 domain controller popped up a msgbox saying
that I had needed to be logged in as an administrator, and at this point the
install was stopped part way through. At the time I was logged in as the
actual domain administrator, so there was no valid reason for this msgbox. I
answered the msgbox and then hit Cancel in the partly completed progress
dialog for the SP. A while later I got a message saying that the update had
succeeded(???), and after a reboot, the server shows itself as being at SP2
level!! (5.2 R2 Build 3790.srv03_sp2_rtm.070216-1710 : service pack 2). WTF?

3. I integrated the 32-bit SP into a flat 32-bit Win2003 R2 Standard RIS
image using update.exe /integrate:PathToRISImage. This reported as having
succeeded, but when I tried a server build from the updated image, it copied
the all Windows image files down to the server ok, but gave an error message
when attempting to start Windows on the reboot "Windows could not start
because of an error in the software. Please report this problem as: load
needed DLLs for HAL". This RIS image worked fine before the SP was
integrated into it.

4. I also tried integrating the x64 SP into a flat x64 Win2003 R2 Standard
RIS image using the same update.exe /integrate command, but it failed with a
message saying that the SP could not be integrated into an image that
already had an SP integrated into it. As this image had been created
directly from R2 CDs that were downloaded from Microsoft volume licensing
and had never had any service packs integrated into them, I found this a bit
strange.

Nick Payne



.

Relevant Pages

  • RE: Help! Startup automatically reboots halfway through
    ... Insert the Windows XP startup disk into the floppy disk drive, ... If this does not fix your issue I suggest that you do a parallel install ... rename the system folder to something besides windows or winnt. ... Once you are done you can try and reboot ...
    (microsoft.public.win2000.setup_deployment)
  • RE: Help!SOS!Hardest Senario-Cant start up!-computer reboots halfway through setup
    ... Insert the Windows XP startup disk into the floppy disk drive, ... If this does not fix your issue I suggest that you do a parallel install ... rename the system folder to something besides windows or winnt. ... Once you are done you can try and reboot ...
    (microsoft.public.win2000.setup)
  • Re: Since installing AD, server reboots every 2-3 days
    ... Windows Debugging Tools and take a look. ... what is causing the reboot. ... sense that the Repair install would have fixed the problem. ... Blue screens? ...
    (microsoft.public.win2000.active_directory)
  • Re: SP2 what a bunch of @#$!!!
    ... I installed SP 2 but lost network connectivity as a result, ... so i forced a hardware reboot. ... My last resort was a repair re-install of windows SP-1 from the original CD. ... end of the install after it had written a lot of stuff to the disk. ...
    (microsoft.public.vstudio.development)
  • Re: install SBS2003 Trial - Update, reboot = "Expired"
    ... I tarted install on 7/23 and after windowsupdate date was 5/23. ... I got the error message only after updating. ... did so and then after a reboot I got to a login screen - saw the To do list and I shutdown and rebooted twice - just to see if all was OK with that error message. ... Debugging Tools for Windows - Overview ...
    (microsoft.public.windows.server.sbs)