Re: Windows Server 2003 SP1 install failure
- From: Darrellg@xxxxxxxxxxxxxxxxxxxx ("Darrell Gorter[MSFT]")
- Date: Wed, 19 Jul 2006 01:02:30 GMT
Hello Tim,
Hmm, I would look at the svcpack.log file for the service pack failures.
I don't recall service pack information being logged to the setuplog.txt
file.
Thanks,
Darrell Gorter[MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
<Thread-Topic: Windows Server 2003 SP1 install failure
<thread-index: AcaqjN3UNDzcVGj5QtyE4JuAr62RUw==
<X-WBNR-Posting-Host: 12.182.116.222
<From: =?Utf-8?B?VGltIEJhbGRlcnN0b24=?=
<TimBalderston@xxxxxxxxxxxxxxxxxxxxxxxxx>
<References: <2A7DF8FE-EAEA-4ED5-B495-B9E026BEB272@xxxxxxxxxxxxx>
<Odc0OelqGHA.5108@xxxxxxxxxxxxxxxxxxxx>
<FDA3020B-84A8-4690-891F-294269CF4677@xxxxxxxxxxxxx>
<Subject: Re: Windows Server 2003 SP1 install failure
<Date: Tue, 18 Jul 2006 10:09:02 -0700
<Lines: 189
<Message-ID: <B2A202D4-9E98-40DC-89B4-A81796656208@xxxxxxxxxxxxx>
<MIME-Version: 1.0
<Content-Type: text/plain;
< charset="Utf-8"
<Content-Transfer-Encoding: 7bit
<X-Newsreader: Microsoft CDO for Windows 2000
<Content-Class: urn:content-classes:message
<Importance: normal
<Priority: normal
<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
<Newsgroups: microsoft.public.windows.server.general
<Path: TK2MSFTNGXA01.phx.gbl
<Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.general:100457
<NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
<X-Tomcat-NG: microsoft.public.windows.server.general
<
<I located the setuplog.txt file under the Windows directory. Here are the
<bottom lines within the file:
<Part of the process:
<07/17/2006
<13:12:45,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,4218,BEGIN_SECTION,Ge
nerating security templates
<07/17/2006
<13:12:47,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,4220,END_SECTION,Gene
rating security templates
<07/17/2006 13:12:47,d:\srv03rtm\base\ntsetup\syssetup\copy.c,644,,SETUP:
<Marked file perfmon.msc read-only
<07/17/2006
<13:12:47,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,5938,END_SECTION,Conf
iguring Common
<07/17/2006
<13:12:47,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,6037,BEGIN_SECTION,Fi
x
<the security on <All Users\Application Data\Microsoft\Windows NT>
<07/17/2006 13:12:47,d:\srv03rtm\base\ntsetup\syssetup\log.c,315,,Setup
<invoked the external program shmgrate.exe Fix-HTML-Help.
<
<07/17/2006
<13:12:47,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,6039,END_SECTION,Fix
<the security on <All Users\Application Data\Microsoft\Windows NT>
<07/17/2006
<13:12:47,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,6044,BEGIN_SECTION,Mi
grating exception packages
<07/17/2006
<13:12:47,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,6046,END_SECTION,Migr
ating exception packages
<07/17/2006
<13:12:47,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,6062,BEGIN_SECTION,Ru
nning SFC
<
<Then this section began:
<
<07/17/2006 13:12:54,d:\srv03rtm\base\ntsetup\syssetup\log.c,315,,Setup
<detected that the system file named [c:\windows\system32\ole32.dll] is not
<signed properly
<by Microsoft. This file has been restored to the correct Microsoft
version
<to maintain system stability.
<.
<.(Repeated for additional files...)
<.
<
<Then this section occurred next:
<
<07/17/2006
<13:14:16,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,6064,END_SECTION,Runn
ing SFC
<07/17/2006
<13:14:16,d:\srv03rtm\base\ntsetup\syssetup\registry.c,1578,BEGIN_SECTION,De
leteCurrentProductIdInRegistry
<07/17/2006
<13:14:16,d:\srv03rtm\base\ntsetup\syssetup\registry.c,1591,END_SECTION,Dele
teCurrentProductIdInRegistry
<07/17/2006
<13:14:16,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,6189,BEGIN_SECTION,Sa
ving repair info
<07/17/2006
<13:14:32,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,6191,END_SECTION,Savi
ng
<repair info
<07/17/2006
<13:14:32,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,6200,BEGIN_SECTION,Re
moving Temporary Files
<07/17/2006 13:14:32,d:\srv03rtm\base\ntsetup\syssetup\utils.cpp,18,,Setup:
<Activationrequired
<07/17/2006
<13:14:32,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,4894,,Setup:
<(Information) activation icons removed
<
<07/17/2006 13:14:33,d:\srv03rtm\base\ntsetup\syssetup\log.c,315,,DUInfo:
<DuInstallUpdatesInfFinal is disabled
<07/17/2006
13:14:33,d:\srv03rtm\base\ntsetup\syssetup\cmdline.c,229,,SETUP:
<SpSetupLoadParameter was unable to find
DynamicUpdateAdditionalPostGuiDrivers.
<07/17/2006
<13:14:33,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,5371,BEGIN_SECTION,Se
tting up Crash Recovery
<07/17/2006
<13:14:33,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,5375,END_SECTION,Sett
ing up Crash Recovery
<07/17/2006
<13:14:50,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,6218,END_SECTION,Remo
ving Temporary Files
<07/17/2006
<13:14:50,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,6225,,SETUP:
<CallSceSetupRootSecurity completed
<07/17/2006
<13:14:50,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,6242,,SETUP:
Changing
<registry quota from 117440512 to 58720256...
<07/17/2006
<13:14:50,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,6247,,SETUP: ...
<succeeded
<07/17/2006
<13:14:50,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,6267,END_SECTION,Fini
shThread
<07/17/2006
<13:14:50,d:\srv03rtm\base\ntsetup\syssetup\welcome.c,944,END_SECTION,Copyin
g
<Files Page
<07/17/2006
<13:14:50,d:\srv03rtm\base\ntsetup\syssetup\welcome.c,1110,BEGIN_SECTION,Fin
ish Page
<07/17/2006
<13:14:50,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,6682,END_SECTION,Wiza
rd
<07/17/2006
<13:14:50,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,6686,BEGIN_SECTION,Re
covery
<07/17/2006
<13:14:50,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,6690,END_SECTION,Reco
very
<07/17/2006
<13:14:50,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,6692,BEGIN_SECTION,Sh
utdown
<07/17/2006 13:14:50,d:\srv03rtm\base\ntsetup\syssetup\log.c,315,,GUI mode
<Setup has finished.
<
<07/17/2006
<13:14:50,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,6694,END_SECTION,Shut
down
<07/17/2006
<13:14:50,d:\srv03rtm\base\ntsetup\syssetup\registry.c,3619,,LogPidValues:
<ProductId20FromProductId30 is NOT empty
<
<07/17/2006
<13:14:50,d:\srv03rtm\base\ntsetup\syssetup\registry.c,3637,,LogPidValues:
<DigitalProductId is NOT empty
<
<07/17/2006
<13:14:50,d:\srv03rtm\base\ntsetup\syssetup\syssetup.c,6706,END_SECTION,Inst
alling Windows NT
<
<
<Any suggestion as to what might be the cause? Thanks
<
<--
<Tim Balderston
<iNet Business Solutions
<
<
<"Tim Balderston" wrote:
<
<> OK, I'll search for the log file. Once i do find it what specifically am
i
<> looking for? Is there a specific line (s) that i need to pay attention
to?
<> Should i post the information here?
<>
<> Thanks,
<> --
<> Tim Balderston
<> iNet Business Solutions
<>
<>
<> "Jabez Gan [MVP]" wrote:
<>
<> > Not sure why it was failing to uninstall/reinstall the Backup Exec,
but for
<> > the SP1 installation issue, please check the *setup.log file which
should be
<> > under C:\windows and see if you can find the log file.
<> >
<> > --
<> > Jabez Gan [MVP]
<> > Windows Server - File System
<> >
<> >
<> > "Tim Balderston" <TimBalderston@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
<> > news:2A7DF8FE-EAEA-4ED5-B495-B9E026BEB272@xxxxxxxxxxxxxxxx
<> > >I recently was asked to assist a company with their Windows Server
2003
<> > > repair. They recently had to replace one of their server hard drives
(RAID
<> > > 5
<> > > config) due to corrupt data and hardware. In doing so they had to
<> > > reinstall
<> > > (repair) the Windows Server 2003 OS with Dell's assistance (running
on a
<> > > Poweredge 1800). In doing so they lost several system services
(DHCP,
<> > > WINS,
<> > > etc.) dependent on the COM+ service which would not start. I was
able to
<> > > repair the OS to get the COM+ service to start allowing the other OS
<> > > dependent services to become working again.
<> > >
<> > > Once that was complete I began updating the server with all the
latest
<> > > updates and patches. Everything updated properly until it came time
to
<> > > install SP1 for Windows Server 2003. I tried using my SP1 CD and
Windows
<> > > Update to install SP1 but during the 'Finalizing Installation' phase
of
<> > > the
<> > > SP1 install the program quits without warning indicating the install
<> > > failed
<> > > and reverts all files back to the originals and restarts the server.
We
<> > > attempted this procedure several times with the same result each
time,
<> > > failing during the 'Finalizing Installation' phase. Can anyone
explain why
<> > > this may be occurring or provide us with some solutions to try? We
can't
<> > > seem
<> > > to find any similar install failure solutions.
<> > >
<> > > We are also experiencing some MSSQL$BACKUP issues (service will not
start,
<> > > hence Backup Exec wil not start), and the DCOM service will not
start.
<> > > We've
<> > > tried to uninstall Backup Exec with no success and we have tried
several
<> > > MS
<> > > KB solutions for the DCOM issue all without any success. We're
working
<> > > with
<> > > Symantec on the Backup Exec issue. Can these items be related to SP1
not
<> > > able
<> > > to complete it's install during the 'Finalizing Installation' phase?
We
<> > > were
<> > > hoping SP1 would update any necessary files to ensure the latest
operating
<> > > system files were installed and working.
<> > >
<> > > Any suggestions would be greatly appreciated. Thanks.
<> > > --
<> > > Tim Balderston
<> > > iNet Business Solutions
<> >
<> >
<> >
<
.
- Follow-Ups:
- Re: Windows Server 2003 SP1 install failure
- From: Tim Balderston
- Re: Windows Server 2003 SP1 install failure
- References:
- Re: Windows Server 2003 SP1 install failure
- From: Jabez Gan [MVP]
- Re: Windows Server 2003 SP1 install failure
- From: Tim Balderston
- Re: Windows Server 2003 SP1 install failure
- From: Tim Balderston
- Re: Windows Server 2003 SP1 install failure
- Prev by Date: RE: Windows server identifies the Intel EM64T Processor as an AMD64
- Next by Date: Re: windows 2003 server run out of space
- Previous by thread: Re: Windows Server 2003 SP1 install failure
- Next by thread: Re: Windows Server 2003 SP1 install failure
- Index(es):
Relevant Pages
|