Known problems when you upgrade to Windows Software Update Services (WSUS) Service Pack 1 (921477)

MORE INFORMATION

Proxy server user name and password settings are reset

If you are using a proxy server, upgrading to WSUS SP1 may reset the proxy server user name and password settings. When this occurs, you receive the following error message when you try to synchronize the updates from the Microsoft servers: To resolve this problem, reset the proxy server user name and password, and then re-synchronize the server. To do this, follow these steps:

1. Start Internet Explorer.
2. On the Tools menu, click Internet Options.
3. On the Connections tab, click LAN Settings.
4. Under Proxy server, clear the Address, Port, and Use a proxy server for your LAN check boxes.
5. Click OK two times.

WSUS SP1 does not update WSUS servers that are set up using remote SQL deployments

To resolve this problem, WSUS SP1 must be installed on both the front end server and the back end server. First, install WSUS SP1 by using the upgrade option on the front end server without using switches. Then, do the same on the back end server.

Computer name changes after you install the original release version of WSUS and before you install WSUS SP1

To work around this problem, use the following script to remove and then replace the ASPNET and WSUS Administrators groups. Then, run the upgrade option again.

Note In the last line of this script, replace <ContentDirectory> with the path of the actual content store.

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"

WSUS SP1 upgrade may fail when the Microsoft SQL Server 2000 Desktop Engine (Windows) (MSDE) database has been migrated to a local SQL Server 2000 computer

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

If this problem occurs, you must change the value for the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup\WmsdeInstalled registry subkey from 1 to 0. To do this, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup

3. In the right pane, right-click WmsdeInstalled, and then click Modify.
4. In the Value data box, type 0, and then click OK.
5. Exit Registry Editor.
6. Upgrade to WSUS SP1.

WSUS SP1 upgrade may fail when the MSDE database has been migrated to a remote SQL Server 2000 computer

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

If this problem occurs, you must change the values of the following registry subkeys:

• You must change the value of the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup\WmsdeInstalled subkey from 1 to 0.
• You must change the value of the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup\InstallType subkey from 0x80 to 0x20.

To do this, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup

3. In the right pane, right-click WmsdeInstalled, and then click Modify.
4. In the Value data box, type 0, and then click OK.
5. Locate and then click the following registry subkey:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup

6. In the right pane, right-click InstallType, and then click Modify.
7. In the Value data box, type 0x20, and then click OK.
8. Exit Registry Editor.
9. Upgrade to WSUS SP1 on the back end server.
10. Upgrade to WSUS SP1 on the front end server.

WSUS database is in an inconsistent state after a failed upgrade

If the upgrade to WSUS SP1 fails, the WSUS database may be in an inconsistent and unusable state. To retry the upgrade, you can use the original WSUS backup database that was created at the start of the upgrade process to restore the WSUS database to a consistent state. To do this, follow these steps:

1. Determine the location of the backup database. To do this, review the contents of the %SystemRoot%\Program Files\Update Services\LogFilesWSUSSetup_%timestamp%.log file.
2. Restore the backup database on the computer that is running WSUS. To do this, run the following script.
   
   Note Replace <PathToDatabaseBackup> with the location of the backup database that you determined in step 1. Then, replace <DatabaseInstance> with the value from the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup\SqlServerName registry subkey.

   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"

3. Uninstall WSUS and keep the WSUS database, log files, and update files when you are prompted to remove them. Make sure that all the check boxes on the Remove Microsoft Windows Server Update Services screen are unchecked.
4. Reinstall the original release version of WSUS to return the WSUS database to a consistent state. Use the existing database when you are prompted for the database.
   
   Note You cannot use the database that you backed up in step 1 in a clean install of WSUS SP1 because the database schema in the original release version of WSUS differs from the schema in WSUS SP1.
5. Install WSUS SP1.