# WARNING: Failed to find updates with error code 80244010

I have a WSUS server on a 2K3 server Std SP2, currently we have @ 100 clients
reporting.
I also have Symantec Endpoint Protection management console, installed on
this server, installed on a custom site.
Today newly added clients started to get errors, and some updates are
failing.

Here is one of the client logs:

2009-06-19 13:47:29:781 1436 67c Misc =========== Logging initialized
(build: 7.1.6001.65, tz: -0400) ===========
2009-06-19 13:47:29:781 1436 67c Misc = Process:
C:\WINDOWS\System32\svchost.exe
2009-06-19 13:47:29:781 1436 67c Misc = Module:
C:\WINDOWS\System32\wuaueng.dll
2009-06-19 13:47:29:781 1436 67c Service *************
2009-06-19 13:47:29:781 1436 67c Service ** START ** Service: Service startup
2009-06-19 13:47:29:781 1436 67c Service *********
2009-06-19 13:47:29:859 1436 67c Agent * WU client version 7.1.6001.65
2009-06-19 13:47:29:859 1436 67c Agent * Base directory:
C:\WINDOWS\SoftwareDistribution
2009-06-19 13:47:29:875 1436 67c Agent * Access type: No proxy
2009-06-19 13:47:29:875 1436 67c Agent * Network state: Connected
2009-06-19 13:48:15:063 1436 67c Agent *********** Agent: Initializing
Windows Update Agent ***********
2009-06-19 13:48:15:063 1436 67c Agent *********** Agent: Initializing
global settings cache ***********
2009-06-19 13:48:15:063 1436 67c Agent * WSUS server: http://swwsus:80
2009-06-19 13:48:15:063 1436 67c Agent * WSUS status server:
http://swwsus:80
2009-06-19 13:48:15:063 1436 67c Agent * Target group: All Computers;
Computers; XP
2009-06-19 13:48:15:063 1436 67c Agent * Windows Update access disabled: No
2009-06-19 13:48:17:953 3880 860 Misc =========== Logging initialized
(build: 7.1.6001.65, tz: -0400) ===========
2009-06-19 13:48:17:953 3880 860 Misc = Process:
C:\WINDOWS\System32\wuauclt.exe
2009-06-19 13:48:17:953 3880 860 Misc = Module:
C:\WINDOWS\System32\wuaueng.dll
2009-06-19 13:48:17:953 3880 860 DtaStor Default service for AU is
{00000000-0000-0000-0000-000000000000}
2009-06-19 13:48:18:000 3880 860 DtaStor Default service for AU is
{9482F4B4-E343-43B6-B170-9A65BC822C77}
2009-06-19 13:48:18:063 1436 67c Agent WARNING: Failed to read the service
id for re-registration 0x80070002
2009-06-19 13:48:18:063 1436 67c Agent WARNING: Missing service entry in the
backup data store; cleaning up
2009-06-19 13:48:18:094 1436 67c DnldMgr Download manager restoring 0
downloads
2009-06-19 13:48:18:094 1436 67c AU ########### AU: Initializing Automatic
Updates ###########
2009-06-19 13:48:18:094 1436 67c AU # WSUS server: http://swwsus:80
2009-06-19 13:48:18:094 1436 67c AU # Detection frequency: 1
2009-06-19 13:48:18:094 1436 67c AU # Target group: All Computers;
Computers; XP
2009-06-19 13:48:18:094 1436 67c AU # Approval type: Scheduled (Policy)
2009-06-19 13:48:18:094 1436 67c AU # Scheduled install day/time: Thursday
at 12:00
2009-06-19 13:48:18:094 1436 67c AU # Auto-install minor updates: No
(Policy)
2009-06-19 13:48:18:125 1436 67c AU Setting AU scheduled install time to
2009-06-25 16:00:00
2009-06-19 13:48:18:125 1436 67c AU AU finished delayed initialization
2009-06-19 13:48:20:078 1436 67c Report *********** Report: Initializing
static reporting data ***********
2009-06-19 13:48:20:078 1436 67c Report * OS Version = 5.1.2600.1.0.65792
2009-06-19 13:48:20:109 1436 67c Report * Computer Brand = Hewlett-Packard
2009-06-19 13:48:20:109 1436 67c Report * Computer Model = HP d530
SFF(DS058A)
2009-06-19 13:48:20:109 1436 67c Report * Bios Revision = 786B2 v2.15
2009-06-19 13:48:20:109 1436 67c Report * Bios Name = 786B2 v2.15
2009-06-19 13:48:20:109 1436 67c Report * Bios Release Date =
2003-12-17T00:00:00
2009-06-19 13:48:20:109 1436 67c Report * Locale ID = 1033
2009-06-19 14:09:51:008 1436 67c AU #############
2009-06-19 14:09:51:008 1436 67c AU ## START ## AU: Search for updates
2009-06-19 14:09:51:008 1436 67c AU #########
2009-06-19 14:09:51:008 1436 67c AU <<## SUBMITTED ## AU: Search for updates
[CallId = {EA1CE9FC-A112-4864-80FB-4316F96D5926}]
2009-06-19 14:09:51:008 1436 974 Agent *************
2009-06-19 14:09:51:008 1436 974 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-06-19 14:09:51:008 1436 974 Agent *********
2009-06-19 14:09:51:008 1436 974 Agent * Online = Yes; Ignore download
priority = No
2009-06-19 14:09:51:008 1436 974 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"
2009-06-19 14:09:51:008 1436 974 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2009-06-19 14:09:57:852 1436 974 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wuident.cab:
2009-06-19 14:09:57:993 1436 974 Misc Microsoft signed: Yes
2009-06-19 14:09:58:102 1436 974 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wsus3setup.cab:
2009-06-19 14:09:58:118 1436 974 Misc Microsoft signed: Yes
2009-06-19 14:09:58:149 1436 974 Setup *********** Setup: Checking whether
self-update is required ***********
2009-06-19 14:09:58:149 1436 974 Setup * Inf file:
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wsus3setup.inf
2009-06-19 14:09:58:227 1436 974 Setup Update NOT required for
C:\WINDOWS\System32\cdm.dll: target version = 7.1.6001.65, required version =
7.1.6001.65
2009-06-19 14:09:58:227 1436 974 Setup Update NOT required for
C:\WINDOWS\System32\wuapi.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2009-06-19 14:09:58:290 1436 974 Setup Update NOT required for
C:\WINDOWS\System32\wuapi.dll.mui: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-06-19 14:09:58:290 1436 974 Setup Update NOT required for
C:\WINDOWS\System32\wuauclt.exe: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-06-19 14:09:58:290 1436 974 Setup Update NOT required for
C:\WINDOWS\System32\wuaucpl.cpl: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-06-19 14:09:58:290 1436 974 Setup Update NOT required for
C:\WINDOWS\System32\wuaucpl.cpl.mui: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-06-19 14:09:58:305 1436 974 Setup Update NOT required for
C:\WINDOWS\System32\wuaueng.dll: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-06-19 14:09:58:305 1436 974 Setup Update NOT required for
C:\WINDOWS\System32\wuaueng.dll.mui: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-06-19 14:09:58:305 1436 974 Setup Update NOT required for
C:\WINDOWS\System32\wucltui.dll: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-06-19 14:09:58:321 1436 974 Setup Update NOT required for
C:\WINDOWS\System32\wucltui.dll.mui: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-06-19 14:09:58:321 1436 974 Setup Update NOT required for
C:\WINDOWS\System32\wups.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2009-06-19 14:09:58:321 1436 974 Setup Update NOT required for
C:\WINDOWS\System32\wups2.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2009-06-19 14:09:58:352 1436 974 Setup Update NOT required for
C:\WINDOWS\System32\wuweb.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2009-06-19 14:09:58:352 1436 974 Setup * IsUpdateRequired = No
2009-06-19 14:09:59:493 1436 974 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2009-06-19 14:09:59:493 1436 974 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://swwsus:80/ClientWebService/client.asmx
2009-06-19 14:09:59:665 1436 974 PT WARNING: Cached cookie has expired or
new PID is available
2009-06-19 14:09:59:665 1436 974 PT Initializing simple targeting cookie,
clientId = 9aa4274f-53a1-46d1-b8df-b72195871bea, target group = All
Computers; Computers; XP, DNS name = cmchr14.stemc.org
2009-06-19 14:09:59:665 1436 974 PT Server URL =
http://swwsus:80/SimpleAuthWebService/SimpleAuth.asmx
2009-06-19 14:15:03:240 1436 974 PT WARNING: Exceeded max server round
trips: 0x80244010
2009-06-19 14:15:03:318 1436 974 PT WARNING: Sync of Updates: 0x80244010
2009-06-19 14:15:03:334 1436 974 PT WARNING: SyncServerUpdatesInternal
failed: 0x80244010
2009-06-19 14:15:03:475 1436 974 Agent * WARNING: Failed to synchronize,
error = 0x80244010
2009-06-19 14:15:04:693 1436 974 Agent * WARNING: Exit code = 0x80244010
2009-06-19 14:15:04:725 1436 974 Agent *********
2009-06-19 14:15:04:725 1436 974 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-06-19 14:15:04:725 1436 974 Agent *************
2009-06-19 14:15:04:725 1436 974 Agent WARNING: WU client failed Searching
for update with error 0x80244010
2009-06-19 14:15:05:256 1436 858 AU >>## RESUMED ## AU: Search for updates
[CallId = {EA1CE9FC-A112-4864-80FB-4316F96D5926}]
2009-06-19 14:15:05:256 1436 858 AU # WARNING: Search callback failed,
result = 0x80244010
2009-06-19 14:15:05:256 1436 858 AU # WARNING: Failed to find updates with
error code 80244010
2009-06-19 14:15:05:256 1436 858 AU #########
2009-06-19 14:15:05:256 1436 858 AU ## END ## AU: Search for updates
[CallId = {EA1CE9FC-A112-4864-80FB-4316F96D5926}]
2009-06-19 14:15:05:256 1436 858 AU #############
2009-06-19 14:15:05:678 1436 858 AU AU setting next detection timeout to
2009-06-19 19:03:44
2009-06-19 14:15:05:693 1436 858 AU Setting AU scheduled install time to
2009-06-25 16:00:00
2009-06-19 14:15:09:772 1436 974 Report REPORT EVENT:
{47BE8BE6-AEB3-4D55-B42C-09E868BF69B0} 2009-06-19
14:15:04:662-0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244010 AutomaticUpdates Failure Software
Synchronization Windows Update Client failed to detect with error 0x80244010.
2009-06-19 14:28:26:305 1436 974 PT WARNING: Cached cookie has expired or
new PID is available
2009-06-19 14:28:26:320 1436 974 PT Initializing simple targeting cookie,
clientId = 9aa4274f-53a1-46d1-b8df-b72195871bea, target group = All
Computers; Computers; XP, DNS name = cmchr14.stemc.org
2009-06-19 14:28:26:320 1436 974 PT Server URL =
http://swwsus:80/SimpleAuthWebService/SimpleAuth.asmx
2009-06-19 14:28:26:445 1436 974 Report Uploading 1 events using cached
cookie, reporting URL =
http://swwsus:80/ReportingWebService...ebService.asmx
2009-06-19 14:28:26:477 1436 974 Report Reporter successfully uploaded 1
events.
2009-06-19 15:03:44:633 1436 67c AU #############
2009-06-19 15:03:44:649 1436 67c AU ## START ## AU: Search for updates
2009-06-19 15:03:44:649 1436 67c AU #########
2009-06-19 15:03:44:649 1436 67c AU <<## SUBMITTED ## AU: Search for updates
[CallId = {6F3A91AD-87C1-49F2-8254-CD77CA37CDE5}]
2009-06-19 15:03:44:649 1436 684 Agent *************
2009-06-19 15:03:44:649 1436 684 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-06-19 15:03:44:649 1436 684 Agent *********
2009-06-19 15:03:44:649 1436 684 Agent * Online = Yes; Ignore download
priority = No
2009-06-19 15:03:44:649 1436 684 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"
2009-06-19 15:03:44:649 1436 684 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2009-06-19 15:03:44:695 1436 684 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wuident.cab:
2009-06-19 15:03:45:039 1436 684 Misc Microsoft signed: Yes
2009-06-19 15:03:45:055 1436 684 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wuident.cab:
2009-06-19 15:03:45:070 1436 684 Misc Microsoft signed: Yes
2009-06-19 15:03:45:242 1436 684 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wsus3setup.cab:
2009-06-19 15:03:45:258 1436 684 Misc Microsoft signed: Yes
2009-06-19 15:03:45:414 1436 684 Setup *********** Setup: Checking whether
self-update is required ***********
2009-06-19 15:03:45:414 1436 684 Setup * Inf file:
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wsus3setup.inf
2009-06-19 15:03:45:508 1436 684 Setup Update NOT required for
C:\WINDOWS\System32\cdm.dll: target version = 7.1.6001.65, required version =
7.1.6001.65
2009-06-19 15:03:45:539 1436 684 Setup Update NOT required for
C:\WINDOWS\System32\wuapi.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2009-06-19 15:03:45:586 1436 684 Setup Update NOT required for
C:\WINDOWS\System32\wuapi.dll.mui: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-06-19 15:03:45:602 1436 684 Setup Update NOT required for
C:\WINDOWS\System32\wuauclt.exe: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-06-19 15:03:45:633 1436 684 Setup Update NOT required for
C:\WINDOWS\System32\wuaucpl.cpl: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-06-19 15:03:45:633 1436 684 Setup Update NOT required for
C:\WINDOWS\System32\wuaucpl.cpl.mui: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-06-19 15:03:45:664 1436 684 Setup Update NOT required for
C:\WINDOWS\System32\wuaueng.dll: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-06-19 15:03:45:664 1436 684 Setup Update NOT required for
C:\WINDOWS\System32\wuaueng.dll.mui: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-06-19 15:03:45:680 1436 684 Setup Update NOT required for
C:\WINDOWS\System32\wucltui.dll: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-06-19 15:03:45:695 1436 684 Setup Update NOT required for
C:\WINDOWS\System32\wucltui.dll.mui: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-06-19 15:03:45:695 1436 684 Setup Update NOT required for
C:\WINDOWS\System32\wups.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2009-06-19 15:03:45:695 1436 684 Setup Update NOT required for
C:\WINDOWS\System32\wups2.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2009-06-19 15:03:45:727 1436 684 Setup Update NOT required for
C:\WINDOWS\System32\wuweb.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2009-06-19 15:03:45:727 1436 684 Setup * IsUpdateRequired = No
2009-06-19 15:03:50:680 1436 684 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2009-06-19 15:03:50:680 1436 684 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://swwsus:80/ClientWebService/client.asmx

"Jason" <> wrote in message
news:BE526B69-2CA5-4EC6-A9E1-...

>I have a WSUS server on a 2K3 server Std SP2, currently we have @ 100
>clients
> reporting.
> I also have Symantec Endpoint Protection management console, installed on
> this server, installed on a custom site.
> Today newly added clients started to get errors, and some updates are
> failing.

Two configuration errors pop to my eyes immediately:

> 2009-06-19 13:48:15:063 1436 67c Agent * WSUS server: http://swwsus:80
> 2009-06-19 13:48:15:063 1436 67c Agent * WSUS status server:
> http://swwsus:80

Drop the port number from the URL. The URL should simply be http://swwsus

> 2009-06-19 13:48:15:063 1436 67c Agent * Target group: All Computers;
> Computers; XP

You *CANNOT* assign "All Computers" as a target group. Computers will be
automatically included in "All Computers". It's a pseudo-group populated by
the rollup of all computers in the database. Please remove all
configurations assigning group membership to "All Computers".

> 2009-06-19 13:48:20:078 1436 67c Report * OS Version =
> 5.1.2600.1.0.65792

This machine is still running Windows XP =Service Pack 1= ??!??!??!

> 2009-06-19 14:09:59:665 1436 974 PT Server URL =
> http://swwsus:80/SimpleAuthWebService/SimpleAuth.asmx
> 2009-06-19 14:15:03:240 1436 974 PT WARNING: Exceeded max server round
> trips: 0x80244010

