WSUS 3.0 clients failed with error 0x80244019

I have this problem in 300+ computers, although their name showed up
in WSUS compuetr list, they aren't getting any update or sending any
report. I've looked on the Internt by that code and most resolution I
found were about syncing with the Windows Update server *on the
Internet*, which does not really fit in my case here.

Could someone give me some hint? Below is a copy of WindowsUpdate.log


**************************************************************************************************** *****
008-03-05 10:54:49:088 1212 e14 Misc =========== Logging initialized
(build: 7.0.6000.381, tz: -0800) ===========
2008-03-05 10:54:49:088 1212 e14 Misc = Process: D:\WINDOWS
\System32\svchost.exe
2008-03-05 10:54:49:088 1212 e14 Misc = Module: D:\WINDOWS
\system32\wuaueng.dll
2008-03-05 10:54:49:088 1212 e14 Service *************
2008-03-05 10:54:49:088 1212 e14 Service ** START ** Service: Service
startup
2008-03-05 10:54:49:088 1212 e14 Service *********
2008-03-05 10:54:49:088 1212 e14 Agent * WU client version
7.0.6000.381
2008-03-05 10:54:49:088 1212 e14 Agent * Base directory: D:\WINDOWS
\SoftwareDistribution
2008-03-05 10:54:49:088 1212 e14 Agent * Access type: No proxy
2008-03-05 10:54:49:104 1212 e14 Agent * Network state: Connected
2008-03-05 10:54:51:776 1212 9b4 Agent *********** Agent:
Initializing Windows Update Agent ***********
2008-03-05 10:54:51:776 1212 9b4 Agent *********** Agent:
Initializing global settings cache ***********
2008-03-05 10:54:51:776 1212 9b4 Agent * WSUS server: http://BETA
2008-03-05 10:54:51:776 1212 9b4 Agent * WSUS status server: http://BETA
2008-03-05 10:54:51:776 1212 9b4 Agent * Target group: (Unassigned
Computers)
2008-03-05 10:54:51:776 1212 9b4 Agent * Windows Update access
disabled: No
2008-03-05 10:54:51:776 1212 9b4 DnldMgr Download manager restoring 0
downloads
2008-03-05 10:54:51:791 1212 9b4 AU ########### AU: Initializing
Automatic Updates ###########
2008-03-05 10:54:51:791 1212 9b4 AU AU setting next detection timeout
to 2008-03-05 18:54:51
2008-03-05 10:54:52:307 1212 9b4 AU # WSUS server: http://BETA
2008-03-05 10:54:52:307 1212 9b4 AU # Detection frequency: 22
2008-03-05 10:54:52:307 1212 9b4 AU # Approval type: Scheduled
(Policy)
2008-03-05 10:54:52:307 1212 9b4 AU # Scheduled install day/time:
Thursday at 4:00
2008-03-05 10:54:52:307 1212 9b4 AU # Auto-install minor updates: No
(Policy)
2008-03-05 10:54:52:651 1212 e14 Report *********** Report:
Initializing static reporting data ***********
2008-03-05 10:54:52:651 1212 e14 Report * OS Version =
5.1.2600.2.0.65792
2008-03-05 10:54:52:666 1212 e14 Report * Computer Brand = INTEL_
2008-03-05 10:54:52:666 1212 e14 Report * Computer Model = DG965WH_
2008-03-05 10:54:52:682 1212 e14 Report * Bios Revision = MQ96510J.
86A.1687.2007.0510.0258
2008-03-05 10:54:52:682 1212 e14 Report * Bios Name = Default System
BIOS
2008-03-05 10:54:52:682 1212 e14 Report * Bios Release Date =
2007-05-10T00:00:00
2008-03-05 10:54:52:682 1212 e14 Report * Locale ID = 1028
2008-03-05 10:54:53:041 1212 9b4 AU Setting AU scheduled install time
to 2008-03-06 12:00:00
2008-03-05 10:54:53:041 1212 9b4 AU AU finished delayed initialization
2008-03-05 10:54:53:041 1212 e14 AU #############
2008-03-05 10:54:53:041 1212 e14 AU ## START ## AU: Search for
updates
2008-03-05 10:54:53:041 1212 e14 AU #########
2008-03-05 10:54:53:041 1212 e14 AU <<## SUBMITTED ## AU: Search for
updates [CallId = {95912018-64B6-4360-B0F4-EC740214B26B}]
2008-03-05 10:54:53:041 1212 9b4 AU Triggering AU detection through
DetectNow API
2008-03-05 10:54:53:041 1212 9b4 AU Piggybacking on an AU detection
already in progress
2008-03-05 10:54:53:073 1212 6cc Report WARNING: Reporter failed to
upload events with hr = 8024000c.
2008-03-05 10:54:53:073 1212 6cc Agent *************
2008-03-05 10:54:53:073 1212 6cc Agent ** START ** Agent: Finding
updates [CallerId = AutomaticUpdates]
2008-03-05 10:54:53:073 1212 6cc Agent *********
2008-03-05 10:54:53:073 1212 6cc Agent * Online = Yes; Ignore
download priority = No
2008-03-05 10:54:53:073 1212 6cc Agent * Criteria = "IsHidden=0 and
IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or
IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and
IsAssigned=1 or IsHidden=0 and IsInstalled=1 and
DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1
or IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation'
and IsAssigned=1 and RebootRequired=1"
2008-03-05 10:54:53:073 1212 6cc Agent * ServiceID = {3DA21691-
E39D-4DA6-8A4B-B43877BCB1B7}
2008-03-05 10:54:53:073 1212 6cc Misc Validating signature for D:
\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2008-03-05 10:54:53:073 1212 6cc Misc Microsoft signed: Yes
2008-03-05 10:55:05:089 1212 6cc Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190194
2008-03-05 10:55:05:089 1212 6cc Misc WARNING: WinHttp:
ShouldFileBeDownloaded failed with 0x80190194
2008-03-05 10:55:05:089 1212 6cc Misc WARNING: DownloadFileInternal
failed for http://BETA/selfupdate/wuident.cab: error 0x80190194
2008-03-05 10:55:05:089 1212 6cc Setup FATAL: IsUpdateRequired failed
with error 0x80244019
2008-03-05 10:55:05:089 1212 6cc Setup WARNING: SelfUpdate: Default
Service: IsUpdateRequired failed: 0x80244019
2008-03-05 10:55:05:089 1212 6cc Setup WARNING: SelfUpdate: Default
Service: IsUpdateRequired failed, error = 0x80244019
2008-03-05 10:55:05:089 1212 6cc Agent * WARNING: Skipping scan,
self-update check returned 0x80244019
2008-03-05 10:55:05:182 1212 6cc Agent * WARNING: Exit code =
0x80244019
2008-03-05 10:55:05:182 1212 6cc Agent *********
2008-03-05 10:55:05:182 1212 6cc Agent ** END ** Agent: Finding
updates [CallerId = AutomaticUpdates]
2008-03-05 10:55:05:182 1212 6cc Agent *************
2008-03-05 10:55:05:182 1212 6cc Agent WARNING: WU client failed
Searching for update with error 0x80244019
2008-03-05 10:55:05:182 1212 14c0 AU >>## RESUMED ## AU: Search for
updates [CallId = {95912018-64B6-4360-B0F4-EC740214B26B}]
2008-03-05 10:55:05:182 1212 14c0 AU # WARNING: Search callback
failed, result = 0x80244019
2008-03-05 10:55:05:182 1212 14c0 AU # WARNING: Failed to find
updates with error code 80244019
2008-03-05 10:55:05:182 1212 14c0 AU #########
2008-03-05 10:55:05:182 1212 14c0 AU ## END ## AU: Search for
updates [CallId = {95912018-64B6-4360-B0F4-EC740214B26B}]
2008-03-05 10:55:05:182 1212 14c0 AU #############
2008-03-05 10:55:05:182 1212 14c0 AU AU setting next detection timeout
to 2008-03-05 23:55:05
2008-03-05 10:55:05:182 1212 14c0 AU Setting AU scheduled install time
to 2008-03-06 12:00:00
2008-03-05 10:55:05:214 1212 6cc Report Uploading 1 events using
cached cookie, reporting URL = http://BETA/ReportingWebService/Repo...ebService.asmx
2008-03-05 10:55:05:214 1212 6cc Report Reporter successfully uploaded
1 events.
2008-03-05 10:55:05:245 1212 6cc Report Uploading 1 events using
cached cookie, reporting URL = http://BETA/ReportingWebService/Repo...ebService.asmx
2008-03-05 10:55:05:260 1212 6cc Report Reporter successfully uploaded
1 events.
2008-03-05 10:55:10:089 1212 6cc Report REPORT EVENT: {013A919B-
B092-487C-80BD-F19CCDA4E107} 2008-03-05 10:55:05:089-0800 1 148 101
{D67661EB-2423-451D-BF5D-13199E37DF28} 0 80244019 SelfUpdate Failure
Software Synchronization Windows Update Client failed to detect with
error 0x80244019.

