Error 0x80040E14 updating to WSUS 3.0 SP2

[Tom]

Hello,

See error log below.

It's failing on making a backup but why is it trying to backup into a
folder with a ID# in it?
(ie: D:\WSUS\{14DDB0A0-C716-48FC-B12A-A2750D3C467E}\SUSDB.bak)

Every time I run it that ID number in {}'s is different, so there is
no point in creating the folder. Every other post I've read about
this did not have this in their log.

I've already made sure D:\WSUS has full control permissions for
Network Service, Authenticated Users, Users, etc. I'm running as
Administrator on SBS 2003.

Thanks,

Tom

2010-03-15 14:57:21 Success MWUSSetup Validating pre-
requisites...
2010-03-15 14:57:29 Success MWUSSetup Creating database
backup...
2010-03-15 14:57:38 Error MWUSSetup ExecuteQuery: Failed
to execute SQL query BACKUP DATABASE SUSDB to DISK=N'D:\WSUS\{14DDB0A0-
C716-48FC-B12A-A2750D3C467E}\SUSDB.bak' (Error 0x80040E14)
2010-03-15 14:57:38 Error MWUSSetup
ExecuteQueryGetNoResults: Failed to execute query BACKUP DATABASE
SUSDB to DISK=N'%s' (Error 0x80040E14)
2010-03-15 14:57:38 Error MWUSSetup BackupDatabase:
Failed to backup database (Error 0x80040E14)
2010-03-15 14:57:38 Error MWUSSetup
CUpgradeDriver::PerformSetup: Failed to backup database (Error
0x80040E14)
2010-03-15 14:57:38 Error MWUSSetup
CSetupDriver::LaunchSetup: Setup failed (Error 0x80040E14)
2010-03-15 14:57:49 Error MWUSSetup CWatsonHelper::Init:
Failed to load WER library. (Error 0x8007007E: The specified module
could not be found.)
2010-03-15 14:57:49 Error MWUSSetup
CSetupDriver::ReportFailure: Failed to initalize the CWatsonHelper.
This is expected on pre-Vista machines. (Error 0x80004005: Unspecified
error)
2010-03-15 14:57:49 Error MWUSSetup DoInstall: Wsus
setup failed (Error 0x80040E14)

[Lawrence Garvin [MVP]]

Post by Tom
Hello,
See error log below.
It's failing on making a backup but why is it trying to backup into a
folder with a ID# in it?
(ie: D:\WSUS\{14DDB0A0-C716-48FC-B12A-A2750D3C467E}\SUSDB.bak)
Every time I run it that ID number in {}'s is different, so there is
no point in creating the folder. Every other post I've read about
this did not have this in their log.
I've already made sure D:\WSUS has full control permissions for
Network Service, Authenticated Users, Users, etc. I'm running as
Administrator on SBS 2003.

Perhaps your account does not have the requisite permissions to READ from
the database, or execute a BACKUP of the database.

Note here that you're not getting a "Failed to WRITE" error, you're getting
a "Failed to execute query" error.

Also, quite relevant as to what you're trying to upgrade FROM -- you did not
share that detail.

[Tom]

Post by Lawrence Garvin [MVP]

Post by Tom
Hello,
See error log below.
It's failing on making a backup but why is it trying to backup into a
folder with a ID# in it?
(ie: D:\WSUS\{14DDB0A0-C716-48FC-B12A-A2750D3C467E}\SUSDB.bak)
Every time I run it that ID number in {}'s is different, so there is
no point in creating the folder.  Every other post I've read about
this did not have this in their log.
I've already made sure D:\WSUS has full control permissions for
Network Service, Authenticated Users, Users, etc.  I'm running as
Administrator on SBS 2003.

Perhaps your account does not have the requisite permissions to READ from
the database, or execute a BACKUP of the database.
Note here that you're not getting a "Failed to WRITE" error, you're getting
a "Failed to execute query" error.
Also, quite relevant as to what you're trying to upgrade FROM -- you did not
share that detail.
--
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2010)
My Blog:http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website:http://www.microsoft.com/wsus
My MVP Profile:http://mvp.support.microsoft.com/profile/Lawrence.Garvin