The client and server are having issues communicating. Could be because of
the port 80 suffix; could be because of the "All Computers" membership
assignment; could be because WUA v7.1 has likely not been regression tested
on Windows XP Service Pack 1, since XPSP1 was a non-supported platform when
the WUA v7.1 was released with WSUS v3.

Suggest, in addition to fixing the two configuration issues, that you
*IMMEDIATELY* install XP Service Pack 2 or XP Service Pack 3 to this system.

Then, with a properly configured client on a supported OS platform, we can
reliably troubleshoot the 0x80244010 error, if it still exists.

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Lawrence,
Thanks for the info, However I am having trouble with all my clients
regardless of the service pack installed. Prior to yesterday all clients were
reporting w/out any issues. I have only had the issue with this since I
installed SEP v11. I initially installed it on the default web site in IIS.
Coul this be the issue, and if so should I re-install WSUS, because of a
possible corruption of my IIS site?

"Lawrence Garvin [MVP]" wrote:

> "Jason" <> wrote in message
> news:BE526B69-2CA5-4EC6-A9E1-...
>
> >I have a WSUS server on a 2K3 server Std SP2, currently we have @ 100
> >clients
> > reporting.
> > I also have Symantec Endpoint Protection management console, installed on
> > this server, installed on a custom site.
> > Today newly added clients started to get errors, and some updates are
> > failing.
>
> Two configuration errors pop to my eyes immediately:
>
> > 2009-06-19 13:48:15:063 1436 67c Agent * WSUS server: http://swwsus:80
> > 2009-06-19 13:48:15:063 1436 67c Agent * WSUS status server:
> > http://swwsus:80
>
> Drop the port number from the URL. The URL should simply be http://swwsus
>
> > 2009-06-19 13:48:15:063 1436 67c Agent * Target group: All Computers;
> > Computers; XP
>
> You *CANNOT* assign "All Computers" as a target group. Computers will be
> automatically included in "All Computers". It's a pseudo-group populated by
> the rollup of all computers in the database. Please remove all
> configurations assigning group membership to "All Computers".
>
> > 2009-06-19 13:48:20:078 1436 67c Report * OS Version =
> > 5.1.2600.1.0.65792
>
> This machine is still running Windows XP =Service Pack 1= ??!??!??!
>
> > 2009-06-19 14:09:59:665 1436 974 PT Server URL =
> > http://swwsus:80/SimpleAuthWebService/SimpleAuth.asmx
> > 2009-06-19 14:15:03:240 1436 974 PT WARNING: Exceeded max server round
> > trips: 0x80244010
>
> The client and server are having issues communicating. Could be because of
> the port 80 suffix; could be because of the "All Computers" membership
> assignment; could be because WUA v7.1 has likely not been regression tested
> on Windows XP Service Pack 1, since XPSP1 was a non-supported platform when
> the WUA v7.1 was released with WSUS v3.
>
> Suggest, in addition to fixing the two configuration issues, that you
> *IMMEDIATELY* install XP Service Pack 2 or XP Service Pack 3 to this system.
>
> Then, with a properly configured client on a supported OS platform, we can
> reliably troubleshoot the 0x80244010 error, if it still exists.
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My Websites: http://www.onsitechsolutions.com;
> http://wsusinfo.onsitechsolutions.com
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>
>

