top WSUS to SP1 issues

72 views
Skip to first unread message

Bobbie Harder (MSFT)

unread,
Jun 20, 2006, 10:40:06 PM6/20/06
to
Hi folks -
these Issues will be updated tomorrow in a KB and in the online WSUS SP1
readme, but I thought I'd get you an early draft before fit and finish to
help some of you blocked by the top issues we're seeing folks having with
upgrading to SP1:

*Important This post contains information about how to modify the registry.
Make sure to back up the registry before you modify it. Make sure that you
know how to restore the registry if a problem occurs. For more information
about how to back up, restore, and modify the registry, click the following
article number to view the article in the Microsoft Knowledge Base:
256986 (http://support.microsoft.com/kb/256986/) Description of the
Microsoft Windows registry


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 resynchronize your server.

2. 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:
HKLM\Software\Microsoft\Update Services\Server\Setup\WmsdeInstalled, from
"1" to "0"
before attempting to upgrade to WSUS SP1.
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:
a. HKLM\Software\Microsoft\Update Services\Server\Setup\WmsdeInstalled,
from "1" to "0"
before attempting to upgrade to WSUS SP1.
b. HKLM\Software\Microsoft\Update Services\Server\Setup\InstallType from
"0x80" to "0x20"

c. After updating these registry key values, initiate upgrade on backend
then 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 a clean install of WSUS SP1 since the database schema has
changed between WSUS RTM and WSUS SP1.

--
Bobbie Harder
Program Manager, WSUS
Microsoft

This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


mmcginley

unread,
Jun 21, 2006, 1:44:01 AM6/21/06
to
Thank you!

mmcginley

unread,
Jun 21, 2006, 2:03:01 AM6/21/06
to
Tried #3 and am getting:

[DBMSLPCN]SQL Server does not exist or access denied.
[DBMSLPCN]ConnectionOpen (Connect()).

DB is running and WSUS can connect to it. Performing command with an
account that is local admin.

Teich

unread,
Jun 21, 2006, 7:16:01 AM6/21/06
to
Thanks a ton!!
#4 did the trick on my WSUS-Server.
I already found the first Registry Key, but not second.
Also I don't have a remote SQL server, changing the second reg key helped.

Best regards,
Bernd Teichert

brianhahne

unread,
Jun 22, 2006, 11:15:03 AM6/22/06
to
Tnanks for getting this out there. Still having back-end upgrade issues
though. Recovered and re-tried the SP1 install, and it still fails.

One thing I find. We had a remote SQL server, and did NOT have ASP
installed, because IIS is not on the server. I installed the asp user, with
iisreg, and that seems to have helped resolve the missing aspnet user. But
shouldn't it be said that on a back-end, that IIS is a requirement? Maybe it
is and I missed it?

Lawrence Garvin (MVP)

unread,
Jun 22, 2006, 4:14:02 PM6/22/06
to
"brianhahne" <brian...@discussions.microsoft.com> wrote in message
news:E9730705-C610-4F91...@microsoft.com...

> Tnanks for getting this out there. Still having back-end upgrade issues
> though. Recovered and re-tried the SP1 install, and it still fails.
>
> One thing I find. We had a remote SQL server, and did NOT have ASP
> installed, because IIS is not on the server. I installed the asp user,
> with
> iisreg, and that seems to have helped resolve the missing aspnet user. But
> shouldn't it be said that on a back-end, that IIS is a requirement? Maybe
> it
> is and I missed it?

ASP and IIS are not requirements for the back-end server. I'd have to look
at a split-server install to see what exact accounts are created, and it's
possible that this is a flaw in the back-end SP1 installation (if it's
looking for an account that would not normally be there).

On the other hand, if the back-end were installed (and the installer
/created/ the ASPNET account and added it to the database), and then, at
some future time, IIS was installed, and uninstalled, it's also possible
that IIS /removed/ the ASPNET account.

Bobbie, or somebody from the WSUS team, may be able to comment on this
faster than I can actually "check it out".

--
Lawrence Garvin, M.S., MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, eveything else is at
http://wsusinfo.onsitechsolutions.com
...


brianhahne

unread,
Jun 22, 2006, 4:32:02 PM6/22/06
to
Thanks. Yeah, on our sql box (Windows 2003 SP1, SQL 2000 SP4) we definitely
had no ASPNET user. I used the iisreg command and it created the user.
It's odd, because WSUS has been working for months, in this setup. Just the
upgrade was failing. It now works thanks to the registry fix (STILL not sure
how that got messed up) as well as the orphaned users.

I see a LOT of people having SQL remote issues with SP1 installs. I would
recommend they delete all users and recreate the logins to try that fix.
Worked like a champ for me.


"Lawrence Garvin (MVP)" wrote:

> ....
>
>
>

jasonk...@gmail.com

unread,
Jul 7, 2006, 9:48:21 AM7/7/06
to
I am still having a issue upgrading. I had WSUS RTM and it still made
me uninstall WSUS before upgrading to SP1. Then when I say to use the
existing database and point it to the directory, the install fails.
This is a basic setup still using MSDE on the same computer as the IIS.
Here is the logfile. Any help would be greatly appreciated. (On a side
note I can install SP1 if I don't point it to the old database??)

2006-07-06 16:23:57 Error CustomActions.Dll SQL command is
returning error (Error 0x80004005: Unspecified error)
2006-07-06 16:23:57 Error CustomActions.Dll ExecuteSQLCommand
returning error (Error 0x80004005: Unspecified error)
2006-07-06 16:23:57 Error CustomActions.Dll Failed to execute SQL
script (Error 0x80004005: Unspecified error)
2006-07-06 16:23:57 Error CustomActions.Dll
BuildAndExecuteSQLQuery failed (Error 0x80004005: Unspecified error)
2006-07-06 16:23:57 Error CustomActions.Dll Failed to execute add
account SQL Script (Error 0x80004005: Unspecified error)
2006-07-06 16:23:57 Error CustomActions.Dll AddAccount returning
error (Error 0x80004005: Unspecified error)
2006-07-06 16:23:57 Error CustomActions.Dll Failed to add account
(Error 0x80004005: Unspecified error)
2006-07-06 16:23:57 Error CustomActions.Dll AddPermissions failed
(Error 0x80004005: Unspecified error)
2006-07-06 16:23:57 Error CustomActions.Dll Failed to add
permissions to the database (Error 0x80004005: Unspecified error)
2006-07-06 16:23:57 Error CustomActions.Dll InstallDatabase
failed (Error 0x80004005: Unspecified error)
2006-07-06 16:23:57 Error CustomActions.Dll Failed to setup the
database (Error 0x80004005: Unspecified error)
2006-07-06 16:23:57 Error CustomActions.Dll Failed to configure
the database (Error 0x80004005: Unspecified error)
2006-07-06 16:23:58 Error CustomActions.Dll SQL command is
returning error (Error 0x80004005: Unspecified error)
2006-07-06 16:23:58 Error CustomActions.Dll ExecuteSQLCommand
returning error (Error 0x80004005: Unspecified error)
2006-07-06 16:23:58 Error CustomActions.Dll Failed to execute SQL
script (Error 0x80004005: Unspecified error)
2006-07-06 16:23:58 Error CustomActions.Dll
BuildAndExecuteSQLQuery failed (Error 0x80004005: Unspecified error)
2006-07-06 16:23:58 Error CustomActions.Dll Failed to execute
remove database access SQL Script (Error 0x80004005: Unspecified error)
2006-07-06 16:23:58 Error CustomActions.Dll
RemoveDatabaseAccessToAccount returning error (Error 0x80004005:
Unspecified error)
2006-07-06 16:23:58 Error CustomActions.Dll Failed to remove
database access to account NT AUTHORITY\NETWORK SERVICE. This account
may still have access to SUSDB. (Error 0x80004005: Unspecified error)
2006-07-06 16:23:58 Error CustomActions.Dll SQL command is
returning error (Error 0x80004005: Unspecified error)
2006-07-06 16:23:58 Error CustomActions.Dll ExecuteSQLCommand
returning error (Error 0x80004005: Unspecified error)
2006-07-06 16:23:58 Error CustomActions.Dll Failed to execute SQL
script (Error 0x80004005: Unspecified error)
2006-07-06 16:23:58 Error CustomActions.Dll
BuildAndExecuteSQLQuery failed (Error 0x80004005: Unspecified error)
2006-07-06 16:23:58 Error CustomActions.Dll Failed to execute
remove database access SQL Script (Error 0x80004005: Unspecified error)
2006-07-06 16:23:58 Error CustomActions.Dll
RemoveDatabaseAccessToAccount returning error (Error 0x80004005:
Unspecified error)
2006-07-06 16:23:58 Error CustomActions.Dll Failed to remove
database access to account SERVER\ASPNETThis account may still have
access to SUSDB. (Error 0x80004005: Unspecified error)
2006-07-06 16:23:58 Error CustomActions.Dll SQL command is
returning error (Error 0x80004005: Unspecified error)
2006-07-06 16:23:58 Error CustomActions.Dll ExecuteSQLCommand
returning error (Error 0x80004005: Unspecified error)
2006-07-06 16:23:58 Error CustomActions.Dll Failed to execute SQL
script (Error 0x80004005: Unspecified error)
2006-07-06 16:23:58 Error CustomActions.Dll
BuildAndExecuteSQLQuery failed (Error 0x80004005: Unspecified error)
2006-07-06 16:23:58 Error CustomActions.Dll Failed to execute
remove database access SQL Script (Error 0x80004005: Unspecified error)
2006-07-06 16:23:58 Error CustomActions.Dll
RemoveDatabaseAccessToAccount returning error (Error 0x80004005:
Unspecified error)
2006-07-06 16:23:58 Error CustomActions.Dll Failed to remove
SUSDB access to SERVER\WSUS Administrators. This account may still have
access to SUSDB. (Error 0x80004005: Unspecified error)
2006-07-06 16:24:09 Error MWUSSetup MWUS Installation
Failed (Error 0x00000643: Fatal error during installation.)
2006-07-06 16:24:09 Error MWUSSetup InstallMSUS failed
(Error 0x80070643: Fatal error during installation.)
2006-07-06 16:24:09 Error MWUSSetup MWUS installation
failed (Error 0x80070643: Fatal error during installation.)
2006-07-06 16:24:09 Error MWUSSetup PerformInstall failed
(Error 0x80070643: Fatal error during installation.)
2006-07-06 16:24:09 Success MWUSSetup Rolling back
Installation
2006-07-06 16:24:09 Success MWUSSetup WSUS Server
installation failed. You can look at C:\Program Files\Update
Services\LogFiles\WSUSCa_060706_1618.log file to determine the cause of
the failure
2006-07-06 16:24:35 Success MWUSSetup WMSDE Uninstall
Succeeded
2006-07-06 16:24:35 Error MWUSSetup Failed to copy
Setup\UninstallHelper.exe to C:\Temp\1\UninstallHelper.exe (Error
0x80070003: The system cannot find the path specified.)
2006-07-06 16:24:35 Success MWUSSetup StringObtained:
Microsoft Windows Server Update Services could not create the database.
For more information, see the Setup logs "C:\Program Files\Update
Services\LogFiles\WSUSCa_060706_1618.log" and "C:\Program Files\Update
Services\LogFiles\WSUSSetup_060706_1617.log" .
2006-07-06 16:29:27 Error MWUSSetup WSUS Setup:
Performing Install Failed. (Error 0x80070643: Fatal error during
installation.)
2006-07-06 16:29:27 Error MWUSSetup WSUS Setup Failed.
(Error 0x80070643: Fatal error during installation.)

Reply all
Reply to author
Forward
0 new messages