Currently running WSUS 3.0 SP1. Using the Administrator account, why
would it not have access?

Thanks,

Tom

[Tom]

Post by Lawrence Garvin [MVP]

Post by Tom
Hello,
See error log below.
It's failing on making a backup but why is it trying to backup into a
folder with a ID# in it?
(ie: D:\WSUS\{14DDB0A0-C716-48FC-B12A-A2750D3C467E}\SUSDB.bak)
Every time I run it that ID number in {}'s is different, so there is
no point in creating the folder.  Every other post I've read about
this did not have this in their log.
I've already made sure D:\WSUS has full control permissions for
Network Service, Authenticated Users, Users, etc.  I'm running as
Administrator on SBS 2003.

Perhaps your account does not have the requisite permissions to READ from
the database, or execute a BACKUP of the database.
Note here that you're not getting a "Failed to WRITE" error, you're getting
a "Failed to execute query" error.
Also, quite relevant as to what you're trying to upgrade FROM -- you did not
share that detail.
--
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2010)
My Blog:http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website:http://www.microsoft.com/wsus
My MVP Profile:http://mvp.support.microsoft.com/profile/Lawrence.Garvin

Currently running WSUS 3.0 SP1.  Using the Administrator account, why
would it not have access?
Thanks,
Tom- Hide quoted text -
- Show quoted text -

I noticed this error in Event Viewer:

Event Type: Error
Event Source: MSSQL$MICROSOFT##SSEE
Event Category: (2)
Event ID: 18210
Date: 3/17/2010
Time: 4:55:08 PM
User: TLMFRA\administrator
Computer: PIKESPEAK
Description:
BackupMedium::ReportIoError: write failure on backup device 'D:\WSUS
\{0D42355D-2F31-47EB-B7DB-F32154893546}\SUSDB.bak'. Operating system
error 112(There is not enough space on the disk.).

But there is 8.69GB free on C: and 66.3GB free on D:. The database is
2.9GB.

Thanks,

Tom

[Lawrence Garvin [MVP]]

Post by Tom
BackupMedium::ReportIoError: write failure on backup device 'D:\WSUS
\{0D42355D-2F31-47EB-B7DB-F32154893546}\SUSDB.bak'. Operating system
error 112(There is not enough space on the disk.).
But there is 8.69GB free on C: and 66.3GB free on D:. The database is
2.9GB.

Do you have quotas enabled on the server?

Thanks,

Tom

[Tom]

Post by Lawrence Garvin [MVP]

Post by Tom
BackupMedium::ReportIoError: write failure on backup device 'D:\WSUS
\{0D42355D-2F31-47EB-B7DB-F32154893546}\SUSDB.bak'. Operating system
error 112(There is not enough space on the disk.).
But there is 8.69GB free on C: and 66.3GB free on D:.  The database is
2.9GB.

Do you have quotas enabled on the server?
Thanks,
Tom
--
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2010)
My Blog:http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website:http://www.microsoft.com/wsus
My MVP Profile:http://mvp.support.microsoft.com/profile/Lawrence.Garvin

Yes, quotas are enabled.

I first saw Administrator had a low limit, and set it to No Limit, but
it didn't help. I then unchecked "Deny disk space to users exceeding
quota limit" in the Quota tab of the D: drive Properties. I was then
able to do the update!

But what I don't understand is how the quota stopped it. Even now, I
can sort the Quota Entries by disk space used and the most used is
BUILTIN, everyone else is under 1GB. The database itself was already
bigger.

Thanks,

Tom

[Lawrence Garvin [MVP]]

Post by Tom
Yes, quotas are enabled.
I first saw Administrator had a low limit, and set it to No Limit, but
it didn't help. I then unchecked "Deny disk space to users exceeding
quota limit" in the Quota tab of the D: drive Properties. I was then
able to do the update!

But what I don't understand is how the quota stopped it.

Because it's not the Administrator account that's involved in that quota,
it's the database service account that actually writes to the disk.

And if the database size already exceeds the quota . . .