In regards to the issue with the port 80, I thought that this is an
alternative and accepted method, via GP.

Please correct me if I am incorrect.

"Jason" wrote:

> Lawrence,
> Thanks for the info, However I am having trouble with all my clients
> regardless of the service pack installed. Prior to yesterday all clients were
> reporting w/out any issues. I have only had the issue with this since I
> installed SEP v11. I initially installed it on the default web site in IIS.
> Coul this be the issue, and if so should I re-install WSUS, because of a
> possible corruption of my IIS site?
>
> "Lawrence Garvin [MVP]" wrote:
>
> > "Jason" <> wrote in message
> > news:BE526B69-2CA5-4EC6-A9E1-...
> >
> > >I have a WSUS server on a 2K3 server Std SP2, currently we have @ 100
> > >clients
> > > reporting.
> > > I also have Symantec Endpoint Protection management console, installed on
> > > this server, installed on a custom site.
> > > Today newly added clients started to get errors, and some updates are
> > > failing.
> >
> > Two configuration errors pop to my eyes immediately:
> >
> > > 2009-06-19 13:48:15:063 1436 67c Agent * WSUS server: http://swwsus:80
> > > 2009-06-19 13:48:15:063 1436 67c Agent * WSUS status server:
> > > http://swwsus:80
> >
> > Drop the port number from the URL. The URL should simply be http://swwsus
> >
> > > 2009-06-19 13:48:15:063 1436 67c Agent * Target group: All Computers;
> > > Computers; XP
> >
> > You *CANNOT* assign "All Computers" as a target group. Computers will be
> > automatically included in "All Computers". It's a pseudo-group populated by
> > the rollup of all computers in the database. Please remove all
> > configurations assigning group membership to "All Computers".
> >
> > > 2009-06-19 13:48:20:078 1436 67c Report * OS Version =
> > > 5.1.2600.1.0.65792
> >
> > This machine is still running Windows XP =Service Pack 1= ??!??!??!
> >
> > > 2009-06-19 14:09:59:665 1436 974 PT Server URL =
> > > http://swwsus:80/SimpleAuthWebService/SimpleAuth.asmx
> > > 2009-06-19 14:15:03:240 1436 974 PT WARNING: Exceeded max server round
> > > trips: 0x80244010
> >
> > The client and server are having issues communicating. Could be because of
> > the port 80 suffix; could be because of the "All Computers" membership
> > assignment; could be because WUA v7.1 has likely not been regression tested
> > on Windows XP Service Pack 1, since XPSP1 was a non-supported platform when
> > the WUA v7.1 was released with WSUS v3.
> >
> > Suggest, in addition to fixing the two configuration issues, that you
> > *IMMEDIATELY* install XP Service Pack 2 or XP Service Pack 3 to this system.
> >
> > Then, with a properly configured client on a supported OS platform, we can
> > reliably troubleshoot the 0x80244010 error, if it still exists.
> >
> > --
> > Lawrence Garvin, M.S., MCITP:EA, MCDBA
> > Principal/CTO, Onsite Technology Solutions, Houston, Texas
> > Microsoft MVP - Software Distribution (2005-2009)
> >
> > MS WSUS Website: http://www.microsoft.com/wsus
> > My Websites: http://www.onsitechsolutions.com;
> > http://wsusinfo.onsitechsolutions.com
> > My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
> >
> >

