WSUS 3.0 Computers Not Reported Yet

[Noddy53]

Hi All

I am having major problems with my XP clients and WSUS.

Basically my set-up is as follows.
I have a master WSUS Server and 5 DownStream Servers. The master WSUS Server connects to MS fine to receive updates and is installed on Port 80. My 5 DownStream Servers connect to my master and receive updates and update themselves no problem.

In DNS I use round robin for the 5 DownStream servers, they are all at diffrent sites on diffrent LAN's and in DNS are all known as WSUS.

WSUS on each of the DownStream Servers is installed in their own Website in IIS using Port 8530. GP is set for the clients to pick up their updates from http://WSUS:8530

Out of 5 sites I only seem to have one that is working , all the others the clients show up in the local WSUS console with the Yellow Triangle with a Status of Not Reported Yet.

When Starting WSUS3.0 console I get the following Pop Up

> error saying "IIS Worker Process encountered a problem and needed to
> close.". As a side note, in the event log, I see this error after
> restarting the WSUS sever

When I re-start the Update Service I get the following Error in the Event Viewer

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12022
Date: 25/10/2007
Time: 15:21:20
User: N/A
Computer: ML-CRD-DC0
Description:
The Client Web Service is not working.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I am constantly getting the following ASP NET Warning Messages in the Event Viewer

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12022
Date: 25/10/2007
Time: 15:21:20
User: N/A
Computer: ML-CRD-DC0
Description:
The Client Web Service is not working.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

And this is what is reporting in the Windows Update log on a client PC.

