SP1 Install Error
Gareth
I get the following error when attempting to update my Windows 2003 server
to SP1... anyone encountered this before?
3823.516: Copied file: C:\Program Files\Support Tools\dcdiag.exe
3823.938: Copied file: C:\WINDOWS\system32\spool\DRIVERS\W32X86\3\unires.dll
3824.360: Copied file:
C:\WINDOWS\system32\spool\DRIVERS\W32X86\3\unidrvui.dll
3824.610: Copied file (delayed):
C:\WINDOWS\system32\spool\DRIVERS\W32X86\3\SET126B.tmp
3824.610: Copied file: C:\WINDOWS\system32\spool\DRIVERS\W32X86\3\unidrv.dll
3824.938: Copied file: C:\WINDOWS\system32\spool\DRIVERS\W32X86\3\pclxl.dll
3825.172: Copied file:
C:\WINDOWS\system32\spool\DRIVERS\W32X86\3\pcl5eres.dll
3886.297: PruneCatalogsFromHotfixes:RegQueryValueEx Failed: 0x2
3886.516: Num Ticks for Copying files : 2518938
3886.516: Starting process: C:\WINDOWS\uddisp.exe install
"g:\b04790d0e26d0fdff3\i386\"
12990.360: Return Code = 1603
12990.360: DoInstallation: RunInfProcesses for ProcessesToRunAfterCopying
failed.
12990.375: Service Pack 1 Setup encountered an error: An error in updating
your system has occurred.
13033.922: Unregistration of sprecovr successful
13034.453: An error in updating your system has occurred.
Select 'OK' to undo the changes that have been made.
13047.110: Message displayed to the user: An error in updating your system
has occurred.
Select 'OK' to undo the changes that have been made.
13047.110: User Input: OK
13047.250: Starting process:
C:\WINDOWS\$NtServicePackUninstall$\spuninst\spuninst.exe /~ -u -z
14767.766: Software Update Rollback has completed with return code 0xbc2.
This rollback requires a reboot.
14767.782: Service Pack 1 installation did not complete.
Windows Server 2003 has been partially updated and may not work properly.
14954.907: Message displayed to the user: Service Pack 1 installation did
not complete.
Windows Server 2003 has been partially updated and may not work properly.
14954.907: User Input: OK
14954.907: Update.exe extended error code = 0xf070
14954.907: Update.exe return code was masked to 0x643 for MSI custom action
compliance.
Shutdown Initiated in Self Extractor
***
Michael L. Meyer
I am getting the exact same error on my w2k3 Terminal Server. The SP1
installed fine on y SQL and Data servers, but on the TS, it gave me the same
errorcode (didn't look at the log for which part failed specifically)
looking forward to an answer from someone :)
Mike
Michael L. Meyer
file.
927.141: Starting process: C:\WINDOWS\system32\wbem\mofcomp.exe
C:\WINDOWS\system32\wbem\wlbsprov.mof
927.500: Return Code = 3
927.500: Starting process: C:\WINDOWS\system32\wbem\mofcomp.exe
C:\WINDOWS\system32\wbem\cimwin32.mof
929.859: Return Code = 3
929.859: DoInstallation:RunInfProcesses for ProcessesToRun Failed
929.859: Service Pack 1 Setup encountered an error: An error in updating
your system has occurred.
933.203: Unregistration of sprecovr successful
933.234: An error in updating your system has occurred.
Select 'OK' to undo the changes that have been made.
991.547: Message displayed to the user: An error in updating your system has
occurred.
Select 'OK' to undo the changes that have been made.
991.547: User Input: OK
991.547: Starting process:
C:\WINDOWS\$NtServicePackUninstall$\spuninst\spuninst.exe /~ -u -z
1203.391: Software Update Rollback has completed with return code 0xbc2.
This rollback requires a reboot.
1203.391: Service Pack 1 installation did not complete.
Windows Server 2003 has been partially updated and may not work properly.
2072.063: Message displayed to the user: Service Pack 1 installation did not
complete.
Windows Server 2003 has been partially updated and may not work properly.
2072.063: User Input: OK
2072.063: Update.exe extended error code = 0xf070
2072.063: Update.exe return code was masked to 0x643 for MSI custom action
compliance.
Shutdown Initiated in Self Extractor
***
any help would be appreciated.
Gareth
Yeah mine is running exchange 2003... I have managed to install SP1 now...
first I tried running 'sfc /scannow' and it did update some files, and I made
sure I had a latest versions of my drivers... however it still came up with
the same error.
What I tried next was to patch SP1 onto a full 2003 installation disk, then
run an upgrade installation, and that ran 100% fine, just had to re-activate
my virus program... altough the whole process took a lot lot longer.
Cheers
G
Keith Vinson
it doesn't have TS installed (except for remote admin, but it is a remote
domain controller) UDDISP.exe is the last step before it errors out.
4841.703: Starting process: C:\WINDOWS\uddisp.exe install
"e:\cd8d20dbf3e8308d090dbdfa4083\i386\\"
4846.500: Return Code = 1642
4846.500: DoInstallation: RunInfProcesses for ProcessesToRunAfterCopying
failed.
does anyone know how to get around this?
Thanks,
Keith
"Gareth" <Gar...@discussions.microsoft.com> wrote in message
news:4047A7FA-7EF5-47FE...@microsoft.com...
Sean
We just hit the same problem. Can you give us some detail on how you
got around it with the full installation disk? Cheers.
Sean
mhcooper
Did you get any resolution to your 0xf070 sp1 error when installing
Windows 2003 service pack?
I just received the same error message after installing Windows 2003
standard edition on a new HP machine.
I successfully installed 2003, SP1 on another machine, but it already
had the prior 20+ hot fixes.
--
mhcooper
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message1530401.html
Darrell Gorter[MSFT]
Did you recover from this? If so how did you do so?
Are your temp folders valid? We some similar failures with invalid
specified temp folders?
Thanks,
Darrell Gorter[MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
>Thread-Topic: SP1 Install Error
>thread-index: AcU40nVuzHhXTvjJQQK9+oyxLV62Bg==
>X-WBNR-Posting-Host: 66.51.112.179
>From: "=?Utf-8?B?TWljaGFlbCBMLiBNZXllcg==?="
<Michae...@discussions.microsoft.com>
>Subject: SP1 Install Error
>Date: Sun, 3 Apr 2005 21:55:01 -0700
>Lines: 39
>Message-ID: <0C3887EE-EBF0-4C50...@microsoft.com>
>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.0
>Newsgroups: microsoft.public.windows.server.general
>Path: TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.windows.server.general:61669
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>X-Tomcat-NG: microsoft.public.windows.server.general
Darrell Gorter[MSFT]
Is the error the same return code as reported?
In this case 3 or is the return coe different?
>927.141: Starting process: C:\WINDOWS\system32\wbem\mofcomp.exe
>C:\WINDOWS\system32\wbem\wlbsprov.mof
>927.500: Return Code = 3
>927.500: Starting process: C:\WINDOWS\system32\wbem\mofcomp.exe
>C:\WINDOWS\system32\wbem\cimwin32.mof
>929.859: Return Code = 3
Thanks,
Darrell Gorter[MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
>From: ine...@gmail.com (Sean)
>Newsgroups: microsoft.public.windows.server.general
>Subject: Re: SP1 Install Error
>Date: 10 Apr 2005 00:04:35 -0700
>Organization: http://groups.google.com
>Lines: 6
>Message-ID: <23b5bc6e.05040...@posting.google.com>
>References: <0C3887EE-EBF0-4C50...@microsoft.com>
>NNTP-Posting-Host: 150.101.218.66
>Content-Type: text/plain; charset=ISO-8859-1
>Content-Transfer-Encoding: 8bit
>X-Trace: posting.google.com 1113116676 31667 127.0.0.1 (10 Apr 2005
07:04:36 GMT)
>X-Complaints-To: groups...@google.com
>NNTP-Posting-Date: Sun, 10 Apr 2005 07:04:36 +0000 (UTC)
>Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli
ne.de!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!postnews.google.com!no
t-for-mail
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.general:33953
>X-Tomcat-NG: microsoft.public.windows.server.general
Darrell Gorter[MSFT]
Is this the return code 3 error in the svcpack log file
>927.141: Starting process: C:\WINDOWS\system32\wbem\mofcomp.exe
>C:\WINDOWS\system32\wbem\wlbsprov.mof
>927.500: Return Code = 3
>927.500: Starting process: C:\WINDOWS\system32\wbem\mofcomp.exe
>C:\WINDOWS\system32\wbem\cimwin32.mof
>929.859: Return Code = 3
Are you still seeing this?
Thanks,
Darrell Gorter[MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
>From: mhcooper <mhcoope...@mail.mcse.ms>
>Subject: Re: SP1 Install Error
>Date: Mon, 18 Apr 2005 16:31:37 -0500
>Message-ID: <mhcoope...@mail.mcse.ms>
>Organization: MCSE.MS forum
>User-Agent: MCSE.MS usenet gateway
>X-Newsreader: MCSE.MS usenet gateway
>X-Originating-IP: 208.198.188.2
>References: <0C3887EE-EBF0-4C50...@microsoft.com>
>Newsgroups: microsoft.public.windows.server.general
>NNTP-Posting-Host: mcse.ms 66.98.192.98
>Lines: 1
>Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP1
5.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.general:63170
>X-Tomcat-NG: microsoft.public.windows.server.general
Michael L. Meyer
No I still have not figured out a solution to this yet. SP1 installed fine
on machines that are not running terminal services so far it has only been
failing if the machine has TS already installed.
I will be attempting an "upgrade" from a streamlined sp1 w2k3 server cd to
see if the problem gets resolved.
Thanks for your help.
Mike
Darrell Gorter[MSFT]
What is your path?
I think the return code 3 is "The system cannot find the path specified"
Open a cmd prompt and type set.
Check your path.
Thanks,
Darrell Gorter[MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
>Thread-Topic: SP1 Install Error
>thread-index: AcVKg5/FiQhWXTdyRJu/b9r1pxLNqg==
>X-WBNR-Posting-Host: 207.34.105.246
>From: "=?Utf-8?B?TWljaGFlbCBMLiBNZXllcg==?="
<Michae...@discussions.microsoft.com>
>References: <0C3887EE-EBF0-4C50...@microsoft.com>
<lDfKJX4R...@TK2MSFTNGXA01.phx.gbl>
>Subject: RE: SP1 Install Error
>Date: Tue, 26 Apr 2005 10:16:03 -0700
>Lines: 93
>Message-ID: <7C69FA1D-8EDE-4DC7...@microsoft.com>
>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.0
>Newsgroups: microsoft.public.windows.server.general
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.general:35399
>X-Tomcat-NG: microsoft.public.windows.server.general
Michael L. Meyer
that's not the error that I am seeing in the log that I posted as much as it
is error code 3. I guess I don't follow your path question. the path is
showing the standard entries
(c:\windows\system32;c:\windows;c:\windows\system, etc, etc)
What makes you think that it is a path problem? i downloaded the full sp1
and ran it as is. I've also downlaoded the version using windowsupdate and
the result is the same. I don't think it is actually a path problem (though
I won't discount that yet).
do you suggest that I manually extract the sp1 to a folder I specify, add
that path to the environment variables then rerun the update?
Darrell Gorter[MSFT]
The return code 3 is usually a path cannot be found type of error.
The path could be a search of the existing path strings where an entry is
no longer valid, or it could be a path to the service pack install temp
file locations.
It could also be something the serivce pack is touching that is trying to
access a path of some type, like a driver or app install package, where the
source files are needed.
Thanks,
Darrell Gorter[MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
>Thread-Topic: SP1 Install Error
>thread-index: AcVLb2qTcpa4+NKsQ2C4ZWMYUwGwag==
>X-WBNR-Posting-Host: 207.34.105.246
>From: "=?Utf-8?B?TWljaGFlbCBMLiBNZXllcg==?="
<Michae...@discussions.microsoft.com>
>References: <0C3887EE-EBF0-4C50...@microsoft.com>
<lDfKJX4R...@TK2MSFTNGXA01.phx.gbl>
<7C69FA1D-8EDE-4DC7...@microsoft.com>
<izvXiz1S...@TK2MSFTNGXA02.phx.gbl>
>Subject: RE: SP1 Install Error
>Date: Wed, 27 Apr 2005 14:23:55 -0700
>Lines: 162
>Message-ID: <8CCE69DA-D8D2-4680...@microsoft.com>
>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.0
>Newsgroups: microsoft.public.windows.server.general
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.general:35504
>X-Tomcat-NG: microsoft.public.windows.server.general
QWERTYTPN1134
_ROOT_CAUSE_
I had the same issue. The root cause was a corrupt WMI database. When
the SP1 installation tried to register a new namespace or update
existing namespaces, it failed.
The easiest way to identify the WMI database corruption is to go to
WMIMGMT.MSC > Server Properties > Security tab. The Microsoft NLB
namespace should not have any subcontainers. Prior to resolving the
issue, the root namespace was repeated as subcontainers of the
Microsoft NLB namespace. I could select Root > Microsoft NLB >
Microsoft NLB > Microsoft NLB > Microsoft NLB (see attachments). Not
good! This of course is not how I discovered the issue, but it is the
easiest way to identify the issue.
_RESOLUTION__
Microsoft has provided the ability to run a consistency checker against
the WMI database that fixes this issue. The problem is, this
functionality is not included with the first release of Windows 2003 -
the functionality was added with SP1. So how do we run the consistency
checker if we cannot install SP1 on the server?
- Run the install for SP1
- When you receive the message that the SP1 installation has failed, do
not press OK (yet)
At this point, the SP1 .DLLs and .EXEs for WMI are installed and
available, even though SP1 setup has not completed successfully. We
know that as soon as we press the OK button SP1 will be removed, but we
can still issue the command to run the WMI database consistency
checker.
- At a command prompt, issue the following command. This will run the
WMI database consistency checker:
rundll32 wbemupgd, RepairWMISetup
- Check the file C:\WINDOWS\SYSTEM32\WBEM\LOGS\SETUP.LOG for the
following text:
(Wed Jun 14 19:00:26 2006): ERROR: wbemupgd.dll: The WMI repository has
failed to upgrade. The repository has been backed up to
C:\WINDOWS\system32\WBEM\Repository.001 and a new one created.
This indicates that the WMI database consistency checker has run
successfully, that it found consistency issues, and that it has created
a new repository.
- It is now safe to press OK in the message box indicating the SP1
installation has failed
Setup will uninstall SP1
- At the “Installation did not complete” message, press OK
Setup will restart the server automatically (you will not be prompted)
- Re-install SP1. The installation should be successful.
Sources:
http://www.microsoft.com/technet/scriptcenter/topics/help/wmi.mspx
+-------------------------------------------------------------------+
|Filename: WMI_Corrupt.jpg |
|Download: http://forums.techarena.in/attachment.php?attachmentid=6109|
+-------------------------------------------------------------------+
--
QWERTYTPN1134
------------------------------------------------------------------------
QWERTYTPN1134's Profile: http://forums.techarena.in/member.php?userid=15709
View this thread: http://forums.techarena.in/showthread.php?t=59722
qwertytpn1134
Root Cause
I had the same issue. The root cause was a corrupt WMI database. When
the SP1 installation tried to register a new namespace or update
existing namespaces, it failed.
The easiest way to identify the WMI database corruption is to go to
WMIMGMT.MSC > Server Properties > Security tab. The Microsoft NLB
namespace should not have any subcontainers. Prior to resolving the
issue, the root namespace was repeated as subcontainers of the
Microsoft NLB namespace. I could select Root > Microsoft NLB >
Microsoft NLB > Microsoft NLB > Microsoft NLB. Not good! This of course
is not how I discovered the issue, but it is the easiest way to identify
the issue.
- - - - - - - - - -
I broke this post into 2 pieces because of the 2K character limit. Dear
boardmaster: Please consider revising the limit, it's a significant
inconvenience.
--
qwertytpn1134
------------------------------------------------------------------------
qwertytpn1134
---Resolution-----
Microsoft has provided the ability to run a consistency checker against
the WMI database that fixes this issue. The problem is, this
functionality is not included with the first release of Windows 2003 -
the functionality was added with SP1. So how do we run the consistency
checker if we cannot install SP1 on the server?
- Run the install for SP1
- When you receive the message that the SP1 installation has failed, do
not press OK (yet)
At this point, the SP1 .DLLs and .EXEs for WMI are installed and
available, even though SP1 setup has not completed successfully. We
know that as soon as we press the OK button SP1 will be removed, but we
can still issue the command to run the WMI database consistency
checker.
- At a command prompt, issue the following command. This will run the
WMI database consistency checker:
rundll32 wbemupgd, RepairWMISetup
- Check the file C:\WINDOWS\SYSTEM32\WBEM\LOGS\SETUP.LOG for the
following text:
(Wed Jun 14 19:00:26 2006): ERROR: wbemupgd.dll: The WMI repository has
failed to upgrade. The repository has been backed up to
C:\WINDOWS\system32\WBEM\Repository.001 and a new one created.
--
qwertytpn1134
---Resolution, Continued-----
This indicates that the WMI database consistency checker has run
successfully, that it found consistency issues, and that it has created
a new repository.
- It is now safe to press OK in the message box indicating the SP1
installation has failed
Setup will uninstall SP1
- At the “Installation did not complete” message, press OK
Setup will restart the server automatically (you will not be prompted)
- Re-install SP1. The installation should be successful.
- - - - - - - - - - -
Doing this in 3 posts is more than a little inconvenient.