Re: WSUS

wrote:

> On the clients, running clientdiag.exe results in nothing unusual. All
> results are PASS or NONE.

Please post the actual output.

> The WindowsUpdate.log file on the clients seem to suggest difficulty
> with a cached cookie (? I guess) called hr= 0x80244017.

This is an access denied error. It might be worth checking the IIS logs to see
if they provide more information.

Harry.

>
> The last 4 lines...
>
> GetConfig: 0x80244017
> PT: Cannot recover from fault, origin=GetConfig, hr=0x80244017
> Failed to obtain cached cookie with hr = 80244017
> Failed to upload events with hr = 80244017
>
> Elsewhere in the log there are calls for this same referenced item...
> such as:
>
> Sync of updates: 0x80244017
> WU client failed searching for update with error 0x80244017
> Search Callback Failed, hr is 0x80244017
>
> Communication does seem to be taking place between the client and
> server.
>
> In the ReportingEvents.log entries are:
>
> 0 - Automaticupdates - Success Pre-deployment checks - Reporting
> client status
> 80244017 - Selfupdate - Failure Software synchronization - Error:
> Agent failed detecting with reason: 0x80244017
> 80244017 - Automaticupdates - Failure Synchronization - Error: Agent
> failed detecting with reason: 0x80244017
> 0 - Automaticupdates - Success Pre-Deployment checks - Reporting
> client status
>
> These errors repeat, some with 800710dd or 80072efd instead of
> 80244017.
>
> Setting were done following the guidance provided by microsoft for
> setting it up on a disconnected server. Settings and updates were
> copied from a server on a parallel network, metadata imported
> successfully using wsusutil.exe. Updates do appear to be seen...
> clients do not...
>
> Any suggestions?

<> wrote in message
news:4b7c583a-dc37-4ea8-8351-...
On Sep 23, 3:22 pm, "Harry Johnston [MVP]" <ha...@scms.waikato.ac.nz>
wrote:
> garrettfi...@gmail.com wrote:
> > On the clients, running clientdiag.exe results in nothing unusual. All
> > results are PASS or NONE.
>
> Please post the actual output.

> > The last 4 lines...

<sigh>. . . and even those four lines have the timestamps removed.

Please understand, the log entries you've provided are all but useless taken
out of context like they have been.

It's why we wouldn't speculate on your issue from your original post.

*DETAILS* are critical to making intelligent, educated analyses of problems
and possible solutions.


However -- in this case, we might be lucky -- here's an *obvious* problem
that's easily traceable from this single data point:

> Wuaueng.dll version 5.4.3790.5512. . . . . . . . . . . . PASS

This is the build of the WUAgent that shipped with XP Service Pack 3. It's
severely problematic, and generally, the only way this build could be
present is if the machine had never been previously patched, or even
connected to WU/MU/WSUS; if it had, XP SP3 would not have installed this
build, and there is no other way to get this build of the WUAgent, except
from XP SP3.

Therefore, based on this one data point, the most likely cause here is the
issue documented in KB956708.

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

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin