WSUS clients not being seen...

[pmaths]

I'm having an issue with five of our Windows XP PC's where, when viewed on the WSUS console, they appear with the details "The computer has not responded yet". Our version of WSUS is 2.0.0.2620, which sits on a Windows 2000 server. I currently have another 100+ XP PC's connected to WSUS with no issues.

I've done a fair amount of trawlling the net and so far I have tried:

If I check the windows update log file, I see the follow relevant information from running wuauclt /resetauthorization /detectnow

2010-07-08 15:58:09+0100 1744 dd4 Triggering AU detection through DetectNow api
2010-07-08 15:58:09+0100 1744 e9c AU received event of 1
2010-07-08 15:58:09+0100 1744 e9c WU client succeeds CClientCallRecorder::BeginFindUpdates from AutomaticUpdates with call id {633E0512-3834-4FE8-A5D8-985A7F5213D1}
2010-07-08 15:58:09+0100 1744 14c WU client executing call {633E0512-3834-4FE8-A5D8-985A7F5213D1} of type Search Call
2010-07-08 15:58:10+0100 1940 d44 Trying to make out of proc datastore active
2010-07-08 15:58:10+0100 1744 14c DownloadFileInternal failed for

http://riker:8530/SelfUpdate/wuident.cab:

error 0x80190194
2010-07-08 15:58:10+0100 1744 14c IsUpdateRequired failed with error 0x80244019
2010-07-08 15:58:10+0100 1940 d44 Out of proc datastore is now active
2010-07-08 15:58:10+0100 1744 14c PT: Using serverID {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2010-07-08 15:58:10+0100 1744 14c WU client failed Searching for update with error 0x80248008
2010-07-08 15:58:10+0100 1744 14c Search Callback Failed, hr is 0x80248008
2010-07-08 15:58:10+0100 1744 14c Setting next AU detection timeout to 2010-07-08 18:39:34
2010-07-08 15:58:10+0100 1744 14c WU client calls back to search call AutomaticUpdates with code Call failed and error 0x80248008
2010-07-08 15:58:10+0100 1744 14c WU client completed and deleted call {633E0512-3834-4FE8-A5D8-985A7F5213D1}
2010-07-08 15:58:15+0100 1744 14c REPORT EVENT: {36C43B30-F3F2-4AE4-86FF-5588C2F0EA33} 223 2010-07-08 15:58:10+0100 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 0 80244019 SelfUpdate Failure Software Synchronization Error: Agent failed detecting with reason: 0x80244019
2010-07-08 15:58:15+0100 1744 14c REPORT EVENT: {BF4F180E-D92F-46F4-A736-F123BC16E4CC} 224 2010-07-08 15:58:10+0100 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248008 AutomaticUpdates Failure Software Synchronization Error: Agent failed detecting with reason: 0x80248008
2010-07-08 15:58:15+0100 1744 14c Created new event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{195E545E-E56B-4D20-A384-05AE7199F41B}.bin for writing.
2010-07-08 15:59:38+0100 1744 14c Successfully opened event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{D6AC707C-7492-4561-A06D-9A993C39F151}.bin for reading.
2010-07-08 15:59:38+0100 1744 14c PT: Using serverID {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2010-07-08 15:59:38+0100 1744 14c Failed to obtain cached cookie with hr = 80248008.
2010-07-08 15:59:38+0100 1744 14c Failed to upload events with hr = 80248008.

Searching on the error No 0x80244019, I've checked a few things in the servers IIS console, all of which checkout fine.

If I run the WSUS client diag on one of the client PC's, I get the following error:

WinHttpDownloadFileToMemory(szURLDest, NULL, 0, NULL, NULL, NULL, &downloadBuffer) failed with hr=0x80190194 (null)

With this error in mind, I've tried stoping windows update services on the PC, renaming the software distribution folder and restarting the update services to recreate the renamed folder. This did little to help.

I'm starting to struggle to find any sort of resolution to this, so if anyone can advise it will be very gratefully received.

Cheers

 

[goombawaho]

Can you import (from a known working XP machine) or at least verify the variables in the WSUS registry settings on the machines that are having a problem?

http://technet.microsoft.com/en-us/library/cc708449(WS.10).aspx

It has to be a setting IF there is network connectivity between the workstations and the WSUS server.

 

[pmaths]

Hi,

Sorry, I should have mentioned. Windows updates are set by group policy.

I've examined the registry entries that you highlighted and both a good and bad PC have the same registry settings.

Interestingly, if I point the bad PC to windows updates via the internet and not our WSUS server, I get a whole different problem. The error I get here is 0x8024d007

Im still very much at a loss on this but will keep plugging away.

Any help will gratefully be received.

 

[rodjor23]

Try stopping the Windows Update Service, deleting the c:\windows\softwaredistribution folder and restarting the Windows Update Service and running wuauclt.exe /detectnow. I have experienced this in the past and it has fixed the problem.

 

[pmaths]

Hi Rodjor23,

Unfortunatly I've already tried this and no joy...

 

[goombawaho]

Format?? Re-image?? There are dedicated WSUS forums for these tricky problems.

 

[Lemon13]

http://support.microsoft.com/kb/956701/en

M. Knorr

MCSE, MCTS, MCSA, CCNA