2007-10-25 13:31:21:656 1000 5d0 Misc =========== Logging initialized (build: 7.0.6000.374, tz: +0100) ===========
2007-10-25 13:31:21:671 1000 5d0 Misc = Process: C:\WINDOWS\System32\svchost.exe
2007-10-25 13:31:21:671 1000 5d0 Misc = Module: C:\WINDOWS\system32\wuaueng.dll
2007-10-25 13:31:21:656 1000 5d0 Service *************
2007-10-25 13:31:21:671 1000 5d0 Service ** START ** Service: Service startup
2007-10-25 13:31:21:671 1000 5d0 Service *********
2007-10-25 13:31:21:687 1000 5d0 Agent * WU client version 7.0.6000.374
2007-10-25 13:31:21:687 1000 5d0 Agent * Base directory: C:\WINDOWS\SoftwareDistribution
2007-10-25 13:31:21:687 1000 5d0 Agent * Access type: No proxy
2007-10-25 13:31:21:687 1000 5d0 Agent * Network state: Connected
2007-10-25 13:32:04:070 1000 8a0 Agent *********** Agent: Initializing Windows Update Agent ***********
2007-10-25 13:32:04:070 1000 8a0 Agent *********** Agent: Initializing global settings cache ***********
2007-10-25 13:32:04:070 1000 8a0 Agent * WSUS server: http://WSUS:8530
2007-10-25 13:32:04:070 1000 8a0 Agent * WSUS status server: http://WSUS:8530
2007-10-25 13:32:04:070 1000 8a0 Agent * Target group: Desktop and Laptop
2007-10-25 13:32:04:070 1000 8a0 Agent * Windows Update access disabled: No
2007-10-25 13:32:04:083 1000 8a0 DnldMgr Download manager restoring 0 downloads
2007-10-25 13:32:04:208 1000 8a0 AU ########### AU: Initializing Automatic Updates ###########
2007-10-25 13:32:04:296 1000 8a0 AU # WSUS server: http://WSUS:8530
2007-10-25 13:32:04:296 1000 8a0 AU # Detection frequency: 4
2007-10-25 13:32:04:296 1000 8a0 AU # Target group: Desktop and Laptop
2007-10-25 13:32:04:296 1000 8a0 AU # Approval type: Scheduled (Policy)
2007-10-25 13:32:04:296 1000 8a0 AU # Scheduled install day/time: Every day at 10:00
2007-10-25 13:32:04:296 1000 8a0 AU # Auto-install minor updates: Yes (User preference)
2007-10-25 13:32:04:371 1000 8a0 AU Setting AU scheduled install time to 2007-10-26 09:00:00
2007-10-25 13:32:04:371 1000 8a0 AU AU finished delayed initialization
2007-10-25 13:32:04:371 1000 8a0 AU Triggering AU detection through DetectNow API
2007-10-25 13:32:04:371 1000 8a0 AU Triggering Online detection (non-interactive)
2007-10-25 13:32:05:411 1000 5d0 Agent Created new random SusClientId 9766f084-b6e7-4d58-a836-8c205038d96b. Old Id: none.
2007-10-25 13:32:05:411 1000 5d0 Report *********** Report: Initializing static reporting data ***********
2007-10-25 13:32:05:411 1000 5d0 Report * OS Version = 5.1.2600.2.0.65792
2007-10-25 13:32:05:462 1000 5d0 Report * Computer Brand = Hewlett-Packard
2007-10-25 13:32:05:462 1000 5d0 Report * Computer Model = HP Compaq nc6120 (PY505ET#ABU)
2007-10-25 13:32:05:462 1000 5d0 Report * Bios Revision = 68DTD Ver. F.0B
2007-10-25 13:32:05:462 1000 5d0 Report * Bios Name = EPP runtime BIOS - Version 1.1
2007-10-25 13:32:05:462 1000 5d0 Report * Bios Release Date = 2005-09-16T00:00:00
2007-10-25 13:32:05:462 1000 5d0 Report * Locale ID = 2057
2007-10-25 13:32:05:537 1000 5d0 AU #############
2007-10-25 13:32:05:537 1000 5d0 AU ## START ## AU: Search for updates
2007-10-25 13:32:05:537 1000 5d0 AU #########
2007-10-25 13:32:05:650 1000 5d0 AU <<## SUBMITTED ## AU: Search for updates [CallId = {84D2FFDF-2D9E-4F99-816C-E1631EA4C6D2}]
2007-10-25 13:32:06:502 1000 5d0 AU ########### AU: Uninitializing Automatic Updates ###########
2007-10-25 13:32:09:159 1000 aec PT WARNING: GetCurrentComputerInfo failed, not fatal: 0x8024000b
2007-10-25 13:32:09:159 1000 aec PT WARNING: Cached cookie has expired or new PID is available
2007-10-25 13:32:09:159 1000 aec PT WARNING: PopulateAuthCookies failed: 0x8024000b
2007-10-25 13:32:09:159 1000 aec PT WARNING: RefreshCookie failed: 0x8024000b
2007-10-25 13:32:09:159 1000 aec PT WARNING: RefreshPTState failed: 0x8024000b
2007-10-25 13:32:09:159 1000 aec PT WARNING: PTError: 0x8024000b
2007-10-25 13:32:09:159 1000 aec Report WARNING: Reporter failed to upload events with hr = 8024000b.
2007-10-25 13:32:09:222 1000 5d0 Report WARNING: Reporter failed to upload events with hr = 80240004.
2007-10-25 13:32:09:473 1000 5d0 Service *********
2007-10-25 13:32:09:473 1000 5d0 Service ** END ** Service: Service exit [Exit code = 0x240001]
2007-10-25 13:32:09:473 1000 5d0 Service *************
2007-10-25 13:32:10:651 1000 b74 Misc =========== Logging initialized (build: 7.0.6000.374, tz: +0100) ===========
2007-10-25 13:32:10:651 1000 b74 Misc = Process: C:\WINDOWS\System32\svchost.exe
2007-10-25 13:32:10:651 1000 b74 Misc = Module: C:\WINDOWS\system32\wuaueng.dll
2007-10-25 13:32:10:651 1000 b74 Service *************
2007-10-25 13:32:10:651 1000 b74 Service ** START ** Service: Service startup
2007-10-25 13:32:10:651 1000 b74 Service *********
2007-10-25 13:32:10:651 1000 b74 Agent * WU client version 7.0.6000.374
2007-10-25 13:32:10:651 1000 b74 Agent * Base directory: C:\WINDOWS\SoftwareDistribution
2007-10-25 13:32:10:651 1000 b74 Agent * Access type: No proxy
2007-10-25 13:32:10:651 1000 b74 Agent * Network state: Connected
2007-10-25 13:32:56:115 1000 b74 Agent *********** Agent: Initializing Windows Update Agent ***********
2007-10-25 13:32:56:115 1000 b74 Agent *********** Agent: Initializing global settings cache ***********
2007-10-25 13:32:56:115 1000 b74 Agent * WSUS server: http://WSUS:8530
2007-10-25 13:32:56:115 1000 b74 Agent * WSUS status server: http://WSUS:8530
2007-10-25 13:32:56:115 1000 b74 Agent * Target group: Desktop and Laptop
2007-10-25 13:32:56:115 1000 b74 Agent * Windows Update access disabled: No
2007-10-25 13:32:56:115 1000 b74 DnldMgr Download manager restoring 0 downloads
2007-10-25 13:32:56:115 1000 b74 AU ########### AU: Initializing Automatic Updates ###########
2007-10-25 13:32:56:115 1000 b74 AU # WSUS server: http://WSUS:8530
2007-10-25 13:32:56:115 1000 b74 AU # Detection frequency: 4
2007-10-25 13:32:56:115 1000 b74 AU # Target group: Desktop and Laptop
2007-10-25 13:32:56:115 1000 b74 AU # Approval type: Scheduled (Policy)
2007-10-25 13:32:56:115 1000 b74 AU # Scheduled install day/time: Every day at 10:00
2007-10-25 13:32:56:115 1000 b74 AU # Auto-install minor updates: Yes (User preference)
2007-10-25 13:32:56:115 1000 b74 AU Setting AU scheduled install time to 2007-10-26 09:00:00
2007-10-25 13:32:56:115 1000 b74 AU AU finished delayed initialization
2007-10-25 13:32:56:528 1000 b74 Report *********** Report: Initializing static reporting data ***********
2007-10-25 13:32:56:528 1000 b74 Report * OS Version = 5.1.2600.2.0.65792
2007-10-25 13:32:56:591 1000 b74 Report * Computer Brand = Hewlett-Packard
2007-10-25 13:32:56:591 1000 b74 Report * Computer Model = HP Compaq nc6120 (PY505ET#ABU)
2007-10-25 13:32:56:591 1000 b74 Report * Bios Revision = 68DTD Ver. F.0B
2007-10-25 13:32:56:591 1000 b74 Report * Bios Name = EPP runtime BIOS - Version 1.1
2007-10-25 13:32:56:591 1000 b74 Report * Bios Release Date = 2005-09-16T00:00:00
2007-10-25 13:32:56:591 1000 b74 Report * Locale ID = 2057
2007-10-25 13:32:57:481 1000 228 PT WARNING: Cached cookie has expired or new PID is available
2007-10-25 13:32:57:481 1000 228 PT Initializing simple targeting cookie, clientId = 9766f084-b6e7-4d58-a836-8c205038d96b, target group = Desktop and Laptop, DNS name = ml133.milklink.com
2007-10-25 13:32:57:481 1000 228 PT Server URL = http://WSUS:8530/SimpleAuthWebService/SimpleAuth.asmx
2007-10-25 13:33:06:431 1000 228 PT WARNING: GetCookie failure, error = 0x80244008, soap client error = 8, soap error code = 0, HTTP status code = 200
2007-10-25 13:33:06:431 1000 228 PT WARNING: PTError: 0x80244008
2007-10-25 13:33:06:431 1000 228 PT WARNING: GetCookie_WithRecovery failed : 0x80244008
2007-10-25 13:33:06:431 1000 228 PT WARNING: RefreshCookie failed: 0x80244008
2007-10-25 13:33:06:431 1000 228 PT WARNING: RefreshPTState failed: 0x80244008
2007-10-25 13:33:06:431 1000 228 PT WARNING: PTError: 0x80244008
2007-10-25 13:33:06:431 1000 228 Report WARNING: Reporter failed to upload events with hr = 80244008.
2007-10-25 13:33:06:481 1000 228 PT WARNING: Cached cookie has expired or new PID is available
2007-10-25 13:33:06:481 1000 228 PT Initializing simple targeting cookie, clientId = 9766f084-b6e7-4d58-a836-8c205038d96b, target group = Desktop and Laptop, DNS name = ml133.milklink.com
2007-10-25 13:33:06:481 1000 228 PT Server URL = http://WSUS:8530/SimpleAuthWebService/SimpleAuth.asmx
2007-10-25 13:33:06:481 1000 228 PT WARNING: GetCookie failure, error = 0x80244008, soap client error = 8, soap error code = 0, HTTP status code = 200
2007-10-25 13:33:06:481 1000 228 PT WARNING: PTError: 0x80244008
2007-10-25 13:33:06:481 1000 228 PT WARNING: GetCookie_WithRecovery failed : 0x80244008
2007-10-25 13:33:06:481 1000 228 PT WARNING: RefreshCookie failed: 0x80244008
2007-10-25 13:33:06:481 1000 228 PT WARNING: RefreshPTState failed: 0x80244008
2007-10-25 13:33:06:481 1000 228 PT WARNING: PTError: 0x80244008
2007-10-25 13:33:06:481 1000 228 Report WARNING: Reporter failed to upload events with hr = 80244008.
2007-10-25 13:33:06:531 1000 228 PT WARNING: Cached cookie has expired or new PID is available
2007-10-25 13:33:06:531 1000 228 PT Initializing simple targeting cookie, clientId = 9766f084-b6e7-4d58-a836-8c205038d96b, target group = Desktop and Laptop, DNS name = ml133.milklink.com
2007-10-25 13:33:06:531 1000 228 PT Server URL = http://WSUS:8530/SimpleAuthWebService/SimpleAuth.asmx
2007-10-25 13:33:06:531 1000 228 PT WARNING: GetCookie failure, error = 0x80244008, soap client error = 8, soap error code = 0, HTTP status code = 200
2007-10-25 13:33:06:531 1000 228 PT WARNING: PTError: 0x80244008
2007-10-25 13:33:06:531 1000 228 PT WARNING: GetCookie_WithRecovery failed : 0x80244008
2007-10-25 13:33:06:531 1000 228 PT WARNING: RefreshCookie failed: 0x80244008
2007-10-25 13:33:06:531 1000 228 PT WARNING: RefreshPTState failed: 0x80244008
2007-10-25 13:33:06:531 1000 228 PT WARNING: PTError: 0x80244008
2007-10-25 13:33:06:531 1000 228 Report WARNING: Reporter failed to upload events with hr = 80244008.


I have tried the following Script to re-register but this does not seemed to of helped.

reg delete
\\%computername%\HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpda*te
/v SusClientId /f
wuauclt.exe /resetauthorization /detectnow
net stop wuauserv
net start wuauserv

Need serious help now, PLEASE

Noddy53 wrote:

> In DNS I use round robin for the 5 DownStream servers, they are all at
> diffrent sites on diffrent LAN's and in DNS are all known as WSUS.

To the best of my knowledge this is not a supported configuration. If you've
found some documentation suggesting that this should work, please provide a
reference.

Assuming the downstream servers have different fully-qualified DNS names, they
should probably work OK if you remove the round-robin setup. You might need to
uninstall and reinstall depending on how confused the servers have become.

Harry.

[Noddy53]

Thanks for the reply Harry.
We have used this approach using SUS, WSUS2.0 and now 3.0 and it is only now we are having a problem.
This approach is working on at least one of our sites.

"Noddy53" <Noddy53.2z1xjg@DoNotSpam.com> wrote in message
news:Noddy53.2z1xjg@DoNotSpam.com...

> We have used this approach using SUS, WSUS2.0 and now 3.0 and it is
> only now we are having a problem.
> This approach is working on at least one of our sites.

Round Robin DNS *will* work with replica servers for the purpose of
distributing approvals and content; however, you need to be acutely aware of
the ramifications as pertain to reporting. Because reporting is not
replicated horizontally, or downstream, the only reliable methodology of
obtaining reporting data is:

[a] On the master server =if= reporting rollup is enabled,
[b] On the replica server where the client last reported.


--
Lawrence Garvin, M.S., MCTS, MCP
MVP - Software Distribution (2005-2007)
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

Noddy53 wrote:

> In DNS I use round robin for the 5 DownStream servers, they are all at
> diffrent sites on diffrent LAN's and in DNS are all known as WSUS.

OK, this puzzles me for another reason. Surely if your servers are all at
different sites you would want the clients to connect to the server at their own
site, rather than a randomly chosen one?

Lawrence has pointed out that (within certain limits) round-robin DNS setups do
work, which knocks out my first theory, so I'll have another look. :-)

The relevant error code from the log is 0x80244008, "SOAP client failed to parse
a SOAP fault" which unfortunately seems uninformative. In combination with the
event log messages on the server I think we can conclude that the problem is at
the servers rather than the clients. Perhaps there might be more useful
information in the IIS logs?

Just in case it helps please run the client diagnostics tool on one of the
clients and post the results.

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

Just to be on the safe side, I'd like to doublecheck the DNS setup - does each
server (including the master server) have its own distinct fully-qualified DNS
name? Does each server /know/ it's own fully-qualified DNS name? There could
be issues if the name a server thinks belongs to it is has a round-robin entry
or points somewhere else.

> Out of 5 sites I only seem to have one that is working

OK, obvious question then - what is different about that one site?

Harry.

"Harry Johnston [MVP]" <harry@scms.waikato.ac.nz> wrote in message
news:eebmgTbGIHA.5208@TK2MSFTNGP04.phx.gbl...
> Noddy53 wrote:
>
>> In DNS I use round robin for the 5 DownStream servers, they are all at
>> diffrent sites on diffrent LAN's and in DNS are all known as WSUS.
>
> OK, this puzzles me for another reason. Surely if your servers are all at
> different sites you would want the clients to connect to the server at
> their own
> site, rather than a randomly chosen one?
>
> Lawrence has pointed out that (within certain limits) round-robin DNS
> setups do work, which knocks out my first theory, so I'll have another
> look. :-)


The missing component, which wasn't mentioned in the original post (or my
reply), is relevant to whether or not NetMasking is also in use. By default
it is (as is round robin when more than one 'A' record is configured), so
with NetMasking in force, a client system will *always* be directed to the
WSUS server on the local IP Subnet if one exists.

If there is no WSUS server on the local IP Subnet, then the queries will be
random among the servers -- and this is where the potential reporting issue
arises.


--
Lawrence Garvin, M.S., MCTS, MCP
MVP - Software Distribution (2005-2007)
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