oratek
asked on
WSUS 3.0 SP2 update (KB972455) fails
Hi All,
I am trying to apply windows WSUS update KB972455 however this update will not complete the install as the first phase of the update is the backup of the current WSUS database which fails.
Knowing that the update fails due to the backup failure is useful, however I cannot work out what is stopping the WSUS database backup from working.
I am running the update process from a downloaded version of the update and when started shows that the update can connect to the data base and even creates the SUS.DB file where the backup will be stored, but after a timeout period, the process fails with
2010-11-09 15:06:55 Success MWUSSetup Validating pre-requisites...
2010-11-09 15:06:56 Error MWUSSetup WSUS is outdated. But this will not block setup (Error 0x00000000: The operation completed successfully.)
2010-11-09 15:07:34 Success MWUSSetup Creating database backup...
2010-11-09 15:10:00 Error MWUSSetup ExecuteQuery: Failed to execute SQL query BACKUP DATABASE SUSDB to DISK=N'H:\WSUS\{23D11CFD-E 8EB-4439-B 93C-4C8230 4E8F41}\SU SDB.bak' (Error 0x80040E14)
2010-11-09 15:10:00 Error MWUSSetup ExecuteQueryGetNoResults: Failed to execute query BACKUP DATABASE SUSDB to DISK=N'%s' (Error 0x80040E14)
2010-11-09 15:10:00 Error MWUSSetup BackupDatabase: Failed to backup database (Error 0x80040E14)
2010-11-09 15:10:00 Error MWUSSetup CUpgradeDriver::PerformSet up: Failed to backup database (Error 0x80040E14)
2010-11-09 15:10:00 Error MWUSSetup CSetupDriver::LaunchSetup: Setup failed (Error 0x80040E14)
2010-11-09 15:18:40 Error MWUSSetup CWatsonHelper::Init: Failed to load WER library. (Error 0x8007007E: The specified module could not be found.)
2010-11-09 15:18:40 Error MWUSSetup CSetupDriver::ReportFailur e: Failed to initalize the CWatsonHelper. This is expected on pre-Vista machines. (Error 0x80004005: Unspecified error)
2010-11-09 15:18:40 Error MWUSSetup DoInstall: Wsus setup failed (Error 0x80040E14)
I am using MS SQL SERVER 2005 (installed with the last version of WSUS 3.0 sp1).
The database instance is MICROSOFT##SSEE
The server is a 2003R2 SP2 server fully patched
Any ideas
I am trying to apply windows WSUS update KB972455 however this update will not complete the install as the first phase of the update is the backup of the current WSUS database which fails.
Knowing that the update fails due to the backup failure is useful, however I cannot work out what is stopping the WSUS database backup from working.
I am running the update process from a downloaded version of the update and when started shows that the update can connect to the data base and even creates the SUS.DB file where the backup will be stored, but after a timeout period, the process fails with
2010-11-09 15:06:55 Success MWUSSetup Validating pre-requisites...
2010-11-09 15:06:56 Error MWUSSetup WSUS is outdated. But this will not block setup (Error 0x00000000: The operation completed successfully.)
2010-11-09 15:07:34 Success MWUSSetup Creating database backup...
2010-11-09 15:10:00 Error MWUSSetup ExecuteQuery: Failed to execute SQL query BACKUP DATABASE SUSDB to DISK=N'H:\WSUS\{23D11CFD-E
2010-11-09 15:10:00 Error MWUSSetup ExecuteQueryGetNoResults: Failed to execute query BACKUP DATABASE SUSDB to DISK=N'%s' (Error 0x80040E14)
2010-11-09 15:10:00 Error MWUSSetup BackupDatabase: Failed to backup database (Error 0x80040E14)
2010-11-09 15:10:00 Error MWUSSetup CUpgradeDriver::PerformSet
2010-11-09 15:10:00 Error MWUSSetup CSetupDriver::LaunchSetup:
2010-11-09 15:18:40 Error MWUSSetup CWatsonHelper::Init: Failed to load WER library. (Error 0x8007007E: The specified module could not be found.)
2010-11-09 15:18:40 Error MWUSSetup CSetupDriver::ReportFailur
2010-11-09 15:18:40 Error MWUSSetup DoInstall: Wsus setup failed (Error 0x80040E14)
I am using MS SQL SERVER 2005 (installed with the last version of WSUS 3.0 sp1).
The database instance is MICROSOFT##SSEE
The server is a 2003R2 SP2 server fully patched
Any ideas
ASKER
hi mcsjohn
Thanks for the suggestions.
- The rights on the H:WSUS folder include all administrators and the network service account with full rights.
I don't think file rights are an issue as the update process happily creates the backup folder and SUS.DB file. It just seems to stop at the point of actally exporting the data.
- H drive current has approximately 150Gb free space
- There are no quotas enabled on this server on any of the volumes.
This problem seems to be more evil.
Thanks for the suggestions.
- The rights on the H:WSUS folder include all administrators and the network service account with full rights.
I don't think file rights are an issue as the update process happily creates the backup folder and SUS.DB file. It just seems to stop at the point of actally exporting the data.
- H drive current has approximately 150Gb free space
- There are no quotas enabled on this server on any of the volumes.
This problem seems to be more evil.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
I accepted my own comment as the solution as it is the only solution and nobody else bothered to comment except for one very helpful expert.
- make sure the rights are setup for H:\WSUS (including NETWORK SERVICE account)
- do you have enough space on drive H for the backup?
- make sure quotas are not enabled or there are big enough for the backup