次の方法で共有

WSUS Clients Failing with Error 0x80244019 After Installing WSUS SP1

  • [アーティクル]

Last week I discovered that many of my servers were no longer updating successfully from my intranet Windows Server Update Services (WSUS) server. Looking in WindowsUpdate.log file, I noticed errors similar to the following:

2008-03-22 18:53:24:377 808 ba0 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190194
2008-03-22 18:53:24:377 808 ba0 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190194
2008-03-22 18:53:24:377 808 ba0 Misc WARNING: DownloadFileInternal failed for https://colossus:8530/selfupdate/wuident.cab: error 0x80190194
2008-03-22 18:53:24:377 808 ba0 Setup FATAL: IsUpdateRequired failed with error 0x80244019
2008-03-22 18:53:24:377 808 ba0 Setup WARNING: SelfUpdate: Default Service: IsUpdateRequired failed: 0x80244019
2008-03-22 18:53:24:377 808 ba0 Setup WARNING: SelfUpdate: Default Service: IsUpdateRequired failed, error = 0x80244019
2008-03-22 18:53:24:377 808 ba0 Agent * WARNING: Skipping scan, self-update check returned 0x80244019
2008-03-22 18:53:25:002 808 ba0 Agent * WARNING: Exit code = 0x80244019

Upon troubleshooting the problem, I discovered that the SelfUpdate virtual directory was not configured on my WSUS server (i.e. the server named COLOSSUS). To resolve the issue, I used IIS Manager to create the SelfUpdate virtual directory (using the local path C:\Program Files\Update Services\Selfupdate). I then used wuauclt /detectnow to force an update on one of my servers to confirm that this resolved the issue.

A little post mortem analysis further revealed the following event on COLOSSUS:

Event Type: Information
Event Source: MsiInstaller
Event Category: None
Event ID: 11724
Date: 3/22/2008
Time: 7:17:29 AM
Computer: COLOSSUS
Description:
Product: Microsoft Windows Server Update Services 3.0 -- Removal completed successfully.

Ah, yes...now it was all coming back to me. On the morning of March 22nd, I decided to install WSUS Service Pack 1 (SP1). Since I did not encounter any errors during the install, it appears that WSUS SP1 is the likely culprit for the missing SelfUpdate virtual directory.

Perhaps this only happens when you have WSUS installed on a non-standard port or when you have SharePoint installed on the WSUS server. As you can see in the excerpt from WindowsUpdate.log above, I am using port 8530 for the WSUS Web site. This is because COLOSSUS is currently running both WSUS and MOSS 2007.

Comments

  • Anonymous
    August 11, 2008
    Hi, The post was extremly helpful. After updating SP1 for SWUS3.0 it actually removed selfupdate virtual directory. I did not realized this at all. Its only when my servers and desktop machines  are not getting updates i noticed that SUS is no more funcitonal. Added the Virtual directory poing to the directiry C:Program FilesUpdate ServicesSelfupdate it started working. Thanx a ton Jeremy. regds, Ravikumar.K

  • Anonymous
    August 15, 2008
    You, sir, are a life-saver!  This happened to me too.  But it only happened on my 64-bit WSUS server.  Maybe a correlation there?  Is your server 64-bit too?  SP1 on my 32-bit WSUS server installed just fine...

  • Anonymous
    August 18, 2008
    My WSUS server (i.e. COLOSSUS) is 32-bit. It is powered by an AMD Athlon 64 X2 dual core processor -- I just haven't gotten around to putting 64-bit Windows Server 2008 on it yet ;-)

  • Anonymous
    April 20, 2010
    Thank you very much!  It worked for me too!  I have 26 WSUS servers in our enterprise, and ONE that was not working...  ARGH!  Thanks again for sharing. -C