WSUS Client not yet reported

From: "Corey" <czinn@xxxxxxxxxxxx>
Date: Tue, 4 Sep 2007 17:06:57 -0400

I had a previous issue with WSUS which was resolved, and I continued the
thread with a new issue, which probably wasn't a good idea. So I'm starting
a new thread for this issue.

I have a SBS2003 set up with WSUS. Right now, I only have one client pc (XP
Pro SP 2). It is showing up correctly in WSUS. However, it says "This
computer has not reported status yet." I have checked the WindowsUpdate.log
on the client, which has the following (I replaced the actual server name
with "wsusserver' in the following log info):

2007-09-04 16:44:24:478 1772 7a4 AU #############
2007-09-04 16:44:24:478 1772 7a4 AU ## START ## AU: Search for updates
2007-09-04 16:44:24:478 1772 7a4 AU #########
2007-09-04 16:44:24:488 1772 7a4 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {A55F5062-D8F3-4C3A-ACF8-2F575CC7A0CE}]
2007-09-04 16:44:24:488 1772 76c Agent *************
2007-09-04 16:44:24:488 1772 76c Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2007-09-04 16:44:24:488 1772 76c Agent *********
2007-09-04 16:44:24:488 1772 76c Agent * Online = Yes; Ignore download
priority = No
2007-09-04 16:44:24:488 1772 76c 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"
2007-09-04 16:44:24:488 1772 76c Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2007-09-04 16:44:24:498 1772 76c Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190191
2007-09-04 16:44:24:498 1772 76c Misc WARNING: WinHttp:
ShouldFileBeDownloaded failed with 0x80190191
2007-09-04 16:44:24:508 1772 76c Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190191
2007-09-04 16:44:24:508 1772 76c Misc WARNING: WinHttp:
ShouldFileBeDownloaded failed with 0x80190191
2007-09-04 16:44:24:518 1772 76c Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190191
2007-09-04 16:44:24:518 1772 76c Misc WARNING: WinHttp:
ShouldFileBeDownloaded failed with 0x80190191
2007-09-04 16:44:24:548 1772 76c Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190191
2007-09-04 16:44:24:548 1772 76c Misc WARNING: WinHttp:
ShouldFileBeDownloaded failed with 0x80190191
2007-09-04 16:44:24:548 1772 76c Misc WARNING: DownloadFileInternal failed
for http://wsusserver:8530/selfupdate/wuident.cab: error 0x80190191
2007-09-04 16:44:24:548 1772 76c Setup FATAL: IsUpdateRequired failed with
error 0x80244017
2007-09-04 16:44:24:548 1772 76c Setup WARNING: SelfUpdate: Default Service:
IsUpdateRequired failed: 0x80244017
2007-09-04 16:44:24:548 1772 76c Setup WARNING: SelfUpdate: Default Service:
IsUpdateRequired failed, error = 0x80244017
2007-09-04 16:44:24:548 1772 76c Agent * WARNING: Skipping scan,
self-update check returned 0x80244017
2007-09-04 16:44:25:964 1772 76c Agent * WARNING: Exit code = 0x80244017
2007-09-04 16:44:25:964 1772 76c Agent *********
2007-09-04 16:44:25:964 1772 76c Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2007-09-04 16:44:25:964 1772 76c Agent *************
2007-09-04 16:44:25:964 1772 76c Agent WARNING: WU client failed Searching
for update with error 0x80244017
2007-09-04 16:44:25:964 1772 fa0 AU >>## RESUMED ## AU: Search for updates
[CallId = {A55F5062-D8F3-4C3A-ACF8-2F575CC7A0CE}]
2007-09-04 16:44:25:964 1772 fa0 AU # WARNING: Search callback failed,
result = 0x80244017
2007-09-04 16:44:25:964 1772 fa0 AU # WARNING: Failed to find updates with
error code 80244017
2007-09-04 16:44:25:964 1772 fa0 AU #########
2007-09-04 16:44:25:964 1772 fa0 AU ## END ## AU: Search for updates
[CallId = {A55F5062-D8F3-4C3A-ACF8-2F575CC7A0CE}]
2007-09-04 16:44:25:964 1772 fa0 AU #############
2007-09-04 16:44:25:964 1772 fa0 AU AU setting next detection timeout to
2007-09-04 21:42:41
2007-09-04 16:44:29:558 1772 76c Report REPORT EVENT:
{B1E8FC8D-ABB6-4361-AFD2-17C959716697} 2007-09-04 16:44:24:548-0400 1 148
101 {D67661EB-2423-451D-BF5D-13199E37DF28} 0 80244017 SelfUpdate Failure
Software Synchronization Windows Update Client failed to detect with error
0x80244017.
2007-09-04 16:51:42:400 1772 76c PT WARNING: Cached cookie has expired or
new PID is available
2007-09-04 16:51:42:400 1772 76c PT Initializing simple targeting cookie,
clientId = c970b7b1-a859-49c5-b930-a6a758067ede, target group = Computers,
DNS name = coreylaptop.makromed.local
2007-09-04 16:51:42:400 1772 76c PT Server URL =
http://wsusserver:8530/SimpleAuthWebService/SimpleAuth.asmx
2007-09-04 16:51:42:500 1772 76c Report Uploading 1 events using cached
cookie, reporting URL =
http://wsusserver:8530/ReportingWebService/ReportingWebService.asmx
2007-09-04 16:51:42:510 1772 76c Report Reporter successfully uploaded 1
events.

I have searched this issue, and have tried several things to no avail:
- I have typed in a browser window the path to wuident.cab, and successfully
got the download box, so it's not a rights issue there.
- I verified that the WSUS Administration object in IIS has anonymous access
checked (as does the Selfupdate object under WSUS).
- I have completely disabled the firewall on the client pc.
- I have verified that the pc is not using a proxy (proxycfg yields "direct
access").

Any other thoughts/suggestions? This is a new server that I'm setting up and
will be deploying soon.

Thanks!

-Corey

.

Follow-Ups:
- RE: WSUS Client not yet reported
  - From: Manfred Zhuang [MSFT]

Prev by Date: Re: SBS 2003 - NTbackup Error
Next by Date: Re: Remote Web Workplace---ISP concerns?
Previous by thread: Re: Remote Web Workplace---ISP concerns?
Next by thread: RE: WSUS Client not yet reported
Index(es):
- Date
- Thread

Relevant Pages

Re: WSUS Client not yet reported
... I understand that a client workstation is always in "not ... The root cause can be at either the server side or the client side. ... please check if it works with WSUS. ...
(microsoft.public.windows.server.sbs)
Re: Computer not signed for WSUS
... One of the client computer cannot be detected by the WSUS. ... Microsoft CSS Online Newsgroup Support ...
(microsoft.public.windows.server.sbs)
Re: WSUS Client not yet reported
... Client cannot get updates from WSUS. ... Checked IP restriction setting of WSUS Administration ... Microsoft Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
(microsoft.public.windows.server.sbs)
Re: WSUS Client not yet reported
... The root cause can be at either the server side or the client side. ... please check if it works with WSUS. ... any updates in your thread. ...
(microsoft.public.windows.server.sbs)
Re: How-to Uninstall WSUS
... the WSUS Administration web site. ... I will repost in server.update_services and see if Lawrence picks it up. ... client log, server debug log, windows update log, server config, isa2004, ... Never met a client that realistically expected me to have all the ...
(microsoft.public.windows.server.sbs)