Hello all,

I installed WSUS in a custom port - 8530 as I have other software using port
80 in IIS. I imported my clients from AD into their proper groups in WSUS,
from a prompt where WSUS is installed I type --- wuauclt.exe /detectnow.

Below is the message I get -----

* ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-09-23 15:44:49:873 860 1450 Agent * Search Scope = {Machine}
2008-09-23 15:44:49:873 860 1450 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2008-09-23 15:44:49:873 860 1450 Misc Microsoft signed: Yes
2008-09-23 15:44:49:889 860 1450 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190194
2008-09-23 15:44:49:889 860 1450 Misc WARNING: WinHttp:
ShouldFileBeDownloaded failed with 0x80190194
2008-09-23 15:44:49:889 860 1450 Misc WARNING: DownloadFileInternal failed
for http://intranet1/selfupdate/wuident.cab: error 0x80190194
2008-09-23 15:44:49:889 860 1450 Setup FATAL: IsUpdateRequired failed with
error 0x80244019
2008-09-23 15:44:49:889 860 1450 Setup WARNING: SelfUpdate: Default
Service: IsUpdateRequired failed: 0x80244019
2008-09-23 15:44:49:889 860 1450 Setup WARNING: SelfUpdate: Default
Service: IsUpdateRequired failed, error = 0x80244019
2008-09-23 15:44:49:889 860 1450 Agent * WARNING: Skipping scan,
self-update check returned 0x80244019
2008-09-23 15:44:50:139 860 1450 Agent * WARNING: Exit code = 0x80244019


I found a document to create a new virtual directory, not in the default web
site, but I created in the WSUS site, stopped IIS, re-tried the command, and
same error.

Can someone help why my clients are not reporting to WSUS ?

Thanks,
Bob

Re: WSUS 3.0 SP1 - computers have not reported status yet by TaurArian

TaurArian
Tue Sep 23 14:19:13 PDT 2008


"Bob" <Bob@discussions.microsoft.com> wrote in message
news:853E8BB5-71C7-4BEE-9392-D75DBBF21C6B@microsoft.com...
> Hello all,
>
> I installed WSUS in a custom port - 8530 as I have other software using
> port
> 80 in IIS. I imported my clients from AD into their proper groups in WSUS,
> from a prompt where WSUS is installed I type --- wuauclt.exe /detectnow.
>
> Below is the message I get -----
>
> * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
> 2008-09-23 15:44:49:873 860 1450 Agent * Search Scope = {Machine}
> 2008-09-23 15:44:49:873 860 1450 Misc Validating signature for
> C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
> 2008-09-23 15:44:49:873 860 1450 Misc Microsoft signed: Yes
> 2008-09-23 15:44:49:889 860 1450 Misc WARNING: WinHttp:
> SendRequestToServerForFileInformation failed with 0x80190194
> 2008-09-23 15:44:49:889 860 1450 Misc WARNING: WinHttp:
> ShouldFileBeDownloaded failed with 0x80190194
> 2008-09-23 15:44:49:889 860 1450 Misc WARNING: DownloadFileInternal failed
> for http://intranet1/selfupdate/wuident.cab: error 0x80190194
> 2008-09-23 15:44:49:889 860 1450 Setup FATAL: IsUpdateRequired failed with
> error 0x80244019
> 2008-09-23 15:44:49:889 860 1450 Setup WARNING: SelfUpdate: Default
> Service: IsUpdateRequired failed: 0x80244019
> 2008-09-23 15:44:49:889 860 1450 Setup WARNING: SelfUpdate: Default
> Service: IsUpdateRequired failed, error = 0x80244019
> 2008-09-23 15:44:49:889 860 1450 Agent * WARNING: Skipping scan,
> self-update check returned 0x80244019
> 2008-09-23 15:44:50:139 860 1450 Agent * WARNING: Exit code = 0x80244019
>
>
> I found a document to create a new virtual directory, not in the default
> web
> site, but I created in the WSUS site, stopped IIS, re-tried the command,
> and
> same error.
>
> Can someone help why my clients are not reporting to WSUS ?
>
> Thanks,
> Bob
>
>

Perhaps try the WSUS Newsgroup

On the web:
http://www.microsoft.com/communities/newsgroups/list/en-us/default.aspx?dg=microsoft.public.windows.server.update_services

In your newsreader:
news://msnews.microsoft.com/microsoft.public.windows.server.update_services

Xposted for convenience



Re: WSUS 3.0 SP1 - computers have not reported status yet by Harry

Harry
Tue Sep 23 16:22:09 PDT 2008

"Bob" <Bob@discussions.microsoft.com> wrote in message
news:853E8BB5-71C7-4BEE-9392-D75DBBF21C6B@microsoft.com...

> I installed WSUS in a custom port - 8530 as I have other software using port 80 in IIS.

You haven't told your clients this:

>> 2008-09-23 15:44:49:889 860 1450 Misc WARNING: DownloadFileInternal failed
>> for http://intranet1/selfupdate/wuident.cab: error 0x80190194

Note http://intranet1, not http://intranet1:8530.

If you used group policy to assign the clients to WSUS, you need to update it
accordingly.

Harry.

Re: WSUS 3.0 SP1 - computers have not reported status yet by Bob

Bob
Wed Sep 24 07:10:02 PDT 2008



"Harry Johnston [MVP]" wrote:

> "Bob" <Bob@discussions.microsoft.com> wrote in message
> news:853E8BB5-71C7-4BEE-9392-D75DBBF21C6B@microsoft.com...
>
> > I installed WSUS in a custom port - 8530 as I have other software using port 80 in IIS.
>
> You haven't told your clients this:
>
> >> 2008-09-23 15:44:49:889 860 1450 Misc WARNING: DownloadFileInternal failed
> >> for http://intranet1/selfupdate/wuident.cab: error 0x80190194
>
> Note http://intranet1, not http://intranet1:8530.
>
> If you used group policy to assign the clients to WSUS, you need to update it
> accordingly.
>
> Harry.
>

Thanks Harry, but I don;t understand your reply --- I need to update "it"
accordingly, update what and how ? Yes I do use Group Policy nothing was
touched/changed in GP. This is a re-install of WSUS, worked before, but not
now.

Thanks,
Bob


Re: WSUS 3.0 SP1 - computers have not reported status yet by Harry

Harry
Wed Sep 24 13:26:09 PDT 2008

Bob wrote:

>> If you used group policy to assign the clients to WSUS, you need to update it
>> accordingly.

> Thanks Harry, but I don;t understand your reply --- I need to update "it"
> accordingly, update what and how ?

Your group policy currently says that clients should use http://intranet1 as the
WSUS server. You need to change this to tell them to use http://intranet1:8530.

Harry.

Re: WSUS 3.0 SP1 - computers have not reported status yet by Bob

Bob
Wed Sep 24 13:58:01 PDT 2008



"Harry Johnston [MVP]" wrote:

> Bob wrote:
>
> >> If you used group policy to assign the clients to WSUS, you need to update it
> >> accordingly.
>
> > Thanks Harry, but I don;t understand your reply --- I need to update "it"
> > accordingly, update what and how ?
>
> Your group policy currently says that clients should use http://intranet1 as the
> WSUS server. You need to change this to tell them to use http://intranet1:8530.
>
> Harry.
>

Thanks --- I got it, let me add the port and i will reply back with my result.

Bob


Re: WSUS 3.0 SP1 - computers have not reported status yet by Bob

Bob
Fri Sep 26 08:13:01 PDT 2008



"Bob" wrote:

>
>
> "Harry Johnston [MVP]" wrote:
>
> > Bob wrote:
> >
> > >> If you used group policy to assign the clients to WSUS, you need to update it
> > >> accordingly.
> >
> > > Thanks Harry, but I don;t understand your reply --- I need to update "it"
> > > accordingly, update what and how ?
> >
> > Your group policy currently says that clients should use http://intranet1 as the
> > WSUS server. You need to change this to tell them to use http://intranet1:8530.
> >
> > Harry.
> >
>
> Thanks --- I got it, let me add the port and i will reply back with my result.
>
> Bob
>

Ok --- adding the port helped. I imported 2 of 3 groups - test and servers.
The clients/servers show their IP addresses and OS versions. But i have one
problem ----

All of the systems show ---- last report status - not yet reported.

I did my last change 2 days ago - Wednesday, and it should report in daily.
I did gpupdate /force on the DC, and wuauclt.exe /detectnow but the clients
are not reporting in. I take that back ---- only my computer reported in, and
that was Wednesday. Can you let me know why computers are not reporting in ?

Thanks,
Bob


Re: WSUS 3.0 SP1 - computers have not reported status yet by Harry

Harry
Sat Sep 27 16:51:25 PDT 2008

Bob wrote:

> All of the systems show ---- last report status - not yet reported.

Let's start with the Client Diagnostics Tool:

<http://technet.microsoft.com/en-us/wsus/bb466192.aspx>

http://technet.microsoft.com/en-us/wsus/bb466192.aspx

Run it on one of the affected clients and post the results. Then type

wuauclt /detectnow

on the same client, wait thirty minutes, then post the last fifty lines from
WindowsUpdate.log.

Harry.
'

Re: WSUS 3.0 SP1 - computers have not reported status yet by Bob

Bob
Sat Sep 27 18:48:01 PDT 2008



"Harry Johnston [MVP]" wrote:

> Bob wrote:
>
> > All of the systems show ---- last report status - not yet reported.
>
> Let's start with the Client Diagnostics Tool:
>
> <http://technet.microsoft.com/en-us/wsus/bb466192.aspx>
>
> http://technet.microsoft.com/en-us/wsus/bb466192.aspx
>
> Run it on one of the affected clients and post the results. Then type
>
> wuauclt /detectnow
>
> on the same client, wait thirty minutes, then post the last fifty lines from
> WindowsUpdate.log.
>
> Harry.
> '
>

Thanks for the information Harry ----

I'm reading your reply from home, I will do this when I return to the office
Tuesday 9/30.


Bob



Re: WSUS 3.0 SP1 - computers have not reported status yet by Bob

Bob
Tue Sep 30 06:50:00 PDT 2008



"Bob" wrote:

>
>
> "Harry Johnston [MVP]" wrote:
>
> > Bob wrote:
> >
> > > All of the systems show ---- last report status - not yet reported.
> >
> > Let's start with the Client Diagnostics Tool:
> >
> > <http://technet.microsoft.com/en-us/wsus/bb466192.aspx>
> >
> > http://technet.microsoft.com/en-us/wsus/bb466192.aspx
> >
> > Run it on one of the affected clients and post the results. Then type
> >
> > wuauclt /detectnow
> >
> > on the same client, wait thirty minutes, then post the last fifty lines from
> > WindowsUpdate.log.
> >
> > Harry.
> > '
> >
>
> Thanks for the information Harry ----
>
> I'm reading your reply from home, I will do this when I return to the office
> Tuesday 9/30.
>
>
> Bob
>
>

Here is the reply of the client diagnostic tool, which I ran on my desktop.
I will now do the wuauclt/detectnow and post back in 30 minutes are requested.

thanks,
Bob



WSUS Client Diagnostics Tool

Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is running. . . PASS
Wuaueng.dll version 7.1.6001.65 . . . . . . . . . . . . PASS
This version is WSUS 2.0

Checking AU Settings
AU Option is 3 : Notify Prior to Install. . . . . . . . PASS
Option is from Policy settings

Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . NONE
Winhttp local machine ProxyBypass. . . . . . . NONE
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy. . . . . . . . . . . . . . . . . NONE
User IE ProxyByPass. . . . . . . . . . . . . . NONE
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect not in use

Checking Connection to WSUS/SUS Server
WUServer = http://intranet1:8530
WUStatusServer = http://intranet1:8530
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
Connection to server. . . . . . . . . . . . . . . . . . PASS

WinHttpDownloadFileToMemory(szURLDest, NULL, 0, NULL, NULL, NULL,
&downloadBuffe
r) failed with hr=0x80190194

No Error description could be found

Press Enter to Complete




Re: WSUS 3.0 SP1 - computers have not reported status yet by Bob

Bob
Tue Sep 30 07:25:01 PDT 2008



"Bob" wrote:

>
>
> "Bob" wrote:
>
> >
> >
> > "Harry Johnston [MVP]" wrote:
> >
> > > Bob wrote:
> > >
> > > > All of the systems show ---- last report status - not yet reported.
> > >
> > > Let's start with the Client Diagnostics Tool:
> > >
> > > <http://technet.microsoft.com/en-us/wsus/bb466192.aspx>
> > >
> > > http://technet.microsoft.com/en-us/wsus/bb466192.aspx
> > >
> > > Run it on one of the affected clients and post the results. Then type
> > >
> > > wuauclt /detectnow
> > >
> > > on the same client, wait thirty minutes, then post the last fifty lines from
> > > WindowsUpdate.log.
> > >
> > > Harry.
> > > '
> > >
> >
> > Thanks for the information Harry ----
> >
> > I'm reading your reply from home, I will do this when I return to the office
> > Tuesday 9/30.
> >
> >
> > Bob
> >
> >
>
> Here is the reply of the client diagnostic tool, which I ran on my desktop.
> I will now do the wuauclt/detectnow and post back in 30 minutes are requested.
>
> thanks,
> Bob
>
>
>
> WSUS Client Diagnostics Tool
>
> Checking Machine State
> Checking for admin rights to run tool . . . . . . . . . PASS
> Automatic Updates Service is running. . . . . . . . . . PASS
> Background Intelligent Transfer Service is running. . . PASS
> Wuaueng.dll version 7.1.6001.65 . . . . . . . . . . . . PASS
> This version is WSUS 2.0
>
> Checking AU Settings
> AU Option is 3 : Notify Prior to Install. . . . . . . . PASS
> Option is from Policy settings
>
> Checking Proxy Configuration
> Checking for winhttp local machine Proxy settings . . . PASS
> Winhttp local machine access type
> <Direct Connection>
> Winhttp local machine Proxy. . . . . . . . . . NONE
> Winhttp local machine ProxyBypass. . . . . . . NONE
> Checking User IE Proxy settings . . . . . . . . . . . . PASS
> User IE Proxy. . . . . . . . . . . . . . . . . NONE
> User IE ProxyByPass. . . . . . . . . . . . . . NONE
> User IE AutoConfig URL Proxy . . . . . . . . . NONE
> User IE AutoDetect
> AutoDetect not in use
>
> Checking Connection to WSUS/SUS Server
> WUServer = http://intranet1:8530
> WUStatusServer = http://intranet1:8530
> UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
> Connection to server. . . . . . . . . . . . . . . . . . PASS
>
> WinHttpDownloadFileToMemory(szURLDest, NULL, 0, NULL, NULL, NULL,
> &downloadBuffe
> r) failed with hr=0x80190194
>
> No Error description could be found
>
> Press Enter to Complete
>
>
> And here is the status of wuauclt also from my desktop after 30 minutes -----

Thanks,,
Bob

2008-09-30 09:55:53:011 1088 a80 AU Triggering AU detection through
DetectNow API
2008-09-30 09:55:53:026 1088 a80 AU Triggering Online detection
(non-interactive)
2008-09-30 09:55:53:026 1088 168 AU #############
2008-09-30 09:55:53:026 1088 168 AU ## START ## AU: Search for updates
2008-09-30 09:55:53:026 1088 168 AU #########
2008-09-30 09:55:53:026 1088 168 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {C8A4A428-81CE-452C-AF15-3FE465C95E3B}]
2008-09-30 09:55:53:026 1088 108c Agent *************
2008-09-30 09:55:53:026 1088 108c Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-09-30 09:55:53:026 1088 108c Agent *********
2008-09-30 09:55:53:026 1088 108c Agent * Online = Yes; Ignore download
priority = No
2008-09-30 09:55:53:026 1088 108c 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-09-30 09:55:53:026 1088 108c Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-09-30 09:55:53:026 1088 108c Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2008-09-30 09:55:53:057 1088 108c Misc Microsoft signed: Yes
2008-09-30 09:55:53:073 1088 108c Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190194
2008-09-30 09:55:53:073 1088 108c Misc WARNING: WinHttp:
ShouldFileBeDownloaded failed with 0x80190194
2008-09-30 09:55:53:073 1088 108c Misc WARNING: DownloadFileInternal failed
for http://intranet1:8530/selfupdate/wuident.cab: error 0x80190194
2008-09-30 09:55:53:073 1088 108c Setup FATAL: IsUpdateRequired failed with
error 0x80244019
2008-09-30 09:55:53:073 1088 108c Setup WARNING: SelfUpdate: Default
Service: IsUpdateRequired failed: 0x80244019
2008-09-30 09:55:53:073 1088 108c Setup WARNING: SelfUpdate: Default
Service: IsUpdateRequired failed, error = 0x80244019
2008-09-30 09:55:53:073 1088 108c Agent * WARNING: Skipping scan,
self-update check returned 0x80244019
2008-09-30 09:55:53:776 1088 108c Agent * WARNING: Exit code = 0x80244019
2008-09-30 09:55:53:776 1088 108c Agent *********
2008-09-30 09:55:53:776 1088 108c Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-09-30 09:55:53:776 1088 108c Agent *************
2008-09-30 09:55:53:776 1088 108c Agent WARNING: WU client failed Searching
for update with error 0x80244019
2008-09-30 09:55:53:776 1088 e20 AU >>## RESUMED ## AU: Search for updates
[CallId = {C8A4A428-81CE-452C-AF15-3FE465C95E3B}]
2008-09-30 09:55:53:776 1088 e20 AU # WARNING: Search callback failed,
result = 0x80244019
2008-09-30 09:55:53:776 1088 e20 AU # WARNING: Failed to find updates with
error code 80244019
2008-09-30 09:55:53:776 1088 e20 AU #########
2008-09-30 09:55:53:776 1088 e20 AU ## END ## AU: Search for updates
[CallId = {C8A4A428-81CE-452C-AF15-3FE465C95E3B}]
2008-09-30 09:55:53:776 1088 e20 AU #############
2008-09-30 09:55:53:776 1088 e20 AU AU setting next detection timeout to
2008-09-30 18:55:53
2008-09-30 09:55:58:089 1088 108c Report REPORT EVENT:
{659A3B46-515D-41B4-ACF9-8F0456335334} 2008-09-30
09:55:53:073-0400 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 0 80244019 SelfUpdate Failure Software
Synchronization Windows Update Client failed to detect with error 0x80244019.
2008-09-30 10:06:13:368 1088 108c Report Uploading 1 events using cached
cookie, reporting URL =
http://intranet1:8530/ReportingWebService/ReportingWebService.asmx
2008-09-30 10:06:13:368 1088 108c Report Reporter successfully uploaded 1
events.


Re: WSUS 3.0 SP1 - computers have not reported status yet by PA

PA
Tue Sep 30 10:33:14 PDT 2008

