Clients not updating 0% status

Hello all,

I am having some strange problem in my WSUS3 server. The server I had
installed wsus 3 server had a problem with Harddrive so I had to setup new
server with enough diskspace. What I did was setup new server with exactly
the same configuration like IP, name, etc. And I installed WSUS3.0 service
pack1 and made all the Computers folder as exactly as it was in crashed
server. Firewall is also the same as previous one. As soon as start the the
server all clietns (that were in previous server) popped up in console. The
problem is some machine showed up with 99% installed with last status report
data and time but other are "Not yet Reported" with 0% installed (for weeks
now9. Also If I add new machines, this also shows up in the console but
remains 0% installed with "not yet reported". What could be the problem on
this, what am i missing? can you guys guide me somewhere. This was working
fine with previous server.

I checked one of the problem machines and have no error and error looks like
this .

2008-07-15 11:52:38:890 1940 b0 Misc =========== Logging initialized (build:
7.0.6000.381, tz: -0000) ===========
2008-07-15 11:52:38:890 1940 b0 Misc = Process: C:\WINDOWS\Explorer.EXE
2008-07-15 11:52:38:890 1940 b0 Misc = Module: C:\WINDOWS\system32\wuaueng.dll
2008-07-15 11:52:38:890 1940 b0 Shutdwn Install at shutdown: no updates to
install
2008-07-15 14:10:40:484 1692 1445c AU AU received policy change subscription
event
2008-07-15 14:19:12:312 1692 1445c AU AU received policy change subscription
event
2008-07-15 14:40:00:468 1692 1445c AU AU received policy change subscription
event

I run the wsus client diag tool it pass but it comes with like this :
WinHttpDownloadFileToMemory(szURLDest, NULL, 0, NULL, NULL, NULL,
&downloadBuffe
r) failed with hr=0x80190194

AT

(cross-post added to WSUS)
"Anil" <Anil@discussions.microsoft.com> wrote in message
newsE393EB6-E37B-458E-82E8-B9F8BE014B80@microsoft.com...
> Hello all,
>
> I am having some strange problem in my WSUS3 server. The server I had
> installed wsus 3 server had a problem with Harddrive so I had to setup new
> server with enough diskspace. What I did was setup new server with exactly
> the same configuration like IP, name, etc. And I installed WSUS3.0 service
> pack1 and made all the Computers folder as exactly as it was in crashed
> server. Firewall is also the same as previous one. As soon as start the the
> server all clietns (that were in previous server) popped up in console. The
> problem is some machine showed up with 99% installed with last status report
> data and time but other are "Not yet Reported" with 0% installed (for weeks
> now9. Also If I add new machines, this also shows up in the console but
> remains 0% installed with "not yet reported". What could be the problem on
> this, what am i missing? can you guys guide me somewhere. This was working
> fine with previous server.
>
> I checked one of the problem machines and have no error and error looks like
> this .
>
> 2008-07-15 11:52:38:890 1940 b0 Misc =========== Logging initialized (build:
> 7.0.6000.381, tz: -0000) ===========
> 2008-07-15 11:52:38:890 1940 b0 Misc = Process: C:\WINDOWS\Explorer.EXE
> 2008-07-15 11:52:38:890 1940 b0 Misc = Module: C:\WINDOWS\system32\wuaueng.dll
> 2008-07-15 11:52:38:890 1940 b0 Shutdwn Install at shutdown: no updates to
> install
> 2008-07-15 14:10:40:484 1692 1445c AU AU received policy change subscription
> event
> 2008-07-15 14:19:12:312 1692 1445c AU AU received policy change subscription
> event
> 2008-07-15 14:40:00:468 1692 1445c AU AU received policy change subscription
> event
>
> I run the wsus client diag tool it pass but it comes with like this :
> WinHttpDownloadFileToMemory(szURLDest, NULL, 0, NULL, NULL, NULL,
> &downloadBuffe
> r) failed with hr=0x80190194
>
> AT


FWIW 0x0194 == 404 so whatever that last thing you did was
it sent an invalid request to a server. Use Fiddler2 to capture more details
if you can't find any better normal diagnostics.

BTW since your problems seem to have more to do with WSUS than with WU
I have cross-posted this thread to a more relevant newsgroup.


HTH

Robert Aldwinckle
---

Hello Robert,

That did the trick for me. However, one error pops up every now and then in
event viewer. "The Server Synchronization Web server is not working", what
service this is refereing to. when this message pops up client are not
getting updates. Do you have any tips for this ?

AT

"Lawrence Garvin" wrote:

> "Robert Aldwinckle" <robald@techemail.com> wrote in message
> news:OfTjwVR6IHA.404@TK2MSFTNGP05.phx.gbl...
>
> >> I run the wsus client diag tool it pass but it comes with like this :
> >> WinHttpDownloadFileToMemory(szURLDest, NULL, 0, NULL, NULL, NULL,
> >> &downloadBuffe
> >> r) failed with hr=0x80190194
>
> > FWIW 0x0194 == 404 so whatever that last thing you did was
> > it sent an invalid request to a server. Use Fiddler2 to capture more
> > details
> > if you can't find any better normal diagnostics.
> >
> > BTW since your problems seem to have more to do with WSUS than with WU
> > I have cross-posted this thread to a more relevant newsgroup.
>
> The '404' error when running the Client Diagnostic Tool is the WUA
> attempting to acquire the CAB file in the ~\selfupdate virtual directory.
> When this error appears, it's almost always because the ~\selfupdate virtual
> directory is missing -- typically as a result of applying the Service
> Pack -- which has an annoying habit of doing this.
>
> To repair:
>
> 1. Create a virtual directory called 'selfupdate'.
> 2. Assign it to the pathname C:\Program Files\Update Services\selfupdate
> 3. Set the access permissions to allow anonymous access.
>
>
>
>
> --
> Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
> 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
>

follow on with my earlier post. Since I created ´selfupadate directory´that
has resolve the issue. the other problem with Synchronization has resolved
after I add read permission in root drive where update contents are stored
(in my case) c:\wsus.

Since then it starts downloading the updates from microsoft and taking very
long time. Also I get error message in Event view "The server is failing to
download some updates" and bellow error:

Content file download failed. Reason: The requested URL does not exist on
the server.
Source File:
/msdownload/update/software/updt/2008/04/lp-nb-no_6e7b44785f45983208c9016f6875771fe4547143.exe
Destination File:
c:\WSUS\WsusContent\43\6E7B44785F45983208C9016F687 5771FE4547143.exe.

All clients are only 96-99 % updated and some clients that are recently
added are not installed winxp service pack3. WSUS console shows at downloaded
status as 18,307.56 MB of 30,666.41MB. Taking long time might have been
bandwidth issue. Should I wait until this will fully downloaded so client
will updated accordingly. I had setup for automatic approval too. And how big
the Hard disk require for these update to store? I guess it would delete the
unused, expired etc will cleaned up automatically so 45 GB should be just
fine. Can some one give me some clear picture on this ?

AT
"Anil" wrote:

> Hello Robert,
>
> That did the trick for me. However, one error pops up every now and then in
> event viewer. "The Server Synchronization Web server is not working", what
> service this is refereing to. when this message pops up client are not
> getting updates. Do you have any tips for this ?
>
> AT
>
> "Lawrence Garvin" wrote:
>
> > "Robert Aldwinckle" <robald@techemail.com> wrote in message
> > news:OfTjwVR6IHA.404@TK2MSFTNGP05.phx.gbl...
> >
> > >> I run the wsus client diag tool it pass but it comes with like this :
> > >> WinHttpDownloadFileToMemory(szURLDest, NULL, 0, NULL, NULL, NULL,
> > >> &downloadBuffe
> > >> r) failed with hr=0x80190194
> >
> > > FWIW 0x0194 == 404 so whatever that last thing you did was
> > > it sent an invalid request to a server. Use Fiddler2 to capture more
> > > details
> > > if you can't find any better normal diagnostics.
> > >
> > > BTW since your problems seem to have more to do with WSUS than with WU
> > > I have cross-posted this thread to a more relevant newsgroup.
> >
> > The '404' error when running the Client Diagnostic Tool is the WUA
> > attempting to acquire the CAB file in the ~\selfupdate virtual directory.
> > When this error appears, it's almost always because the ~\selfupdate virtual
> > directory is missing -- typically as a result of applying the Service
> > Pack -- which has an annoying habit of doing this.
> >
> > To repair:
> >
> > 1. Create a virtual directory called 'selfupdate'.
> > 2. Assign it to the pathname C:\Program Files\Update Services\selfupdate
> > 3. Set the access permissions to allow anonymous access.
> >
> >
> >
> >
> > --
> > Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
> > 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
> >