"Jason" <> wrote in message
news1F34576-4D2B-4970-BCA9-...
> Lawrence,
> Thanks for the info, However I am having trouble with all my clients
> regardless of the service pack installed.

Okay, then, for the sake of argument, let's do diagnosis from an XP SP2
system. :-)

> Prior to yesterday all clients were
> reporting w/out any issues. I have only had the issue with this since I
> installed SEP v11. I initially installed it on the default web site in
> IIS.
> Coul this be the issue, and if so should I re-install WSUS, because of a
> possible corruption of my IIS site?

Well, yeah.. if you initially installed SEP on the Default Web Site, and
then uninstalled it and installed it to port 81, there well could be
remnants of SEP messing up the functionality on the Default Web Site.

I would suggest reviewing the WSUS Operations Guide and confirming all of
the resources and permissions that are needed to support WSUS are set
correctly. Alternatively, you could just uninstall/reinstall -- but make
sure you've fully cleaned up the SEP on the Default Web Site first, or WSUS
may see the remnants and force the installation to the port 8530 website.


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

"Jason" <> wrote in message
news:873C22AE-5215-40DF-9C28-...
>
> In regards to the issue with the port 80, I thought that this is an
> alternative and accepted method, via GP.

Well, according to the HTTP protocol standards, appending the :80 to the URL
should not have any impact, and is an optional value; however, in reality, I
have seen this cause issues, so I generally recommend removing the
unnecessary port designation.


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Lawrence ,
I have corrected the settings as you had suggested in the GP. Port and
client side targeting.

Here is the log from a XP pro SP2 client:


2009-06-19 22:40:51:187 1412 1050 Misc =========== Logging initialized
(build: 7.2.6001.788, tz: -0400) ===========
2009-06-19 22:40:51:187 1412 1050 Misc = Process:
C:\WINDOWS\System32\svchost.exe
2009-06-19 22:40:51:187 1412 1050 Misc = Module:
C:\WINDOWS\system32\wuaueng.dll
2009-06-19 22:40:51:187 1412 1050 Service *************
2009-06-19 22:40:51:187 1412 1050 Service ** START ** Service: Service
startup
2009-06-19 22:40:51:187 1412 1050 Service *********
2009-06-19 22:40:51:187 1412 1050 Agent * WU client version 7.2.6001.788
2009-06-19 22:40:51:187 1412 1050 Agent * Base directory:
C:\WINDOWS\SoftwareDistribution
2009-06-19 22:40:51:187 1412 1050 Agent * Access type: No proxy
2009-06-19 22:40:51:187 1412 1050 Agent * Network state: Connected
2009-06-19 22:41:36:250 1412 1050 Agent *********** Agent: Initializing
Windows Update Agent ***********
2009-06-19 22:41:36:250 1412 1050 Agent *********** Agent: Initializing
global settings cache ***********
2009-06-19 22:41:36:250 1412 1050 Agent * WSUS server: http://swwsus
2009-06-19 22:41:36:250 1412 1050 Agent * WSUS status server: http://swwsus
2009-06-19 22:41:36:250 1412 1050 Agent * Target group: Computers; IT
2009-06-19 22:41:36:250 1412 1050 Agent * Windows Update access disabled: No
2009-06-19 22:41:39:890 5292 76c Misc =========== Logging initialized
(build: 7.2.6001.788, tz: -0400) ===========
2009-06-19 22:41:39:890 5292 76c Misc = Process:
C:\WINDOWS\system32\wuauclt.exe
2009-06-19 22:41:39:890 5292 76c Misc = Module:
C:\WINDOWS\system32\wuaueng.dll
2009-06-19 22:41:39:890 5292 76c DtaStor Default service for AU is
{00000000-0000-0000-0000-000000000000}
2009-06-19 22:41:39:984 5292 76c DtaStor Default service for AU is
{9482F4B4-E343-43B6-B170-9A65BC822C77}
2009-06-19 22:41:40:046 1412 1050 Agent WARNING: failed to access the auth
cab, fatal error 0x80070003
2009-06-19 22:41:40:062 1412 1050 Agent WARNING: Invalid service in the
backup data store; cleaning up
2009-06-19 22:41:40:062 1412 1050 Agent WARNING: Failed to add and register
service 7971f918-a847-4430-9279-4a52d1efe18d to the data store 0x80240031
2009-06-19 22:41:40:203 1412 1050 DnldMgr Download manager restoring 0
downloads
2009-06-19 22:41:40:218 1412 1050 AU ########### AU: Initializing Automatic
Updates ###########
2009-06-19 22:41:40:218 1412 1050 AU AU setting next detection timeout to
2009-06-20 02:41:40
2009-06-19 22:41:40:218 1412 1050 AU # WSUS server: http://swwsus
2009-06-19 22:41:40:218 1412 1050 AU # Detection frequency: 12
2009-06-19 22:41:40:218 1412 1050 AU # Target group: Computers; IT
2009-06-19 22:41:40:218 1412 1050 AU # Approval type: Scheduled (Policy)
2009-06-19 22:41:40:218 1412 1050 AU # Scheduled install day/time: Monday
at 12:00
2009-06-19 22:41:40:218 1412 1050 AU # Auto-install minor updates: Yes
(Policy)
2009-06-19 22:41:40:250 1412 1050 AU Setting AU scheduled install time to
2009-06-22 16:00:00
2009-06-19 22:41:40:250 1412 1050 AU AU finished delayed initialization
2009-06-19 22:41:41:546 1412 1050 Report *********** Report: Initializing
static reporting data ***********
2009-06-19 22:41:41:546 1412 1050 Report * OS Version = 5.1.2600.2.0.65792
2009-06-19 22:41:41:578 1412 1050 Report * Computer Brand = Hewlett-Packard
2009-06-19 22:41:41:578 1412 1050 Report * Computer Model = HP Compaq
dc5800 Microtower
2009-06-19 22:41:41:578 1412 1050 Report * Bios Revision = 786F2 v01.04
2009-06-19 22:41:41:578 1412 1050 Report * Bios Name = Default System BIOS
2009-06-19 22:41:41:578 1412 1050 Report * Bios Release Date =
2008-01-31T00:00:00
2009-06-19 22:41:41:578 1412 1050 Report * Locale ID = 1033
2009-06-19 22:41:41:609 1412 1050 AU #############
2009-06-19 22:41:41:609 1412 1050 AU ## START ## AU: Search for updates
2009-06-19 22:41:41:609 1412 1050 AU #########
2009-06-19 22:41:41:609 1412 1050 AU <<## SUBMITTED ## AU: Search for
updates [CallId = {0E38B11C-0BD8-4372-9080-FCA3B299380F}]
2009-06-19 22:41:41:625 1412 1624 Agent *************
2009-06-19 22:41:41:625 1412 1624 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-06-19 22:41:41:625 1412 1624 Agent *********
2009-06-19 22:41:41:625 1412 1624 Agent * Online = Yes; Ignore download
priority = No
2009-06-19 22:41:41:625 1412 1624 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"
2009-06-19 22:41:41:625 1412 1624 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2009-06-19 22:41:41:625 1412 1624 Agent * Search Scope = {Machine}
2009-06-19 22:41:43:906 1412 1624 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wuident.cab:
2009-06-19 22:41:43:906 1412 1624 Misc Microsoft signed: Yes
2009-06-19 22:41:43:921 1412 1624 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wsus3setup.cab:
2009-06-19 22:41:43:921 1412 1624 Misc Microsoft signed: Yes
2009-06-19 22:41:43:921 1412 1624 Setup *********** Setup: Checking whether
self-update is required ***********
2009-06-19 22:41:43:921 1412 1624 Setup * Inf file:
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wsus3setup.inf
2009-06-19 22:41:43:921 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 7.2.6001.788, required version
= 7.1.6001.65
2009-06-19 22:41:43:921 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-19 22:41:43:921 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-19 22:41:43:921 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-19 22:41:43:921 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-19 22:41:43:921 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-19 22:41:43:921 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-19 22:41:43:921 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-19 22:41:43:921 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-19 22:41:43:921 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-19 22:41:43:921 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 7.2.6001.788, required version
= 7.1.6001.65
2009-06-19 22:41:43:921 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-19 22:41:43:921 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-19 22:41:43:921 1412 1624 Setup WARNING: Warning: Setup callback
ReportProgress failed: 0x8007000d
2009-06-19 22:41:43:921 1412 1624 Setup * IsUpdateRequired = No
2009-06-19 22:41:44:015 1412 1624 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2009-06-19 22:41:44:015 1412 1624 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://swwsus/ClientWebService/client.asmx
2009-06-19 22:41:44:031 1412 1624 PT WARNING: Cached cookie has expired or
new PID is available
2009-06-19 22:41:44:031 1412 1624 PT Initializing simple targeting cookie,
clientId = 3df10d5e-bc21-4752-9240-b7a3c34caa88, target group = Computers;
IT, DNS name = cmcitwsa.stemc.org
2009-06-19 22:41:44:031 1412 1624 PT Server URL =
http://swwsus/SimpleAuthWebService/SimpleAuth.asmx
2009-06-19 22:42:22:734 1412 1624 PT WARNING: Exceeded max server round
trips: 0x80244010
2009-06-19 22:42:22:734 1412 1624 PT WARNING: Sync of Updates: 0x80244010
2009-06-19 22:42:22:734 1412 1624 PT WARNING: SyncServerUpdatesInternal
failed: 0x80244010
2009-06-19 22:42:22:734 1412 1624 Agent * WARNING: Failed to synchronize,
error = 0x80244010
2009-06-19 22:42:22:750 1412 1624 Agent * WARNING: Exit code = 0x80244010
2009-06-19 22:42:22:750 1412 1624 Agent *********
2009-06-19 22:42:22:750 1412 1624 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-06-19 22:42:22:750 1412 1624 Agent *************
2009-06-19 22:42:22:750 1412 1624 Agent WARNING: WU client failed Searching
for update with error 0x80244010
2009-06-19 22:42:22:750 1412 7c AU >>## RESUMED ## AU: Search for updates
[CallId = {0E38B11C-0BD8-4372-9080-FCA3B299380F}]
2009-06-19 22:42:22:750 1412 7c AU # WARNING: Search callback failed,
result = 0x80244010
2009-06-19 22:42:22:750 1412 7c AU # WARNING: Failed to find updates with
error code 80244010
2009-06-19 22:42:22:750 1412 7c AU #########
2009-06-19 22:42:22:750 1412 7c AU ## END ## AU: Search for updates
[CallId = {0E38B11C-0BD8-4372-9080-FCA3B299380F}]
2009-06-19 22:42:22:750 1412 7c AU #############
2009-06-19 22:42:22:750 1412 7c AU AU setting next detection timeout to
2009-06-20 07:42:22
2009-06-19 22:42:22:750 1412 7c AU Setting AU scheduled install time to
2009-06-22 16:00:00
2009-06-19 22:42:27:750 1412 1624 Report REPORT EVENT:
{1732F0CB-C414-410D-AC7A-A7DEE58FF0A3} 2009-06-19
22:42:22:750-0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244010 AutomaticUpdates Failure Software
Synchronization Windows Update Client failed to detect with error 0x80244010.
2009-06-19 22:43:03:125 1412 e6c AU Triggering AU detection through
DetectNow API
2009-06-19 22:43:03:125 1412 e6c AU Triggering Online detection
(non-interactive)
2009-06-19 22:43:03:125 1412 1050 AU #############
2009-06-19 22:43:03:125 1412 1050 AU ## START ## AU: Search for updates
2009-06-19 22:43:03:125 1412 1050 AU #########
2009-06-19 22:43:03:125 1412 1050 AU <<## SUBMITTED ## AU: Search for
updates [CallId = {7A3C9F28-2D81-446F-9621-C8EF79E447AF}]
2009-06-19 22:43:03:125 1412 1624 Agent *************
2009-06-19 22:43:03:125 1412 1624 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-06-19 22:43:03:125 1412 1624 Agent *********
2009-06-19 22:43:03:125 1412 1624 Agent * Online = Yes; Ignore download
priority = No
2009-06-19 22:43:03:125 1412 1624 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"
2009-06-19 22:43:03:125 1412 1624 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2009-06-19 22:43:03:125 1412 1624 Agent * Search Scope = {Machine}
2009-06-19 22:43:03:125 1412 1624 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wuident.cab:
2009-06-19 22:43:03:140 1412 1624 Misc Microsoft signed: Yes
2009-06-19 22:43:03:140 1412 1624 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wuident.cab:
2009-06-19 22:43:03:140 1412 1624 Misc Microsoft signed: Yes
2009-06-19 22:43:03:140 1412 1624 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wsus3setup.cab:
2009-06-19 22:43:03:156 1412 1624 Misc Microsoft signed: Yes
2009-06-19 22:43:03:156 1412 1624 Setup *********** Setup: Checking whether
self-update is required ***********
2009-06-19 22:43:03:156 1412 1624 Setup * Inf file:
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wsus3setup.inf
2009-06-19 22:43:03:156 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 7.2.6001.788, required version
= 7.1.6001.65
2009-06-19 22:43:03:156 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-19 22:43:03:156 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-19 22:43:03:156 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-19 22:43:03:156 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-19 22:43:03:156 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-19 22:43:03:156 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-19 22:43:03:156 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-19 22:43:03:156 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-19 22:43:03:156 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-19 22:43:03:156 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 7.2.6001.788, required version
= 7.1.6001.65
2009-06-19 22:43:03:156 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-19 22:43:03:156 1412 1624 Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-19 22:43:03:156 1412 1624 Setup * IsUpdateRequired = No
2009-06-19 22:43:03:343 1412 1624 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2009-06-19 22:43:03:343 1412 1624 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://swwsus/ClientWebService/client.asmx
2009-06-19 22:43:03:437 1412 1624 PT Initializing simple targeting cookie,
clientId = 3df10d5e-bc21-4752-9240-b7a3c34caa88, target group = Computers;
IT, DNS name = cmcitwsa.stemc.org
2009-06-19 22:43:03:437 1412 1624 PT Server URL =
http://swwsus/SimpleAuthWebService/SimpleAuth.asmx
2009-06-19 22:44:47:968 1412 1624 PT +++++++++++ PT: Synchronizing extended
update info +++++++++++
2009-06-19 22:44:47:968 1412 1624 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://swwsus/ClientWebService/client.asmx
2009-06-19 22:44:49:562 1412 1624 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190194
2009-06-19 22:44:49:562 1412 1624 Misc WARNING: WinHttp:
ShouldFileBeDownloaded failed with 0x80190194
2009-06-19 22:44:49:562 1412 1624 Agent WARNING: Fail to download eula file
http://swwsus/Content/23/14D19C27B28...F6C7483623.txt with
error 0x80244019
2009-06-19 22:44:49:796 1412 1624 Agent * Found 0 updates and 50
categories in search; evaluated appl. rules of 627 out of 1235 deployed
entities
2009-06-19 22:44:49:828 1412 1624 Agent *********
2009-06-19 22:44:49:828 1412 1624 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-06-19 22:44:49:828 1412 1624 Agent *************
2009-06-19 22:44:49:828 1412 7c AU >>## RESUMED ## AU: Search for updates
[CallId = {7A3C9F28-2D81-446F-9621-C8EF79E447AF}]
2009-06-19 22:44:49:828 1412 7c AU # 0 updates detected
2009-06-19 22:44:49:828 1412 7c AU #########
2009-06-19 22:44:49:828 1412 7c AU ## END ## AU: Search for updates
[CallId = {7A3C9F28-2D81-446F-9621-C8EF79E447AF}]
2009-06-19 22:44:49:828 1412 7c AU #############
2009-06-19 22:44:49:828 1412 7c AU AU setting next detection timeout to
2009-06-20 12:39:33
2009-06-19 22:44:49:828 1412 7c AU Setting AU scheduled install time to
2009-06-22 16:00:00
2009-06-19 22:44:54:828 1412 1624 Report REPORT EVENT:
{1E070E37-F18D-492B-A002-ABB67228F925} 2009-06-19
22:44:49:828-0400 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Windows Update Client successfully detected 0 updates.
2009-06-19 22:44:54:828 1412 1624 Report REPORT EVENT:
{9A470C27-3356-4E06-95A3-D4232855EF94} 2009-06-19
22:44:49:828-0400 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.


