Re: WSUS 3 sp1 do not distribute patches to clients

Right pew, wrong church.

Forwarded to WSUS newsgroup
(microsoft.public.windows.server.update_services) via crosspost as a
convenience to OP.

On the web:
http://www.microsoft.com/communities...pdate_services

In your newsreader:
news://msnews.microsoft.com/microsof...pdate_services
--
~PAB

Christian wrote:
> After upgrading from WSUS 2 to WSUS 3 sp1 the clients no longer receive
> any
> updates from the WSUS server. Running a WSUS client diagnostic tool
> everything gets a pass except an error message at the end of the tool
> message box stating "WinHttpDownloadFileToMemory(szURLDest, Null, 0, Null,
> Null, Nul, &downloadBuffer) failed with hr=0x80190194".
>
>
> The WindowsUpdate log on the local workstations state:
>
> "Agent * Online = Yes; Ignore download priority = No
> 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"
> Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
> Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with
> 0x80190194
> Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190194
> Misc WARNING: DownloadFileInternal failed for
> http://kSERVER/selfupdate/wuident.cab: error 0x80190194
> Setup FATAL: IsUpdateRequired failed with error 0x80244019
> Setup WARNING: SelfUpdate: Default Service: IsUpdateRequired failed:
> 0x80244019
> Setup WARNING: SelfUpdate: Default Service: IsUpdateRequired failed, error
> =
> 0x80244019
> Agent * WARNING: Skipping scan, self-update check returned 0x80244019
> Agent * WARNING: Exit code = 0x80244019
>
>
> Any ideas on what might be wrong is gratefully received

"PA Bear [MS MVP]" <> wrote in message
news:...

> Christian wrote:

>> After upgrading from WSUS 2 to WSUS 3 sp1 the clients no longer receive
>> any
>> updates from the WSUS server. Running a WSUS client diagnostic tool
>> everything gets a pass except an error message at the end of the tool
>> message box stating "WinHttpDownloadFileToMemory(szURLDest, Null, 0,
>> Null,
>> Null, Nul, &downloadBuffer) failed with hr=0x80190194".

This is an HTTP '404' error on the ~/selfupdate virtual directory. This is a
common issue with the WSUS v3 SP1 upgrade. For some reason the installer
does not properly (re)create the ~/selfupdate virtual directory. (The WSUS
team is aware of this and is researching the issue.)

This is the remediation:
[1] Create a new virtual directory called 'selfupdate'. Set the pathname to
%programfiles%\Update Services\selfupdate.
[2] Enable Anonymous Access on the 'selfupdate' virtual directory.

--
Lawrence Garvin, M.S., MCITP, MCBMSP, MCTS(x4), MCP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)

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

I have got the same problem but I have got the selfupdate dir already. I will
post the log

"Lawrence Garvin [MVP]" wrote:

> "PA Bear [MS MVP]" <> wrote in message
> news:...
>
> > Christian wrote:
>
> >> After upgrading from WSUS 2 to WSUS 3 sp1 the clients no longer receive
> >> any
> >> updates from the WSUS server. Running a WSUS client diagnostic tool
> >> everything gets a pass except an error message at the end of the tool
> >> message box stating "WinHttpDownloadFileToMemory(szURLDest, Null, 0,
> >> Null,
> >> Null, Nul, &downloadBuffer) failed with hr=0x80190194".
>
> This is an HTTP '404' error on the ~/selfupdate virtual directory. This is a
> common issue with the WSUS v3 SP1 upgrade. For some reason the installer
> does not properly (re)create the ~/selfupdate virtual directory. (The WSUS
> team is aware of this and is researching the issue.)
>
> This is the remediation:
> [1] Create a new virtual directory called 'selfupdate'. Set the pathname to
> %programfiles%\Update Services\selfupdate.
> [2] Enable Anonymous Access on the 'selfupdate' virtual directory.
>
> --
> Lawrence Garvin, M.S., MCITP, MCBMSP, MCTS(x4), MCP
> Senior Data Architect, APQC, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2008)
>
> 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
>

"IXTECH" <> wrote in message
news:FF27CC90-8789-4531-A1AF-...

>I have got the same problem but I have got the selfupdate dir already.

Then you don't have the same problem. :-)

Please start a new thread with YOUR problem.



--
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 MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

"Lawrence Garvin [MVP]" wrote:

> "IXTECH" <> wrote in message
> news:FF27CC90-8789-4531-A1AF-...
>
> >I have got the same problem but I have got the selfupdate dir already.
>
> Then you don't have the same problem. :-)
>
> Please start a new thread with YOUR problem.
>
>
>
> --
> 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 MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>
>