WSUS SP1 Update error
JonathanL
installd by WSUS installation.
I've tried installing SP1 via Windows Update and by downloading the full
install package.
I get the same error no matter what method I use. The WSUSupdatelog looks
like it's trying to do a database backup to a nonexistent location.
WSUS is installed at E:\WSUS. The error talks about a SQL backup error and
the log looks like it's trying to access the sql bak file at F:\WSUS. I did
an inernt search and all I found was to delete the .bak file which I did but
that didn't help.
Why is it trying to access WSUS on the wrong drive and how do I correct it?
I installed the update on another server and had absolutely no problems.
Lawrence Garvin [MVP]
news:B2ED4457-4DF5-4C34...@microsoft.com...
Let's start by looking at the actual server configs...
Please post the registry key at HKLM\Software\Microsoft\Update Services
--
Lawrence Garvin, M.S., MCBMSP, MCTS(x4), MCP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
JonathanL
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Registration]
"ProductID"="58737-835-9506861-04992"
"DigitalProductID"=hex:a4,00,00,00,03,00,00,00,35,38,37,33,37,2d,38,33,35,2d,\
39,35,30,36,38,36,31,2d,30,34,39,39,32,00,08,00,00,00,43,31,31,2d,30,32,37,\
34,31,00,00,00,00,00,00,00,00,3a,d3,f4,2c,d5,92,99,83,79,fd,ef,3d,02,03,00,\
00,00,00,00,5e,9e,54,46,71,b6,06,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,35,34,33,32,30,00,00,00,00,00,00,00,ec,03,\
00,00,97,b2,fb,54,80,07,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,b9,47,30,ee
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup]
"WmsdeInstalled"=dword:00000001
"PsfsipInstalled"=dword:00000001
"TargetDir"="C:\\Program Files\\Update Services\\"
"ContentDir"="E:\\WSUS"
"CreatedContentDir"=dword:00000000
"SqlServerName"=hex(2):25,00,63,00,6f,00,6d,00,70,00,75,00,74,00,65,00,72,00,\
6e,00,61,00,6d,00,65,00,25,00,5c,00,4d,00,49,00,43,00,52,00,4f,00,53,00,4f,\
00,46,00,54,00,23,00,23,00,53,00,53,00,45,00,45,00,00,00
"SqlAuthenticationMode"="WindowsAuthentication"
"SqlDatabaseName"="SUSDB"
"SqlUserName"=""
"SqlEncryptedPassword"=""
"InstallType"=dword:00000001
"EncryptionKey"=hex:01,00,00,00,d0,8c,9d,df,01,15,d1,11,8c,7a,00,c0,4f,c2,97,\
eb,01,00,00,00,65,a9,c0,de,5e,6d,7a,4f,ae,18,56,2c,99,74,a3,32,04,00,00,00,\
02,00,00,00,00,00,03,66,00,00,a8,00,00,00,10,00,00,00,b0,77,e3,f5,91,e2,48,\
99,e6,81,86,d8,b5,21,48,b3,00,00,00,00,04,80,00,00,a0,00,00,00,10,00,00,00,\
c1,eb,e3,5a,04,ca,50,44,bb,34,37,66,74,8f,2e,46,20,00,00,00,e8,f2,48,8b,43,\
70,27,f5,6c,0a,7f,29,ec,51,85,ba,50,b8,ab,34,36,b1,9a,17,4f,cc,1e,35,a3,65,\
7a,b6,14,00,00,00,94,03,28,ec,4a,7a,b9,47,e9,5b,6c,05,d8,9f,d3,a4,6b,68,8b,\
a7
@=""
"Version"=dword:00000003
"VersionString"="3.0.6000.374"
"ConfigurationSource"=dword:00000000
"ServicePackLevel"=dword:00000000
"EnableRemoting"=dword:00000001
"WsusAdministratorsSid"="S-1-5-21-686174102-1625661690-761356109-1011"
"WSUSReportersSid"="S-1-5-21-686174102-1625661690-761356109-1014"
"SqlInstanceIsRemote"=dword:00000000
"wYukonInstalled"=dword:00000001
"IISInstallRevision"="3.0.6000.374"
"IISPreviousInstallRevision"=""
"IISUninstallConfigFilePath"="C:\\Program Files\\Update
Services\\setup\\UninstallSettings.xml"
"IISTargetWebSiteCreated"="False"
"IISTargetWebSiteIndex"=dword:00000001
"SmtpUserPassword"="AQAAANCMnd8BFdERjHoAwE/Cl+sBAAAAMRb/v5QOwEWZfc++Syr2wQAAAAACAAAAAAADZgAAqAAAABAAAACERfJPBLTPY5TAij9xn4/YAAAAAASAAACgAAAAEAAAAEaMXHguy1LGMht/YtOSgGQwAAAAsHwGa3AqfCwwF2PrKQ8dOItLebbWoXAZkVSYtPagiPxwfTDlAAdWnMW2MeWpnF3dFAAAABeUmDEiOB+eUFsz+sX1V58lqTS0"
"ProxyPassword"=""
"PortNumber"=dword:00000050
"IIsDynamicCompression"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\SetupFailure]
"ErrorType"=dword:00000000
Lawrence Garvin [MVP]
>> > Windows Server 2003 SP2, fully patched, running WSUS 3.0 with the
>> > database
>> > installd by WSUS installation.
>> > I've tried installing SP1 via Windows Update and by downloading the
>> > full
>> > install package.
>> > I get the same error no matter what method I use. The WSUSupdatelog
>> > looks
>> > like it's trying to do a database backup to a nonexistent location.
>> > WSUS is installed at E:\WSUS. The error talks about a SQL backup error
>> > and
>> > the log looks like it's trying to access the sql bak file at F:\WSUS. I
>> > did
>> > an inernt search and all I found was to delete the .bak file which I
>> > did
>> > but
>> > that didn't help.
>> > Why is it trying to access WSUS on the wrong drive and how do I correct
>> > it?
>> Let's start by looking at the actual server configs...
>>
>> Please post the registry key at HKLM\Software\Microsoft\Update Services
> Windows Registry Editor Version 5.00
> "WmsdeInstalled"=dword:00000001
> "PsfsipInstalled"=dword:00000001
> "TargetDir"="C:\\Program Files\\Update Services\\"
> "ContentDir"="E:\\WSUS"
> "VersionString"="3.0.6000.374"
> "SqlInstanceIsRemote"=dword:00000000
> "wYukonInstalled"=dword:00000001
Okay.. the configs concur with your claim -- that WSUS is installed on the
E:\ drive.
It also appears that this server was previously upgraded from WSUS v2. Is
this correct?
If so, did you have any issues performing the upgrade.
Reviwing the Release Notes for WSUS v3 RTM and WSUS v3 SP1, are there are
scenarios in the notes that might apply to you?
(e.g. have you renamed anything, migrated anything, moved anything, changed
permissions on anything,
uninstalled anything from the WSUS Server that used to be installed,
installed anything to the WSUS Server that wasn't installed previously?)
If no to all of the above, then our next best step is to look at the actual
log files where the error is occuring.
JonathanL
v3 upgrade. I don't recall though if there were any difficulties.
I'll have to go through the release notes and get back to you, though I can
say that I haven't renamed, migrated, moved, or changed permissions on
anything related to WSUS that I can think of. This server is the only one I
have so it is also a file server and since it is an HP server I have
installed proliant support packs and associated software on it. I'll have to
look and see if there is anything else on it. No other major apps are
installed, maybe some minor utilities. I'll have to look next time I'm at the
server.
JonathanL
what is installed is: Adobe Reader, Java 6, GPMC, Word Viewer, Silverlight,
NTP Query Tool, Windows Defender, IE7, Resource Kit & Support Tools,
Adminpak, Server 2003 ABE, SNMP, DNS, DHCP, WINS, McAfee Virus Scanner. I
believe that's it. In looking over the SP1 release notes, I'm thinking I need
to shut down McAfee, reboot, then try installing SP1.
JonathanL
part of the wsussetuplog.log that has today's entries. Do you want to see the
entire log?
2008-04-02 20:01:01 Success MWUSSetup Validating pre-requisites...
2008-04-02 20:01:15 Success MWUSSetup Creating database backup...
2008-04-02 20:01:16 Error MWUSSetup ExecuteQuery: Failed to
execute SQL query BACKUP DATABASE SUSDB to DISK=N'F:\WSUS\SUSDB.bak' (Error
0x80040E14)
2008-04-02 20:01:16 Error MWUSSetup ExecuteQueryGetNoResults:
Failed to execute query BACKUP DATABASE SUSDB to DISK=N'%s' (Error 0x80040E14)
2008-04-02 20:01:16 Error MWUSSetup BackupDatabase: Failed to
backup database (Error 0x80040E14)
2008-04-02 20:01:16 Error MWUSSetup
CUpgradeDriver::PerformSetup: Failed to backup database (Error 0x80040E14)
2008-04-02 20:01:16 Error MWUSSetup CSetupDriver::LaunchSetup:
Setup failed (Error 0x80040E14)
2008-04-02 20:01:25 Error MWUSSetup DoInstall: Wsus setup
failed (Error 0x80040E14)
JonathanL
database to F:\WSUS even though WSUS is installed in E:\WSUS. I had
previously created a WSUS folder on F: but it didn't help. So after doing
more internet research, I made sure the Network Service account had Modify
acces to F:\WSUS. Voila! Upgrade went without a single hitch.
Thanks for the help!
Lawrence Garvin [MVP]
> Besides what's needed to run WSUS and aforementioned HP management
> software,
> what is installed is: Adobe Reader, Java 6, GPMC, Word Viewer,
> Silverlight,
> NTP Query Tool, Windows Defender, IE7, Resource Kit & Support Tools,
> Adminpak, Server 2003 ABE, SNMP, DNS, DHCP, WINS, McAfee Virus Scanner. I
> believe that's it. In looking over the SP1 release notes, I'm thinking I
> need
> to shut down McAfee, reboot, then try installing SP1.
Attempting to install software with problematic, or non-supportive, AV
software is one of the leading causes of installation failures. :-)
Is this a =current= version of McAfee?
--
Lawrence Garvin, M.S., MCITP, MCBMSP, MCTS(x4), MCP
Lawrence Garvin [MVP]
> I got it figured out! The upgrade was wanting to save a backup of the
> database to F:\WSUS even though WSUS is installed in E:\WSUS. I had
> previously created a WSUS folder on F: but it didn't help. So after doing
> more internet research, I made sure the Network Service account had Modify
> acces to F:\WSUS. Voila! Upgrade went without a single hitch.
It's possible that the WSUS 3 SP1 installer has been modified to backup the
database to the logical volume with the most available free space.
There was some criticism offered as a result of the WSUS 2 SP1 upgrade
installer trying to put the database backup into the active ~\WSUS folder,
particularly as affected admins who then uninstalled WSUS v2 after a failed
upgrade, which then promptly deleted the database backup just performed.
I'll see if I can get some feedback (confirmation) on this possible change
in behavior.
--
Lawrence Garvin, M.S., MCITP, MCBMSP, MCTS(x4), MCP
JonathanL
with the issue, yes McAfee is completely updated, patches, dat files, and all.
JonathanL
scanning the release notes but I may have missed it. As it turns out, the F:
drive does have more room than E:. On another server I have WSUS on
(completely different location, no connection except me), there's only one
data drive so the backup was done there as I don't think any backup would be
done to the C: system drive.
Lawrence Garvin [MVP]
news:A90156D7-4217-4412...@microsoft.com...
> "JonathanL" <Jona...@discussions.microsoft.com> wrote in message
> news:BA743FDE-C328-4DDC...@microsoft.com...
>> I got it figured out! The upgrade was wanting to save a backup of the
>> database to F:\WSUS even though WSUS is installed in E:\WSUS. I had
>> previously created a WSUS folder on F: but it didn't help. So after doing
>> more internet research, I made sure the Network Service account had
>> Modify
>> acces to F:\WSUS. Voila! Upgrade went without a single hitch.
>
> It's possible that the WSUS 3 SP1 installer has been modified to backup
> the database to the logical volume with the most available free space.
It's always amazing what one can find in the Release Notes.... <g>
Setup will overwrite a previous database backup
WSUS 3.0 SP1 setup will add the database to the default directory, which is
drive\WSUS (where drive is the local NTFS drive that has the greatest amount
of free space). If there is a database backup in this directory, it may be
overwritten. Administrators should save a database backup of the current
version in a different location before upgrading to WSUS 3.0 SP1.