"Lawrence Garvin [MVP]" wrote:

> "Jason" <> wrote in message
> news:BE526B69-2CA5-4EC6-A9E1-...
>
> >I have a WSUS server on a 2K3 server Std SP2, currently we have @ 100
> >clients
> > reporting.
> > I also have Symantec Endpoint Protection management console, installed on
> > this server, installed on a custom site.
> > Today newly added clients started to get errors, and some updates are
> > failing.
>
> Two configuration errors pop to my eyes immediately:
>
> > 2009-06-19 13:48:15:063 1436 67c Agent * WSUS server: http://swwsus:80
> > 2009-06-19 13:48:15:063 1436 67c Agent * WSUS status server:
> > http://swwsus:80
>
> Drop the port number from the URL. The URL should simply be http://swwsus
>
> > 2009-06-19 13:48:15:063 1436 67c Agent * Target group: All Computers;
> > Computers; XP
>
> You *CANNOT* assign "All Computers" as a target group. Computers will be
> automatically included in "All Computers". It's a pseudo-group populated by
> the rollup of all computers in the database. Please remove all
> configurations assigning group membership to "All Computers".
>
> > 2009-06-19 13:48:20:078 1436 67c Report * OS Version =
> > 5.1.2600.1.0.65792
>
> This machine is still running Windows XP =Service Pack 1= ??!??!??!
>
> > 2009-06-19 14:09:59:665 1436 974 PT Server URL =
> > http://swwsus:80/SimpleAuthWebService/SimpleAuth.asmx
> > 2009-06-19 14:15:03:240 1436 974 PT WARNING: Exceeded max server round
> > trips: 0x80244010
>
> The client and server are having issues communicating. Could be because of
> the port 80 suffix; could be because of the "All Computers" membership
> assignment; could be because WUA v7.1 has likely not been regression tested
> on Windows XP Service Pack 1, since XPSP1 was a non-supported platform when
> the WUA v7.1 was released with WSUS v3.
>
> Suggest, in addition to fixing the two configuration issues, that you
> *IMMEDIATELY* install XP Service Pack 2 or XP Service Pack 3 to this system.
>
> Then, with a properly configured client on a supported OS platform, we can
> reliably troubleshoot the 0x80244010 error, if it still exists.
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My Websites: http://www.onsitechsolutions.com;
> http://wsusinfo.onsitechsolutions.com
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>
>