Bob wrote:
>> "Harry Johnston [MVP]" wrote:
>>> Bob wrote:
>>>> All of the systems show ---- last report status - not yet reported.
>>>
>>> Let's start with the Client Diagnostics Tool:
>>>
>>> <http://technet.microsoft.com/en-us/wsus/bb466192.aspx>
>>>
>>> http://technet.microsoft.com/en-us/wsus/bb466192.aspx
>>>
>>> Run it on one of the affected clients and post the results. Then type
>>>
>>> wuauclt /detectnow
>>>
>>> on the same client, wait thirty minutes, then post the last fifty lines
>>> from WindowsUpdate.log.
>>>
> Here is the reply of the client diagnostic tool, which I ran on my
> desktop.
> I will now do the wuauclt/detectnow and post back in 30 minutes are
> requested.
>
> WSUS Client Diagnostics Tool
>
> Checking Machine State
> Checking for admin rights to run tool . . . . . . . . . PASS
> Automatic Updates Service is running. . . . . . . . . . PASS
> Background Intelligent Transfer Service is running. . . PASS
> Wuaueng.dll version 7.1.6001.65 . . . . . . . . . . . . PASS
> This version is WSUS 2.0
>
> Checking AU Settings
> AU Option is 3 : Notify Prior to Install. . . . . . . . PASS
> Option is from Policy settings
>
> Checking Proxy Configuration
> Checking for winhttp local machine Proxy settings . . . PASS
> Winhttp local machine access type
> <Direct Connection>
> Winhttp local machine Proxy. . . . . . . . . . NONE
> Winhttp local machine ProxyBypass. . . . . . . NONE
> Checking User IE Proxy settings . . . . . . . . . . . . PASS
> User IE Proxy. . . . . . . . . . . . . . . . . NONE
> User IE ProxyByPass. . . . . . . . . . . . . . NONE
> User IE AutoConfig URL Proxy . . . . . . . . . NONE
> User IE AutoDetect
> AutoDetect not in use
>
> Checking Connection to WSUS/SUS Server
> WUServer = http://intranet1:8530
> WUStatusServer = http://intranet1:8530
> UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
> Connection to server. . . . . . . . . . . . . . . . . . PASS
>
> WinHttpDownloadFileToMemory(szURLDest, NULL, 0, NULL, NULL, NULL,
> &downloadBuffe
> r) failed with hr=0x80190194
>
> No Error description could be found

<kibbitz>
0x80244019 - SUS_E_PT_HTTP_STATUS_NOT_FOUND - Http status 404 - object not
found.

Random Musings of Jeremy Jameson : WSUS Clients Failing with Error
0x80244019 After Installing WSUS SP1:
http://blogs.msdn.com/jjameson/archive/2008/04/08/wsus-clients-failing-with-error-0x80244019-after-installing-wsus-sp1.aspx

Error 0x80244019 in WindowsUpdate.log - PatchAholic...The WSUS Blog!:
http://msmvps.com/blogs/athif/archive/2006/05/13/Error-0x80244019.aspx
</kibbitz>
--
~PA Bear


Re: WSUS 3.0 SP1 - computers have not reported status yet by Harry

Harry
Tue Sep 30 13:35:41 PDT 2008

Bob wrote:

> 2008-09-30 09:55:53:073 1088 108c Misc WARNING: DownloadFileInternal failed
> for http://intranet1:8530/selfupdate/wuident.cab: error 0x80190194

Hokay. See what happens if you point a web browser at that URL. I expect
you'll get a 404 error, in which case the selfupdate tree is missing. This post
may help:

<http://groups.google.com/group/microsoft.public.windows.server.update_services/msg/a73f6a5371c33478?hl=en>

http://groups.google.com/group/microsoft.public.windows.server.update_services/msg/a73f6a5371c33478?hl=en

Harry.

Re: WSUS 3.0 SP1 - computers have not reported status yet by Bob

Bob
Tue Sep 30 14:38:02 PDT 2008



"PA Bear [MS MVP]" wrote:

> Bob wrote:
> >> "Harry Johnston [MVP]" wrote:
> >>> Bob wrote:
> >>>> All of the systems show ---- last report status - not yet reported.
> >>>
> >>> Let's start with the Client Diagnostics Tool:
> >>>
> >>> <http://technet.microsoft.com/en-us/wsus/bb466192.aspx>
> >>>
> >>> http://technet.microsoft.com/en-us/wsus/bb466192.aspx
> >>>
> >>> Run it on one of the affected clients and post the results. Then type
> >>>
> >>> wuauclt /detectnow
> >>>
> >>> on the same client, wait thirty minutes, then post the last fifty lines
> >>> from WindowsUpdate.log.
> >>>
> > Here is the reply of the client diagnostic tool, which I ran on my
> > desktop.
> > I will now do the wuauclt/detectnow and post back in 30 minutes are
> > requested.
> >
> > WSUS Client Diagnostics Tool
> >
> > Checking Machine State
> > Checking for admin rights to run tool . . . . . . . . . PASS
> > Automatic Updates Service is running. . . . . . . . . . PASS
> > Background Intelligent Transfer Service is running. . . PASS
> > Wuaueng.dll version 7.1.6001.65 . . . . . . . . . . . . PASS
> > This version is WSUS 2.0
> >
> > Checking AU Settings
> > AU Option is 3 : Notify Prior to Install. . . . . . . . PASS
> > Option is from Policy settings
> >
> > Checking Proxy Configuration
> > Checking for winhttp local machine Proxy settings . . . PASS
> > Winhttp local machine access type
> > <Direct Connection>
> > Winhttp local machine Proxy. . . . . . . . . . NONE
> > Winhttp local machine ProxyBypass. . . . . . . NONE
> > Checking User IE Proxy settings . . . . . . . . . . . . PASS
> > User IE Proxy. . . . . . . . . . . . . . . . . NONE
> > User IE ProxyByPass. . . . . . . . . . . . . . NONE
> > User IE AutoConfig URL Proxy . . . . . . . . . NONE
> > User IE AutoDetect
> > AutoDetect not in use
> >
> > Checking Connection to WSUS/SUS Server
> > WUServer = http://intranet1:8530
> > WUStatusServer = http://intranet1:8530
> > UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
> > Connection to server. . . . . . . . . . . . . . . . . . PASS
> >
> > WinHttpDownloadFileToMemory(szURLDest, NULL, 0, NULL, NULL, NULL,
> > &downloadBuffe
> > r) failed with hr=0x80190194
> >
> > No Error description could be found
>
> <kibbitz>
> 0x80244019 - SUS_E_PT_HTTP_STATUS_NOT_FOUND - Http status 404 - object not
> found.
>
> Random Musings of Jeremy Jameson : WSUS Clients Failing with Error
> 0x80244019 After Installing WSUS SP1:
> http://blogs.msdn.com/jjameson/archive/2008/04/08/wsus-clients-failing-with-error-0x80244019-after-installing-wsus-sp1.aspx
>
> Error 0x80244019 in WindowsUpdate.log - PatchAholic...The WSUS Blog!:
> http://msmvps.com/blogs/athif/archive/2006/05/13/Error-0x80244019.aspx
> </kibbitz>
> --
> ~PA Bear
>
>

I did setup a new virtual directory in WSUS in IIS, called it selfupdate,
left the permission to the default - read, stopped/restarted IIS, ran wuauclt
/detectnow and still did not work. Please see the log below --

Thanks,
Bob


2008-09-30 17:15:38:525 1088 e34 AU Triggering AU detection through
DetectNow API
2008-09-30 17:15:38:525 1088 e34 AU Triggering Online detection
(non-interactive)
2008-09-30 17:15:38:525 1088 168 AU #############
2008-09-30 17:15:38:525 1088 168 AU ## START ## AU: Search for updates
2008-09-30 17:15:38:525 1088 168 AU #########
2008-09-30 17:15:38:525 1088 168 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {F4F88A9E-1B71-41E2-9DBF-4B8E5D178A04}]
2008-09-30 17:15:38:525 1088 130c Agent *************
2008-09-30 17:15:38:525 1088 130c Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-09-30 17:15:38:525 1088 130c Agent *********
2008-09-30 17:15:38:541 1088 130c Agent * Online = Yes; Ignore download
priority = No
2008-09-30 17:15:38:541 1088 130c 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-09-30 17:15:38:541 1088 130c Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-09-30 17:15:38:541 1088 130c Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2008-09-30 17:15:38:541 1088 130c Misc Microsoft signed: Yes
2008-09-30 17:15:38:556 1088 130c Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190194
2008-09-30 17:15:38:556 1088 130c Misc WARNING: WinHttp:
ShouldFileBeDownloaded failed with 0x80190194
2008-09-30 17:15:38:556 1088 130c Misc WARNING: DownloadFileInternal failed
for http://intranet1:8530/selfupdate/wuident.cab: error 0x80190194
2008-09-30 17:15:38:556 1088 130c Setup FATAL: IsUpdateRequired failed with
error 0x80244019
2008-09-30 17:15:38:556 1088 130c Setup WARNING: SelfUpdate: Default
Service: IsUpdateRequired failed: 0x80244019
2008-09-30 17:15:38:556 1088 130c Setup WARNING: SelfUpdate: Default
Service: IsUpdateRequired failed, error = 0x80244019
2008-09-30 17:15:38:556 1088 130c Agent * WARNING: Skipping scan,
self-update check returned 0x80244019
2008-09-30 17:15:39:197 1088 130c Agent * WARNING: Exit code = 0x80244019
2008-09-30 17:15:39:197 1088 130c Agent *********
2008-09-30 17:15:39:197 1088 130c Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-09-30 17:15:39:197 1088 130c Agent *************
2008-09-30 17:15:39:197 1088 130c Agent WARNING: WU client failed Searching
for update with error 0x80244019
2008-09-30 17:15:39:197 1088 107c AU >>## RESUMED ## AU: Search for
updates [CallId = {F4F88A9E-1B71-41E2-9DBF-4B8E5D178A04}]
2008-09-30 17:15:39:197 1088 107c AU # WARNING: Search callback failed,
result = 0x80244019
2008-09-30 17:15:39:197 1088 107c AU # WARNING: Failed to find updates
with error code 80244019
2008-09-30 17:15:39:197 1088 107c AU #########
2008-09-30 17:15:39:197 1088 107c AU ## END ## AU: Search for updates
[CallId = {F4F88A9E-1B71-41E2-9DBF-4B8E5D178A04}]
2008-09-30 17:15:39:197 1088 107c AU #############
2008-09-30 17:15:39:197 1088 107c AU AU setting next detection timeout to
2008-10-01 02:15:39
2008-09-30 17:15:43:556 1088 130c Report REPORT EVENT:
{37C62D47-0C99-4BEF-ABE6-9D2712BB8850} 2008-09-30
17:15:38:556-0400 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 0 80244019 SelfUpdate Failure Software
Synchronization Windows Update Client failed to detect with error 0x80244019.
2008-09-30 17:25:58:353 1088 130c PT WARNING: Cached cookie has expired or
new PID is available
2008-09-30 17:25:58:353 1088 130c PT Initializing simple targeting cookie,
clientId = 1f86fbe4-b2fd-4ab9-89d2-0b217057c785, target group = TEST, DNS
name = bobp.amalgamated.com
2008-09-30 17:25:58:353 1088 130c PT Server URL =
http://intranet1:8530/SimpleAuthWebService/SimpleAuth.asmx
2008-09-30 17:25:58:384 1088 130c Report Uploading 1 events using cached
cookie, reporting URL =
http://intranet1:8530/ReportingWebService/ReportingWebService.asmx
2008-09-30 17:25:58:384 1088 130c Report Reporter successfully uploaded 1
events.


Re: WSUS 3.0 SP1 - computers have not reported status yet by PA

PA
Tue Sep 30 15:41:34 PDT 2008