I found out from the first error logged at 10:55:05:089,

*********************************
1212 6cc Misc WARNING: DownloadFileInternal failed for
http://BETA/selfupdate/wuident.cab: error 0x80190194
*********************************

I believe the error is because the directory "selfupdate" does not
exsit at all, why is that and how do I resolve this?
Here is a list of sites under IIS on the WSUS server:

ApiRemoting30
ClientWebService
Content
DssAuthWebService
Inventory
ReportingWebService
ServerSynvWebService
SimpleAuthWebService
aspnet_client

achen schrieb:

> I found out from the first error logged at 10:55:05:089,
>
> *********************************
> 1212 6cc Misc WARNING: DownloadFileInternal failed for
> http://BETA/selfupdate/wuident.cab: error 0x80190194
> *********************************
>
> I believe the error is because the directory "selfupdate" does not
> exsit at all, why is that and how do I resolve this?

Do you update from WSUS 3.0 to WSUS 3.0 SP1? Try what Lawrence wrote
in Message-ID: <324593AA-53EF-451F-B1C8-F19529EF72FA@microsoft.com>
from yesterday in Thread: Self Update is not working

Winfried
--
http://www.microsoft.com/germany/win...s/default.mspx
http://www.wsuswiki.com/Home

I'm trying to gather some background information on this issue. Can you
answer the following questions:

What port is WSUS installed to (80 or 8530)?
What version did you upgrade from?
Are you using a remote or local SQL server?
Are you storing content locally?
Do you have any other applications on this server that use IIS?
Have you previously had any issues with WSUS that you fixed by making
changes to IIS or any other way not through the UI or API?

Can you attach your MSI setup log from the upgrade? The file is found under
%temp% and is called WSUSSetupmsi_*.log. There may be multiple MSI log
files, we only need the most recent one.

As for a workaround you can try what Lawrence Garvin has suggested in
another thread: Create a virtual directory called Selfupdate, allow
anonymous access to it and point it to %programfiles%\Update
Services\Selfupdate

--
Dan Albrecht
Microsoft, WSUS

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

"achen" <achen2002@yahoo.com> wrote in message
news:aab81923-2347-4b4a-a859-7a48c49c5619@e23g2000prf.googlegroups.com...
>I found out from the first error logged at 10:55:05:089,
>
> *********************************
> 1212 6cc Misc WARNING: DownloadFileInternal failed for
> http://BETA/selfupdate/wuident.cab: error 0x80190194
> *********************************
>
> I believe the error is because the directory "selfupdate" does not
> exsit at all, why is that and how do I resolve this?
> Here is a list of sites under IIS on the WSUS server:
>
> ApiRemoting30
> ClientWebService
> Content
> DssAuthWebService
> Inventory
> ReportingWebService
> ServerSynvWebService
> SimpleAuthWebService
> aspnet_client

> What port is WSUS installed to (80 or 8530)?
port 80

> What version did you upgrade from?
It isn't an upgrade, it is a brand new install of WSUS 3.0 SP1.

> Are you using a remote or local SQL server?
local which the database was installed with WSUS.

> Are you storing content locally?
yes, contents are store locally

> Do you have any other applications on this server that use IIS?
no, it was a brand new server. One thing I want to mention is that it
is a domain controller, although I don't believe it has anything to do
with this problem.

> Have you previously had any issues with WSUS that you fixed by making
> changes to IIS or any other way not through the UI or API?
The only thing I had tried, during the troubleshooting process, is to
change the port on IIS from 80 to 8530, since that didn't fix the
problem, I changed it back and I did restart the server.

> Can you attach your MSI setup log from the upgrade? *The file is found under
> %temp% and is called WSUSSetupmsi_*.log. *There may be multiple MSI log
> files, we only need the most recent one.
I searched the whole hard drive and couldn't find any trace of files
according to that file name, maybe because my installation is *not* an
upgrade?

Thanks for the info. Does this server have any antivirus type software on
it? The log file could have been deleted by the system if you TSed to the
machine to perform the install.

--
Dan Albrecht
Microsoft, WSUS

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

"achen" <achen2002@yahoo.com> wrote in message
news:5b38c8fc-a912-454b-a4b2-9c566d8a8b52@e25g2000prg.googlegroups.com...
> What port is WSUS installed to (80 or 8530)?
port 80

> What version did you upgrade from?
It isn't an upgrade, it is a brand new install of WSUS 3.0 SP1.

> Are you using a remote or local SQL server?
local which the database was installed with WSUS.

> Are you storing content locally?
yes, contents are store locally

> Do you have any other applications on this server that use IIS?
no, it was a brand new server. One thing I want to mention is that it
is a domain controller, although I don't believe it has anything to do
with this problem.

> Have you previously had any issues with WSUS that you fixed by making
> changes to IIS or any other way not through the UI or API?
The only thing I had tried, during the troubleshooting process, is to
change the port on IIS from 80 to 8530, since that didn't fix the
problem, I changed it back and I did restart the server.

> Can you attach your MSI setup log from the upgrade? The file is found
> under
> %temp% and is called WSUSSetupmsi_*.log. There may be multiple MSI log
> files, we only need the most recent one.
I searched the whole hard drive and couldn't find any trace of files
according to that file name, maybe because my installation is *not* an
upgrade?

Dan,

Thank you very much for helping me all the way through this. The WSUS
server is working after I manaully create the "selfupdate" virtual
directory. Although I still don't understnad why a manual creating
was required, I'll take this problem as resolved.