Lawrence,
In the process of reinstalling now...
I will keep you up to date on my progress.
Thanks for all your help!!

"Lawrence Garvin [MVP]" wrote:

> "Jason" <> wrote in message
> news1F34576-4D2B-4970-BCA9-...
> > Lawrence,
> > Thanks for the info, However I am having trouble with all my clients
> > regardless of the service pack installed.
>
> Okay, then, for the sake of argument, let's do diagnosis from an XP SP2
> system. :-)
>
> > Prior to yesterday all clients were
> > reporting w/out any issues. I have only had the issue with this since I
> > installed SEP v11. I initially installed it on the default web site in
> > IIS.
> > Coul this be the issue, and if so should I re-install WSUS, because of a
> > possible corruption of my IIS site?
>
> Well, yeah.. if you initially installed SEP on the Default Web Site, and
> then uninstalled it and installed it to port 81, there well could be
> remnants of SEP messing up the functionality on the Default Web Site.
>
> I would suggest reviewing the WSUS Operations Guide and confirming all of
> the resources and permissions that are needed to support WSUS are set
> correctly. Alternatively, you could just uninstall/reinstall -- but make
> sure you've fully cleaned up the SEP on the Default Web Site first, or WSUS
> may see the remnants and force the installation to the port 8530 website.
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My Websites: http://www.onsitechsolutions.com;
> http://wsusinfo.onsitechsolutions.com
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>
>

Ok,
First - Thanks Lawrence for your help and direction.

Second,
This is maybe a "noob" error on my part.
I installed both SEP V11 and WSUS on the same server and had both on the
default web site in IIS. - BAD IDEA!!!! -
Eventuall I reinstalled both on thier own custom web site and then they
decided to play nicely.
Hopefully this helps out someone out there, so they dont spend a weekend
banging thier head aginst the wall!

Thanks again Lawerence.

"Lawrence Garvin [MVP]" wrote:

> "Jason" <> wrote in message
> news1F34576-4D2B-4970-BCA9-...
> > Lawrence,
> > Thanks for the info, However I am having trouble with all my clients
> > regardless of the service pack installed.
>
> Okay, then, for the sake of argument, let's do diagnosis from an XP SP2
> system. :-)
>
> > Prior to yesterday all clients were
> > reporting w/out any issues. I have only had the issue with this since I
> > installed SEP v11. I initially installed it on the default web site in
> > IIS.
> > Coul this be the issue, and if so should I re-install WSUS, because of a
> > possible corruption of my IIS site?
>
> Well, yeah.. if you initially installed SEP on the Default Web Site, and
> then uninstalled it and installed it to port 81, there well could be
> remnants of SEP messing up the functionality on the Default Web Site.
>
> I would suggest reviewing the WSUS Operations Guide and confirming all of
> the resources and permissions that are needed to support WSUS are set
> correctly. Alternatively, you could just uninstall/reinstall -- but make
> sure you've fully cleaned up the SEP on the Default Web Site first, or WSUS
> may see the remnants and force the installation to the port 8530 website.
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My Websites: http://www.onsitechsolutions.com;
> http://wsusinfo.onsitechsolutions.com
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>
>

"Jason" <> wrote in message
news:80285024-022B-4507-8753-...
> Ok,
> First - Thanks Lawrence for your help and direction.
>
> Second,
> This is maybe a "noob" error on my part.
> I installed both SEP V11 and WSUS on the same server and had both on the
> default web site in IIS. - BAD IDEA!!!! -

Actually, Jason, not a noob error.. but poor documentation on the part of
SEP. SEP, apparently, installs it's own HTTP service, which takes over port
80 -- and functionally blocks anything running on IIS. You're not the first
to be bitten by this situation.

> Eventuall I reinstalled both on thier own custom web site and then they
> decided to play nicely.

The minimum requirement in this scenario is to install SEP on the default
port 81; at which point WSUS can install and run from port 80.


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin