WSUS SP1 Known Issues

Bobbie Harder (MSFT) has posted a list of Top known issues whilst upgrading WSUS to WSUS SP1 on microsoft.public.windows.server.update_services. These issues will be updated in a KB and in the online WSUS SP1 readme.


1.  If you are using a proxy server, in some cases the SP1 upgrade may clear the proxy configuration username and password.  This may cause synchronization of updates from Microsoft Servers to generate an “invalid parameter” error. To address this issue, reset the proxy configuration username and password and re-synchronize your server.


2. Remote SQL deployments: WSUS SP1 is not updating WSUS servers which are setup using remote SQL deployments.


Solution:


The WSUS with SP1 setup Package must be run on both the front end and back end servers.


·         Run the setup package on the front end with no switches and choose to upgrade


·         Run the setup package on the back end with no switches and choose to upgrade.


3. Changed Machine Name after RTM install prior to SP1 upgrade can cause the WSUS SP1 upgrade to fail.


Workaround:


Use the following script to remove and re-add the ASPNET and WSUS Administrators groups.  Then run the upgrade again.


osql.exe -S %computername%\WSUS -E -Q “USE SUSDB DECLARE @asplogin
varchar(200) SELECT @asplogin=name from sysusers WHERE name like ‘%ASPNET’
EXEC sp_revokedbaccess @asplogin”
osql.exe -S %computername%\WSUS -E -Q “USE SUSDB DECLARE @wsusadminslogin
varchar(200) SELECT @wsusadminslogin=name from sysusers WHERE name like
‘%WSUS Administrators’ EXEC sp_revokedbaccess @wsusadminslogin”


osql.exe -S %computername%\WSUS -E -Q “USE SUSDB DECLARE @asplogin
varchar(200) SELECT @asplogin=HOST_NAME()+’\ASPNET’ EXEC sp_grantlogin
@asplogin EXEC sp_grantdbaccess @asplogin EXEC sp_addrolemember
webService,@asplogin”
osql.exe -S %computername%\WSUS -E -Q “USE SUSDB DECLARE @wsusadminslogin
varchar(200) SELECT @wsusadminslogin=HOST_NAME()+’\WSUS Administrators’ EXEC
sp_grantlogin @wsusadminslogin EXEC sp_grantdbaccess @wsusadminslogin EXEC
sp_addrolemember webService,@wsusadminslogin”


osql.exe -S %computername%\WSUS -E -Q “backup database SUSDB to
disk=N'<ContentDirectory>\SUSDB.Dat’ with init”
Note you may have  to replace <ContentDirectory> in the last line with the
path to your actual content store.


4.            


a. WSUS SP1 upgrade can fail in some cases when the WMSDE database has been migrated to a  local SQL 2000 server.


Cause:  


A registry key value must be changed in order for WSUS SP1 setup package to recognize there is no wmsde database to update.


Workaround:


If users have migrated WMSDE to a SQL server (local or remote) they must change the value of the following registry key:


1.      HKLM\Software\Microsoft\Update Services\Server\Setup\WmsdeInstalled, from “1” to “0” before attempting to upgrade to WSUS SP1.


 


According to Bernd Teichert (blog reader), In some cases, you might have to change the InstallType too on local SQL 2000 Server installation;


2.      HKLM\Software\Microsoft\Update Services\Server\Setup\InstallType from “0x80” to “0x20”. 


b. WSUS SP1 upgrade can fail in some cases when the WMSDE database has been migrated to a remote SQL 2000 server.


Cause:  


Two registry key values must be changed in order for WSUS sp1 setup package to recognize there is no wmsde database to update and the update must be initiated on the backend, followed by the front end server.


Workaround:


If users have migrated WMSDE to a SQL server (local or remote) they must change the values of the following registry keys:


1.      HKLM\Software\Microsoft\Update Services\Server\Setup\WmsdeInstalled, from “1” to “0” before attempting to upgrade to WSUS SP1.


2.      HKLM\Software\Microsoft\Update Services\Server\Setup\InstallType from “0x80” to “0x20”. 


After updating these registry key values, initiate upgrade on backend and then on front end servers.


 


5. How to recover from a failed upgrade to restore your WSUS server to a consistent state and then retry the upgrade.


Description:


If the upgrade to WSUS SP1 fails it can leave your WSUS installation in an inconsistent and/or unusable state. In order to retry upgrading to WSUS SP1 you need to get your WSUS installation to a consistent state. To do this you can use the backup database created at the beginning of the upgrade process to restore your WSUS server to a pre-upgrade state.


Workaround:  


If the upgrade operation to WSUS SP1 is unsuccessful, you can use the original WSUS backup database that was created at the start of the upgrade process to restore WSUS to a consistent state. In the event of a failed upgrade follow these steps to retry upgrading to WSUS SP1:


To retry upgrading to WSUS SP1;


1.       Determine the location of the backup database by reviewing the contents of the WSUSSetup_%timestamp%.log file. This file is located in the following folder – %programfiles%\Update Services\LogFiles.


2.       Restore the backup database on the WSUS computer.


·         osql.exe -S <DatabaseInstance> -E -Q “USE master ALTER DATABASE
SUSDB SET SINGLE_USER WITH ROLLBACK IMMEDIATE RESTORE DATABASE SUSDB FROM
DISK=N'<PathToDatabaseBackup>’ WITH REPLACE ALTER DATABASE SUSDB SET
MULTI_USER”


·         Remember to replace <DatabaseInstance> and <PathToDatabaseBackup> with values from your installation.


·        For <DatabaseInstance> use the value from the following registry key:
HKLM\Software\Microsoft\Update Services\Server\Setup\SqlServerName


·        For <PathToDatabaseBackup> use the value you identified in step 1.


3.       Uninstall WSUS, but keep the WSUS database, log files and update files when you are prompted to remove them (i.e. Ensure that all options in “Remove Microsoft Windows Server Update Services” are unchecked).


4.       Reinstall WSUS RTM (the original version not WSUS with SP1). Use the existing database when you are prompted to do this. This will return your WSUS system to a consistent state.


5.       Install WSUS SP1.


* Note that you cannot use the backed up database from step 1 above directly in clean install of WSUS SP1 since the database schema has changed between WSUS RTM and WSUS SP1.


For any issues related to WSUS SP1 upgrade, you can post your queries directly on the following thread on microsoft.public.windows.server.update_services.

2 thoughts on “WSUS SP1 Known Issues

Leave a Reply

Your email address will not be published. Required fields are marked *