WSUS Client won't report

[cookie_monster]

I'm having an odd one here or I’m missing something obvious.

 

I have a PC that stopped reporting to WSUS a while ago, I decided to reinstall Windows (XP SP3) to clear it up but it does the same. I had deleted it's account on the WSUS server then when I rebuilt it the account reappeared listed as 'Not yet reported' and that's how it's stayed.

I've just moved WSUS to a new server but didn't migrate the Db and slowly all clients have reappeared including the problem one but it in now listed as 'Not yest reported' again.

 

I've tried the usual forceupdate and reportnow commands and loads of other fixes that have worked before on other clients but it's still the same. The new WSUS (3.2.7600.226 on Server 2008 SP2) is working fine in every way as far as I can tell as was the only one, every client on the network appears and checks in.

 

This PC is identical to 30 others in the same room and I've tried it in a different switch.

 

Can anyone suggest anything else I can try?

 

Cheers.

[DrPerceptron]

Have you tried:

 

net stop wuauserv

REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f

REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f

REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f

net start wuauserv

wuauclt /resetauthorization /detectnow

 

Does anything significant appear in: %systemroot%\WindowsUpdate.log

[cookie_monster]

Yeh i've tried the script, I'll take a look at the WindowsUpdate.log tomorrow it takes quite a bit of time to look throught that log

[mac_shinobi]

Yeh i've tried the script, I'll take a look at the WindowsUpdate.log tomorrow it takes quite a bit of time to look throught that log

 

Format --> Word Wrap

 

Easier to read and then possibly the find function

[cookie_monster]

Format --> Word Wrap

 

Easier to read and then possibly the find function

 

 

 

Well yeh but what am I using the find function to find? If I remember right that log is generally full of esoteric information and error messages.

[mac_shinobi]

Well yeh but what am I using the find function to find? If I remember right that log is generally full of esoteric information and error messages.

 

 

How to read the Windowsupdate.log file

 

about half way down

 

Locating Failures in the log file

 

If you received a specific error message on the Windows Update Web site, follow these steps:

1. Open the Windowsupdate.log log file in Notepad.
   
2. On the Edit menu, click Find, and then search for the specific error message.
   

Note The Web site displays the final error message. This final error message may have been caused by a failure that is described earlier in the Windowsupdate.log log file. Additionally, if you do not know which error occurred on the Windows update Web site or you want to find more information about a failure by Automatic Updates, search for the following key words:

• FATAL
  
• WARNING
  

Note Not all warnings are critical errors. Start with the fatal errors and then work to the top of the Windowsupdate.log log file to make sure that you have identified the correct error message.

[cookie_monster]

Nice one I'll file that for after QCA exams tomorrow.

[meastaugh1]

I know you said you've tried all the usual, but just wanted to check that you'd downloaded the latest WUA and re-run wuauclt /detectnow /resetauthorization?

[cookie_monster]

I have the latest WUA but that's one cmd I haven't tried. I'll let you know.

[meastaugh1]

I have the latest WUA but that's one cmd I haven't tried. I'll let you know.

If you've got the latest version then that command won't help you because you've already run the batch file mentioned by DrPerception, which includes that command on the last line.

[cookie_monster]

It didn't help you're right.

 

I've looked at a working PC and the not working PC log and these are the differences. I might have to rebuild the PC again now the new WSUS is in place and see if that helps.

 

