Windows 2000 SP4 Fails to Install

  • Thread starter Thread starter CHANGE USERNAME TO westes
  • Start date Start date
C

CHANGE USERNAME TO westes

I'm not having any luck installing W2K SP4 onto a W2K server with SP3
installed. I get half way through the install and it consistently fails at
the same place, and then rolls back the changes. It never identifies
exactly which files caused the problem. Is there any log where a more
detaield record would be kept so I can investigate what is causing the
failure?
 
Here are the last few lines in my svpack.log from the failed W2K SP4
install. Can anyone interpret this well enough to suggest why my install
is failing?

--
Will
westes AT earthbroadcast.com


Starting process: C:\WINNT40\system32\shmgrate.exe UpdateOCVersion
***

Return Code = 0
***

Starting process: C:\WINNT40\system32\shmgrate.exe AddConfigurePrograms
***

Return Code = 0
***

Starting process: C:\WINNT40\system32\msmqprop.exe /u
***

Return Code = 4294967295
***

Starting process: C:\WINNT40\system32\wzcsetup.exe /i /P
***

Return Code = 2148467211
***

DoInstallation:RunInfProcesses for ProcessesToRun Failed
***

Service Pack 4 Setup encountered an error: An error in updating your system
has occurred.
***

Failed Deleting C:\WINNT40\system32\msiinst.tmp 2
***

VerifySize: Unable to verify size: Source = NULL: c:\winnt40\oem31.cat

***

An error in updating your system has occurred.

Select 'OK' to undo the changes that have been made, or select 'Cancel' to
quit. If you select 'Cancel', your system will be left in a partially
updated state and may not work correctly.
***

Message displayed to the user: An error in updating your system has
occurred.

Select 'OK' to undo the changes that have been made, or select 'Cancel' to
quit. If you select 'Cancel', your system will be left in a partially
updated state and may not work corr
***

User Input: OK
***

Starting process: C:\WINNT40\$NtServicePackUninstall$\spuninst\spuninst.exe
/~ -u
***

Dirty Uninstall was successful

***
 
Try installing this update and reboot. Then go back and try install SP4:

313664 Using 802.1x Authentication on Computers Running Windows 2000
http://support.microsoft.com/?id=313664

If you still have the problem, you can use the following steps to get more
verbose logging in the Setupapi.log file:

1. To set the Verbose logging level, you can add a value to the following
registry key:



HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup



Value Name: LogLevel

Data Type: REG_DWORD

Value: 0xFFFF

2. Reboot

3. Attempt the sp4 install

4. attach the setupapi.log to here.

5. remove the registry key in step 1 and reboot.
 
Emmers, I don't have a wireless network, so could you briefly explain why
that hotfix would help to install SP4?

--
Will
westes AT earthbroadcast.com

Emmers Presson said:
Try installing this update and reboot. Then go back and try install SP4:

313664 Using 802.1x Authentication on Computers Running Windows 2000
http://support.microsoft.com/?id=313664

If you still have the problem, you can use the following steps to get more
verbose logging in the Setupapi.log file:

1. To set the Verbose logging level, you can add a value to the following
registry key:



HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup



Value Name: LogLevel

Data Type: REG_DWORD

Value: 0xFFFF

2. Reboot

3. Attempt the sp4 install

4. attach the setupapi.log to here.

5. remove the registry key in step 1 and reboot.


--
Emmers Presson [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

CHANGE USERNAME TO westes said:
Here are the last few lines in my svpack.log from the failed W2K SP4
install. Can anyone interpret this well enough to suggest why my install
is failing?

--
Will
westes AT earthbroadcast.com


Starting process: C:\WINNT40\system32\shmgrate.exe UpdateOCVersion
***

Return Code = 0
***

Starting process: C:\WINNT40\system32\shmgrate.exe AddConfigurePrograms
***

Return Code = 0
***

Starting process: C:\WINNT40\system32\msmqprop.exe /u
***

Return Code = 4294967295
***

Starting process: C:\WINNT40\system32\wzcsetup.exe /i /P
***

Return Code = 2148467211
***

DoInstallation:RunInfProcesses for ProcessesToRun Failed
***

Service Pack 4 Setup encountered an error: An error in updating your system
has occurred.
***

Failed Deleting C:\WINNT40\system32\msiinst.tmp 2
***

VerifySize: Unable to verify size: Source = NULL: c:\winnt40\oem31.cat

***

An error in updating your system has occurred.

Select 'OK' to undo the changes that have been made, or select 'Cancel' to
quit. If you select 'Cancel', your system will be left in a partially
updated state and may not work correctly.
***

Message displayed to the user: An error in updating your system has
occurred.

Select 'OK' to undo the changes that have been made, or select 'Cancel' to
quit. If you select 'Cancel', your system will be left in a partially
updated state and may not work corr
***

User Input: OK
***

Starting process: C:\WINNT40\$NtServicePackUninstall$\spuninst\spuninst.exe
/~ -u
***

Dirty Uninstall was successful

***
Click to expand...
Click to expand...
 
Emmers, I don't have a wireless network, so could you briefly explain why
that hotfix would help to install SP4?
Click to expand...

Since Emmers may not be able to respond for a couple of days I will
respond. This hotfix updates several files and resolves a problem that
occurs on some systems. This will work independent of whether you have
wireless or not. If this isn't the issue it is most likely a permissions
issue either with registry keys or most likely with files. Generally
permission problems account for the majority of SP install issues. The
last one I worked on like this was caused by someone removing write
access for the System Account on the System32 directory. The verbose
logging that Emmers mentioned will help diagnose that or just do a check
of permissions on the system drive yourself.

Leonard Severt

Windows 2000 Server Setup Team
 
That hotfix did indeed resolve my problem. I did install W2K SP4 after
applying this hotfix.

Can you elaborate a little on what files it replaces and what is the nature
of the problem with those files?
 
If you notice in the svcpack.log file, the last process that started and
completed (Return Code) before the SP4 error was the following:

Starting process: C:\WINNT40\system32\wzcsetup.exe /i /P
***
Return Code = 2148467211

A return code other than 0 tells us that the process failed. In this case
the SP4 installation failed immediately following this error. Notice that
the previous process msmqprop.exe failed also, but that did not cause the
SP4 install to fail - this is probably because msmq did not need to be
updated since msmq was probably not installed. The SP4 install continued to
the next process.

The program wzcsetup.exe is installing wireless networking support - an
added bonus of SP4. The update 313664 installs the same wireless component.
My thought was to try installing 313664 separately and interactively so that
the error message that was encountered while installing the wireless update
would be exposed. However, the stand-alone install of 313664 completed,
which opened the way for the SP4 to complete. However, I cannot tell you why
installing wireless support failed on SP4 but succeeded separately.

--
Emmers Presson [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

CHANGE USERNAME TO westes said:
That hotfix did indeed resolve my problem. I did install W2K SP4 after
applying this hotfix.

Can you elaborate a little on what files it replaces and what is the nature
of the problem with those files?
Click to expand...
 
Try this:

1. Open Regedt32.exe and highlight HKEY_LOCAL_MACHINE
2. Click on the Security menu and then select permissions.
3. Verify the Administrator has full control. If not, add it here.
4. Click Advanced.
5. Select the "Reset Permissions on all child objects and enable
propagation in
inheritable permissions" check box, and then click OK.
6. Once the registry permissions have been reset, close out of
Regedt32.exe.
7. Apply Service Pack 4

If it still fails:

1. Locate and open SVCpack.log (the new setup log file for SP4).

2. Go to the end of the file, locate the error "An error in updating your
system
has occurred."

3. Go up from there and find the last call before the error with
information on
what was being run
"Starting process: C:\WINNT\system32\wzcsetup.exe /I /P" (or whatever
executable happens to be in your log file)

4. Look that log file up to determine what update it is hanging on, then
try to
follow this article in applying the update first, then reinstalling SP4.

Best regards,

Tom Montefusco
 
Back
Top