[See Harry's reply posted about an hour before you replied to my post.]

Bob wrote:
> "PA Bear [MS MVP]" wrote:
<snip>
>> <kibbitz>
>> 0x80244019 - SUS_E_PT_HTTP_STATUS_NOT_FOUND - Http status 404 - object
>> not
>> found.
>>
>> Random Musings of Jeremy Jameson : WSUS Clients Failing with Error
>> 0x80244019 After Installing WSUS SP1:
>> http://blogs.msdn.com/jjameson/archive/2008/04/08/wsus-clients-failing-with-error-0x80244019-after-installing-wsus-sp1.aspx
>>
>> Error 0x80244019 in WindowsUpdate.log - PatchAholic...The WSUS Blog!:
>> http://msmvps.com/blogs/athif/archive/2006/05/13/Error-0x80244019.aspx
>> </kibbitz>
>
> I did setup a new virtual directory in WSUS in IIS, called it selfupdate,
> left the permission to the default - read, stopped/restarted IIS, ran
> wuauclt /detectnow and still did not work. Please see the log below
<snip>


Re: WSUS 3.0 SP1 - computers have not reported status yet by Bob

Bob
Wed Oct 01 08:19:03 PDT 2008



"PA Bear [MS MVP]" wrote:

> [See Harry's reply posted about an hour before you replied to my post.]
>
> Bob wrote:
> > "PA Bear [MS MVP]" wrote:
> <snip>
> >> <kibbitz>
> >> 0x80244019 - SUS_E_PT_HTTP_STATUS_NOT_FOUND - Http status 404 - object
> >> not
> >> found.
> >>
> >> Random Musings of Jeremy Jameson : WSUS Clients Failing with Error
> >> 0x80244019 After Installing WSUS SP1:
> >> http://blogs.msdn.com/jjameson/archive/2008/04/08/wsus-clients-failing-with-error-0x80244019-after-installing-wsus-sp1.aspx
> >>
> >> Error 0x80244019 in WindowsUpdate.log - PatchAholic...The WSUS Blog!:
> >> http://msmvps.com/blogs/athif/archive/2006/05/13/Error-0x80244019.aspx
> >> </kibbitz>
> >
> > I did setup a new virtual directory in WSUS in IIS, called it selfupdate,
> > left the permission to the default - read, stopped/restarted IIS, ran
> > wuauclt /detectnow and still did not work. Please see the log below
> <snip>
>
>

I reviewed the Google article from Harry posted 9/30/08 1:39 PM.

In IIS my web site - WSUS, I mentioned i created a new virtual directory,
but found the following ---- in the path I have c:\program files\update
services ----- that is it - no selfupdate folder. I go to the directlry and
selfupdate does not exist, and the file --- wuident.cab does not exist either
in the mentioned path.

Any information is greatly appreciated.

Thanks,
Bob


Re: WSUS 3.0 SP1 - computers have not reported status yet by Harry

Harry
Wed Oct 01 13:39:29 PDT 2008

Bob wrote:

> In IIS my web site - WSUS, I mentioned i created a new virtual directory,
> but found the following ---- in the path I have c:\program files\update
> services ----- that is it - no selfupdate folder. I go to the directlry and
> selfupdate does not exist, and the file --- wuident.cab does not exist either
> in the mentioned path.

See KB920659,

<http://support.microsoft.com/kb/920659>

http://support.microsoft.com/kb/920659

"To resolve a problem where the SelfUpdate virtual directory is missing or there
is no SelfUpdate virtual directory listed under the Web site that is bound to
port 80, run the Selfupdate.msi file that is located in the Program files\Update
services\Setup folder."

Harry.

Re: WSUS 3.0 SP1 - computers have not reported status yet by PA

PA
Wed Oct 01 15:08:22 PDT 2008

Harry Johnston [MVP] wrote:
> Bob wrote:
>> In IIS my web site - WSUS, I mentioned i created a new virtual directory,
>> but found the following ---- in the path I have c:\program files\update
>> services ----- that is it - no selfupdate folder. I go to the directlry
>> and
>> selfupdate does not exist, and the file --- wuident.cab does not exist
>> either in the mentioned path.
>
> See KB920659,
>
> <http://support.microsoft.com/kb/920659>
>
> http://support.microsoft.com/kb/920659
>
> "To resolve a problem where the SelfUpdate virtual directory is missing or
> there is no SelfUpdate virtual directory listed under the Web site that is
> bound to port 80, run the Selfupdate.msi file that is located in the
> Program files\Update services\Setup folder."

[Sweet!]


Re: WSUS 3.0 SP1 - computers have not reported status yet by Bob

Bob
Thu Oct 02 08:26:10 PDT 2008



"Bob" wrote:

>
>
> "PA Bear [MS MVP]" wrote:
>
> > [See Harry's reply posted about an hour before you replied to my post.]
> >
> > Bob wrote:
> > > "PA Bear [MS MVP]" wrote:
> > <snip>
> > >> <kibbitz>
> > >> 0x80244019 - SUS_E_PT_HTTP_STATUS_NOT_FOUND - Http status 404 - object
> > >> not
> > >> found.
> > >>
> > >> Random Musings of Jeremy Jameson : WSUS Clients Failing with Error
> > >> 0x80244019 After Installing WSUS SP1:
> > >> http://blogs.msdn.com/jjameson/archive/2008/04/08/wsus-clients-failing-with-error-0x80244019-after-installing-wsus-sp1.aspx
> > >>
> > >> Error 0x80244019 in WindowsUpdate.log - PatchAholic...The WSUS Blog!:
> > >> http://msmvps.com/blogs/athif/archive/2006/05/13/Error-0x80244019.aspx
> > >> </kibbitz>
> > >
> > > I did setup a new virtual directory in WSUS in IIS, called it selfupdate,
> > > left the permission to the default - read, stopped/restarted IIS, ran
> > > wuauclt /detectnow and still did not work. Please see the log below
> > <snip>
> >
> >
>
> I reviewed the Google article from Harry posted 9/30/08 1:39 PM.
>
> In IIS my web site - WSUS, I mentioned i created a new virtual directory,
> but found the following ---- in the path I have c:\program files\update
> services ----- that is it - no selfupdate folder. I go to the directlry and
> selfupdate does not exist, and the file --- wuident.cab does not exist either
> in the mentioned path.
>
> Any information is greatly appreciated.
>
> Thanks,
> Bob
>

Below is the last post i found from Harry ----- Bob

Hokay. See what happens if you point a web browser at that URL. I expect
you'll get a 404 error, in which case the selfupdate tree is missing. This
post
may help:

<http://groups.google.com/group/microsoft.public.windows.server.update_services/msg/a73f6a5371c33478?hl=en>

http://groups.google.com/group/microsoft.public.windows.server.update_services/msg/a73f6a5371c33478?hl=en

Harry


I did try to point my web browser and access the URL and I did get a 404
error.

I also followed the Google groups information, however - there is no
wuident.cab file in the selfupdate folder.

I searched for wuident.cab and it's in the following locations --
c:\windows\software distribution\websetup
c:\windows\software distribution\selfupdate\default

Just to make sure I'm not missing anything -- the wuident.cab "must" be in
the selfupdate folder correct ? My path in selfupdate is - c:\program
files\update services\selfupdate

I re-ran the wuauclt /detectnow command from my desktop - after restart IIS,
still getting the complaint pointing to the cab file, please see below ---


Thanks,
Bob


2008-10-02 11:17:50:721 1088 15e0 AU Triggering AU detection through
DetectNow API
2008-10-02 11:17:50:721 1088 15e0 AU Triggering Online detection
(non-interactive)
2008-10-02 11:17:50:721 1088 3d0 AU #############
2008-10-02 11:17:50:721 1088 3d0 AU ## START ## AU: Search for updates
2008-10-02 11:17:50:721 1088 3d0 AU #########
2008-10-02 11:17:50:721 1088 3d0 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {BF49E835-CA20-4CE8-9A78-6F1868645ACA}]
2008-10-02 11:17:50:721 1088 1198 Agent *************
2008-10-02 11:17:50:721 1088 1198 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-10-02 11:17:50:721 1088 1198 Agent *********
2008-10-02 11:17:50:721 1088 1198 Agent * Online = Yes; Ignore download
priority = No
2008-10-02 11:17:50:721 1088 1198 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-10-02 11:17:50:721 1088 1198 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-10-02 11:17:50:736 1088 1198 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2008-10-02 11:17:50:830 1088 1198 Misc Microsoft signed: Yes
2008-10-02 11:17:50:861 1088 1198 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190194
2008-10-02 11:17:50:877 1088 1198 Misc WARNING: WinHttp:
ShouldFileBeDownloaded failed with 0x80190194
2008-10-02 11:17:50:877 1088 1198 Misc WARNING: DownloadFileInternal failed
for http://intranet1:8530/selfupdate/wuident.cab: error 0x80190194
2008-10-02 11:17:50:877 1088 1198 Setup FATAL: IsUpdateRequired failed with
error 0x80244019
2008-10-02 11:17:50:877 1088 1198 Setup WARNING: SelfUpdate: Default
Service: IsUpdateRequired failed: 0x80244019
2008-10-02 11:17:50:877 1088 1198 Setup WARNING: SelfUpdate: Default
Service: IsUpdateRequired failed, error = 0x80244019
2008-10-02 11:17:50:877 1088 1198 Agent * WARNING: Skipping scan,
self-update check returned 0x80244019
2008-10-02 11:17:52:143 1088 1198 Agent * WARNING: Exit code = 0x80244019
2008-10-02 11:17:52:143 1088 1198 Agent *********
2008-10-02 11:17:52:143 1088 1198 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-10-02 11:17:52:143 1088 1198 Agent *************
2008-10-02 11:17:52:143 1088 1198 Agent WARNING: WU client failed Searching
for update with error 0x80244019
2008-10-02 11:17:52:143 1088 12e0 AU >>## RESUMED ## AU: Search for
updates [CallId = {BF49E835-CA20-4CE8-9A78-6F1868645ACA}]
2008-10-02 11:17:52:143 1088 12e0 AU # WARNING: Search callback failed,
result = 0x80244019
2008-10-02 11:17:52:143 1088 12e0 AU # WARNING: Failed to find updates
with error code 80244019
2008-10-02 11:17:52:143 1088 12e0 AU #########
2008-10-02 11:17:52:143 1088 12e0 AU ## END ## AU: Search for updates
[CallId = {BF49E835-CA20-4CE8-9A78-6F1868645ACA}]
2008-10-02 11:17:52:143 1088 12e0 AU #############
2008-10-02 11:17:52:143 1088 12e0 AU AU setting next detection timeout to
2008-10-02 20:17:52
2008-10-02 11:17:55:893 1088 1198 Report REPORT EVENT:
{47553699-BA15-42F3-8001-AD621B243EEC} 2008-10-02
11:17:50:877-0400 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 0 80244019 SelfUpdate Failure Software
Synchronization Windows Update Client failed to detect with error 0x80244019.


Re: WSUS 3.0 SP1 - computers have not reported status yet by PA

PA
Thu Oct 02 16:03:05 PDT 2008

Bob wrote:
>
>> "PA Bear [MS MVP]" wrote:
>>> [See Harry's reply posted about an hour before you replied to my post.]
<snip>
> Below is the last post i found from Harry ----- Bob
<snip>

Reply to Harry's post, not mine.

Re: WSUS 3.0 SP1 - computers have not reported status yet by Harry

Harry
Thu Oct 02 18:38:21 PDT 2008

Bob wrote:

> Below is the last post i found from Harry ----- Bob

Repost:

See KB920659,

<http://support.microsoft.com/kb/920659>

http://support.microsoft.com/kb/920659

"To resolve a problem where the SelfUpdate virtual directory is missing or there
is no SelfUpdate virtual directory listed under the Web site that is bound to
port 80, run the Selfupdate.msi file that is located in the Program files\Update
services\Setup folder."

Please let us know whether or not this works.

Harry.

Re: WSUS 3.0 SP1 - computers have not reported status yet by Bob

Bob
Fri Oct 03 10:51:01 PDT 2008



"Bob" wrote:

>
>
> "PA Bear [MS MVP]" wrote:
>
> > [See Harry's reply posted about an hour before you replied to my post.]
> >
> > Bob wrote:
> > > "PA Bear [MS MVP]" wrote:
> > <snip>
> > >> <kibbitz>
> > >> 0x80244019 - SUS_E_PT_HTTP_STATUS_NOT_FOUND - Http status 404 - object
> > >> not
> > >> found.
> > >>
> > >> Random Musings of Jeremy Jameson : WSUS Clients Failing with Error
> > >> 0x80244019 After Installing WSUS SP1:
> > >> http://blogs.msdn.com/jjameson/archive/2008/04/08/wsus-clients-failing-with-error-0x80244019-after-installing-wsus-sp1.aspx
> > >>
> > >> Error 0x80244019 in WindowsUpdate.log - PatchAholic...The WSUS Blog!:
> > >> http://msmvps.com/blogs/athif/archive/2006/05/13/Error-0x80244019.aspx
> > >> </kibbitz>
> > >
> > > I did setup a new virtual directory in WSUS in IIS, called it selfupdate,
> > > left the permission to the default - read, stopped/restarted IIS, ran
> > > wuauclt /detectnow and still did not work. Please see the log below
> > <snip>
> >
> >
>
> I reviewed the Google article from Harry posted 9/30/08 1:39 PM.
>
> In IIS my web site - WSUS, I mentioned i created a new virtual directory,
> but found the following ---- in the path I have c:\program files\update
> services ----- that is it - no selfupdate folder. I go to the directlry and
> selfupdate does not exist, and the file --- wuident.cab does not exist either
> in the mentioned path.
>
> Any information is greatly appreciated.
>
> Thanks,
> Bob
>


I received a notice of a reply, but did not find any reply. The last post I
made was October 2, I copied it below again to review.

Thanks,
Bob



I reviewed the Google article from Harry posted 9/30/08 1:39 PM.
>
> In IIS my web site - WSUS, I mentioned i created a new virtual directory,
> but found the following ---- in the path I have c:\program files\update
> services ----- that is it - no selfupdate folder. I go to the directlry and
> selfupdate does not exist, and the file --- wuident.cab does not exist either
> in the mentioned path.
>
> Any information is greatly appreciated.
>
> Thanks,
> Bob






Re: WSUS 3.0 SP1 - computers have not reported status yet by PA

PA
Fri Oct 03 12:12:53 PDT 2008

Whether you received an email notification about Harry's post on 01 October
or not, here it is in Google Groups archive:
http://groups.google.com/group/microsoft.public.windowsupdate/msg/f54726164a91c08b

And he posted the same information again in yet another reply to this thread
on 02 October (16 hours before your reply to which I'm replying now):
http://groups.google.com/group/microsoft.public.windowsupdate/msg/a55c62cee5422385

Harry points you to the Resolution section of this KB article:
http://support.microsoft.com/kb/920659

"To resolve a problem where the SelfUpdate virtual directory is missing or
there
is no SelfUpdate virtual directory listed under the Web site that is bound
to
port 80, run the Selfupdate.msi file that is located in the Program
files\Update
services\Setup folder."
--
~PA Bear

Bob wrote:
>
>> "PA Bear [MS MVP]" wrote:
>>> [See Harry's reply posted about an hour before you replied to my post.]
>>>
<snip>
> I received a notice of a reply, but did not find any reply. The last post
> I
> made was October 2, I copied it below again to review...


Re: WSUS 3.0 SP1 - computers have not reported status yet by Bob

Bob
Fri Oct 03 14:04:00 PDT 2008



"Bob" wrote:

>
>
> "PA Bear [MS MVP]" wrote:
>
> > [See Harry's reply posted about an hour before you replied to my post.]
> >
> > Bob wrote:
> > > "PA Bear [MS MVP]" wrote:
> > <snip>
> > >> <kibbitz>
> > >> 0x80244019 - SUS_E_PT_HTTP_STATUS_NOT_FOUND - Http status 404 - object
> > >> not
> > >> found.
> > >>
> > >> Random Musings of Jeremy Jameson : WSUS Clients Failing with Error
> > >> 0x80244019 After Installing WSUS SP1:
> > >> http://blogs.msdn.com/jjameson/archive/2008/04/08/wsus-clients-failing-with-error-0x80244019-after-installing-wsus-sp1.aspx
> > >>
> > >> Error 0x80244019 in WindowsUpdate.log - PatchAholic...The WSUS Blog!:
> > >> http://msmvps.com/blogs/athif/archive/2006/05/13/Error-0x80244019.aspx
> > >> </kibbitz>
> > >
> > > I did setup a new virtual directory in WSUS in IIS, called it selfupdate,
> > > left the permission to the default - read, stopped/restarted IIS, ran
> > > wuauclt /detectnow and still did not work. Please see the log below
> > <snip>
> >
> >
>
> I reviewed the Google article from Harry posted 9/30/08 1:39 PM.
>
> In IIS my web site - WSUS, I mentioned i created a new virtual directory,
> but found the following ---- in the path I have c:\program files\update
> services ----- that is it - no selfupdate folder. I go to the directlry and
> selfupdate does not exist, and the file --- wuident.cab does not exist either
> in the mentioned path.
>
> Any information is greatly appreciated.
>
> Thanks,
> Bob
> This is strange --- I'm getting email notifications but nobody is replying back .....

Bob


Re: WSUS 3.0 SP1 - computers have not reported status yet by Dejan

Dejan
Fri Oct 03 14:03:41 PDT 2008

Hi

I had the exact problem a few weeks ago. The problem was (is) service pack
for Office 2003. Maybee this link will help you:

http://www.wsus.info/forums/index.php?showtopic=11876

Doing that solved my problems and computers are now reporting status like
they shoud.

"Harry Johnston [MVP]" <harry@scms.waikato.ac.nz> wrote in message
news:%23JjYcwzIJHA.508@TK2MSFTNGP05.phx.gbl...
> Bob wrote:
>
>> 2008-09-30 09:55:53:073 1088 108c Misc WARNING: DownloadFileInternal
>> failed for http://intranet1:8530/selfupdate/wuident.cab: error 0x80190194
>
> Hokay. See what happens if you point a web browser at that URL. I expect
> you'll get a 404 error, in which case the selfupdate tree is missing.
> This post may help:
>
> <http://groups.google.com/group/microsoft.public.windows.server.update_services/msg/a73f6a5371c33478?hl=en>
>
> http://groups.google.com/group/microsoft.public.windows.server.update_services/msg/a73f6a5371c33478?hl=en
>
> Harry.



Re: WSUS 3.0 SP1 - computers have not reported status yet by Harry

Harry
Fri Oct 03 14:52:11 PDT 2008

Bob wrote:

> This is strange --- I'm getting email notifications but nobody is replying back .....

Can you see this message? To get more reliable access to the newsgroup, try
Google Groups. You can search on the subject of your post to locate the thread.

Harry.

Re: WSUS 3.0 SP1 - computers have not reported status yet by Bob

Bob
Mon Oct 06 09:43:00 PDT 2008


Hi Harry,

I read the support article - kb920659.

Selfupdate.msi does not exist on my server, I also followed thru the article
and no luck. The article did mention port 80, I'm not using port 80 i setup a
custom web site as I use IIS for other applications.

I did create a "new virtual directory" SelfUpdate previously, not virtual
directory(from file). When I click on the drop down in selfupdate virtual
directory, I get - there are no items to be shown.

Do you believe I should uninstall WSUS, maybe install on a differnet server
? anyone run WSUS on a DC ?

Thanks,
Bob


"Harry Johnston [MVP]" wrote:

> Bob wrote:
>
> > In IIS my web site - WSUS, I mentioned i created a new virtual directory,
> > but found the following ---- in the path I have c:\program files\update
> > services ----- that is it - no selfupdate folder. I go to the directlry and
> > selfupdate does not exist, and the file --- wuident.cab does not exist either
> > in the mentioned path.
>
> See KB920659,
>
> <http://support.microsoft.com/kb/920659>
>
> http://support.microsoft.com/kb/920659
>
> "To resolve a problem w