2009-11-19	09:13:19:786	 864	bdc	Report	Uploading 2 events using cached cookie, reporting URL = http://storm:8530/ReportingWebService/ReportingWebService.asmx
2009-11-19	09:13:22:067	 864	bdc	Report	WARNING: Failed to upload events to the server with hr = c00ce558.
2009-11-19	09:13:22:067	 864	bdc	PT	WARNING: ReportEventBatch failure, error = 0x80244016, soap client error = 10, soap error code = 0, HTTP status code = 400
2009-11-19	09:13:22:067	 864	bdc	Report	WARNING: Reporter failed to upload events with hr = 80244016.
2009-11-19	09:13:22:098	 864	bdc	Report	Uploading 2 events using cached cookie, reporting URL = http://storm:8530/ReportingWebService/ReportingWebService.asmx
2009-11-19	09:13:22:098	 864	bdc	Report	WARNING: Failed to upload events to the server with hr = c00ce558.
2009-11-19	09:13:22:098	 864	bdc	PT	WARNING: ReportEventBatch failure, error = 0x80244016, soap client error = 10, soap error code = 0, HTTP status code = 400
2009-11-19	09:13:22:098	 864	bdc	Report	WARNING: Reporter failed to upload events with hr = 80244016.
2009-11-19	09:13:30:286	 864	430	AU	Triggering AU detection through DetectNow API
2009-11-19	09:13:30:286	 864	430	AU	Triggering Online detection (non-interactive)

 

2009-11-19	09:13:45:661	 864	bdc	Report	REPORT EVENT: {4AB56E59-B6FF-4BEF-B7F1-D28824263DB5}	2009-11-19 09:13:40:661-0000	1	147	101	{00000000-0000-0000-0000-000000000000}	0	0	AutomaticUpdates	Success	Software Synchronization	Windows Update Client successfully detected 0 updates.
2009-11-19	09:13:45:661	 864	bdc	Report	REPORT EVENT: {1CCEF9FC-6DAE-4143-BD04-04ADC8ACD26A}	2009-11-19 09:13:40:661-0000	1	156	101	{00000000-0000-0000-0000-000000000000}	0	0	AutomaticUpdates	Success	Pre-Deployment Check	Reporting client status.

 

Got a few hits on google but nothing helpful so far.

 

I'll run the WSUS Client Diagnostic Tool as soon as I can get back on the client.

Edited November 19, 2009 by cookie_monster

[cookie_monster]

I think I'm down to another rebuild

 

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.4.7600.226. . . . . . . . . . . . PASS
               This version is WSUS 2.0

Checking AU Settings
       AU Option is 4: Scheduled Install . . . . . . . . . . . PASS
               Option is from Policy settings

Checking Proxy Configuration
       Checking for winhttp local machine Proxy settings . . . PASS
               Winhttp local machine access type
                       
               Winhttp local machine Proxy. . . . . . . . . .  NONE
               Winhttp local machine ProxyBypass. . . . . . .  NONE
       Checking User IE Proxy settings . . . . . . . . . . . . PASS

               User IE Proxy
               proxy.embc.uk.com:80
               User IE ProxyByPass
               *.*.*.*;*.embc.uk.com;
               User IE AutoConfig URL Proxy . . . . . . . . .  NONE
               User IE AutoDetect
               AutoDetect not in use

Checking Connection to WSUS/SUS Server
               WUServer = http://storm:8530
               WUStatusServer = http://storm:8530
       UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
       Connection to server. . . . . . . . . . . . . . . . . . PASS
       SelfUpdate folder is present. . . . . . . . . . . . . . PASS

[ricki]

HI

 

I know this will be a silly question but have you ghosted the machine and forgot to newsid of syspreped it.

 

Richard

[cookie_monster]

HI

 

I know this will be a silly question but have you ghosted the machine and forgot to newsid of syspreped it.

 

Richard

 

 

No this is a clean install and I've deleted the SUSID.

[TwoZeroAlpha]

I'm suffering the same issue. Of 32 PCs in a room 4 are not talking to WSUS any more. Strangely they were the first four to be picked up by the management console. I'll give the WUA and commands a whirl and report back.

 

Edit: Ok, run the latest WUA installer and wuauclt /detectnow /resetauthorization on two of my 4 that are playing up. They've moved from "Unassigned computers" to the correct group but are still showing as "not reported". So a partial success!

Edited November 24, 2009 by TwoZeroAlpha