WSUS 3.0 SP1 - computers have not reported status yet

[Bob]

"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/archi...-wsus-sp1.aspx
> >>
> >> Error 0x80244019 in WindowsUpdate.log - PatchAholic...The WSUS Blog!:
> >> http://msmvps.com/blogs/athif/archiv...x80244019.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

[Harry Johnston [MVP]]

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.

[PA Bear [MS MVP]]

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!]

[Bob]

"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/archi...-wsus-sp1.aspx
> > >>
> > >> Error 0x80244019 in WindowsUpdate.log - PatchAholic...The WSUS Blog!:
> > >> http://msmvps.com/blogs/athif/archiv...x80244019.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/micro...71c33478?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.

[PA Bear [MS MVP]]

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.

[Harry Johnston [MVP]]

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.

[Bob]

"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/archi...-wsus-sp1.aspx
> > >>
> > >> Error 0x80244019 in WindowsUpdate.log - PatchAholic...The WSUS Blog!:
> > >> http://msmvps.com/blogs/athif/archiv...x80244019.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

[PA Bear [MS MVP]]

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/micro...4726164a91c08b

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/micro...5c62cee5422385

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...

[Dejan Klancar]

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/micro...71c33478?hl=en
>
> Harry.

[Bob]

"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/archi...-wsus-sp1.aspx
> > >>
> > >> Error 0x80244019 in WindowsUpdate.log - PatchAholic...The WSUS Blog!:
> > >> http://msmvps.com/blogs/athif/archiv...x80244019.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

[Harry Johnston [MVP]]

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.

[Bob]

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 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.
>

[Harry Johnston [MVP]]

Bob wrote:

> Selfupdate.msi does not exist on my server, [...]

That's not a good sign.

> Do you believe I should uninstall WSUS,

Yes, I think so.

> maybe install on a differnet server

I think it would be OK to try reinstalling on the same server first.

> ? anyone run WSUS on a DC ?

Not considered best practice, but it does work.

Harry.

[Bob]

"Harry Johnston [MVP]" wrote:

> Bob wrote:
>
> > Selfupdate.msi does not exist on my server, [...]
>
> That's not a good sign.
>
> > Do you believe I should uninstall WSUS,
>
> Yes, I think so.
>
> > maybe install on a differnet server
>
> I think it would be OK to try reinstalling on the same server first.
>
> > ? anyone run WSUS on a DC ?
>
> Not considered best practice, but it does work.
>
> Harry.
>
Thanks Harry,

I will un-install then re-install on the same server still to a custom port
not 80. Can you tell me if there is anything I should check after the
un-install, maybe check for any directories that may be left behind ? How
about SP1 - good idea to install it, as I read about it causing problems ?

Thanks again,
Bob

[Harry Johnston [MVP]]

Bob wrote:

> I will un-install then re-install on the same server still to a custom port
> not 80. Can you tell me if there is anything I should check after the
> un-install, maybe check for any directories that may be left behind ?

I'm not sure about this one. I think if the uninstall doesn't produce any error
messages, anything that has been left behind shouldn't cause problems.

> How about SP1 - good idea to install it, as I read about it causing problems ?

I'd stick with it, at least for now. (I'm not sure you've got a choice, I don't
recall offhand whether the RTM version is still available for download.)

Harry.