Advertisement

04.02.2008 at 04:07PM PDT, ID: 23291226
[x]
Attachment Details

Our WSUS 3.0 SP1 server is not displaying any client machines.  What can we do to rectify this?

Asked by netmaster3620 in Microsoft Server, Windows XP Operating System, Windows Network Security Questions

Tags: Microsoft, WSUS, 3.0 SP1

We have upgraded to WSUS 3.0 SP1 after our WSUS 3.0 server stopped synchronizing Windows XP updates from Microsoft.  Even after the upgrade we were still experiencing the same issue.  After performing extensive troubleshooting I decided to completely uninstall WSUS including the database and I perform a complete re-install.  

We are now able to obtain Windows XP and all other updates however, none of our client machines are checking into the server.  Below are some of the things that I have done to troubleshoot the issue.  

1. On the client machines I ran the following command to force the machine to check into the WSUS server.  
   
wuauclt.exe /resetauthorization /detectnow

3.After running the command the client did not show up on the WSUS server. I looked at the error logs on the WSUS Server and I saw corresponding error logs that read.  (Additional Detail in attached IIS-log.txt file)

/ClientWebService/client.asmx - 80 - 10.127.4.180 Windows-Update-Agent 404 2 1260

2.  I then looked at the C:\WINDOWS\WindowsUpdate.log file on the client machine.  I noticed the following errors in the log.  

---------------------------------------------------------------------------------------------------------------------------
2008-04-02      17:35:13:115      1880      4f8      AU      Setting AU scheduled install time to 2008-04-03 07:00:00
2008-04-02      17:35:13:130      1820      1be4      CltUI      AU client got new directive = 'Shutdown', serviceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, return = 0x00000000
2008-04-02      17:35:13:365      1880      d10      AU      AU received handle event
2008-04-02      17:35:18:115      1880      2cc      Report      REPORT EVENT: {D5D9B4A7-FB6C-4AE8-A657-5C41627BF63E}      2008-04-02 17:35:13:115-0400      1      161      101      {238493F6-6D43-4ECB-A4E9-EB63CA49EC87}      100      80244019      AutomaticUpdates      Failure      Content Download      Error: Download failed.
2008-04-02      17:52:45      6136      17cc      Misc      ===========  Logging initialized (build: 5.8.0.2694, tz: -0400)  ===========
2008-04-02      17:52:45      6136      17cc      Misc        = Process: c:\14b203ad0e80732a14d1b4e8ae\wusetup.exe
2008-04-02      17:52:45      6136      17cc      Setup      Windows Update Client standalone setup : resource dll path is c:\14b203ad0e80732a14d1b4e8ae\en\wusetupr.dll
2008-04-02      17:52:45      6136      17cc      Setup      ***********  Setup: Checking whether self-update is required  ***********
2008-04-02      17:52:45      6136      17cc      Setup        * Inf file: c:\14b203ad0e80732a14d1b4e8ae\wusetup.inf
2008-04-02      17:52:45      6136      17cc      Setup      Update NOT required for C:\WINDOWS\system32\cdm.dll: target version = 7.1.6001.65, required version = 5.8.0.2694
2008-04-02      17:52:45      6136      17cc      Setup      Update required for C:\WINDOWS\system32\iuengine.dll: target version = 5.8.0.2469, required version = 5.8.0.2694
2008-04-02      17:52:45      6136      17cc      Setup      Update NOT required for C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wuapi.dll\7.1.6001.65\wuapi.dll: target version = 7.1.6001.65, required version = 5.8.0.2694
2008-04-02      17:52:45      6136      17cc      Setup      Update NOT required for C:\WINDOWS\system32\wuauclt.exe: target version = 7.1.6001.65, required version = 5.8.0.2694
2008-04-02      17:52:45      6136      17cc      Setup      Update required for C:\WINDOWS\system32\wuauclt1.exe: target version = 5.8.0.2469, required version = 5.8.0.2694
2008-04-02      17:52:45      6136      17cc      Setup      Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.1.6001.65, required version = 5.8.0.2694
2008-04-02      17:52:45      6136      17cc      Setup      Update NOT required for C:\WINDOWS\system32\wuaueng.dll: target version = 7.1.6001.65, required version = 5.8.0.2694
2008-04-02      17:52:45      6136      17cc      Setup      Update required for C:\WINDOWS\system32\wuaueng1.dll: target version = 5.8.0.2469, required version = 5.8.0.2694
2008-04-02      17:52:45      6136      17cc      Setup      Update NOT required for C:\WINDOWS\system32\wucltui.dll: target version = 7.1.6001.65, required version = 5.8.0.2694
2008-04-02      17:52:45      6136      17cc      Setup      Update NOT required for C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wups.dll\7.1.6001.65\wups.dll: target version = 7.1.6001.65, required version = 5.8.0.2694
2008-04-02      17:52:45      6136      17cc      Setup      Update NOT required for C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wups2.dll\7.1.6001.65\wups2.dll: target version = 7.1.6001.65, required version = 5.8.0.2694
2008-04-02      17:52:45      6136      17cc      Setup      Update NOT required for C:\WINDOWS\system32\wuweb.dll: target version = 7.0.6000.381, required version = 5.8.0.2694
2008-04-02      17:52:45      6136      17cc      Setup        * IsUpdateRequired = Yes
2008-04-02      17:52:45      6136      17cc      Setup      Windows Update Client standalone setup : eula file path is c:\14b203ad0e80732a14d1b4e8ae\en\eula.rtf
2008-04-02      18:01:40:787      1880      1be4      PT      WARNING: Cached cookie has expired or new PID is available
2008-04-02      18:01:40:787      1880      1be4      PT      Initializing simple targeting cookie, clientId = 001eae92-42b7-4e2f-b97a-99a16b3bb344, target group = , DNS name = jarmstrong.bcc.local
2008-04-02      18:01:40:787      1880      1be4      PT        Server URL = http://sus.bcc.local/SimpleAuthWebService/SimpleAuth.asmx
2008-04-02      18:01:40:802      1880      1be4      PT      WARNING: GetAuthorizationCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
2008-04-02      18:01:40:802      1880      1be4      PT      WARNING: Failed to initialize Simple Targeting Cookie: 0x80244019
2008-04-02      18:01:40:802      1880      1be4      PT      WARNING: PopulateAuthCookies failed: 0x80244019
2008-04-02      18:01:40:802      1880      1be4      PT      WARNING: RefreshCookie failed: 0x80244019
2008-04-02      18:01:40:802      1880      1be4      PT      WARNING: RefreshPTState failed: 0x80244019
2008-04-02      18:01:40:802      1880      1be4      PT      WARNING: PTError: 0x80244019
2008-04-02      18:01:40:802      1880      1be4      Report      WARNING: Reporter failed to upload events with hr = 80244019.
2008-04-02      18:23:36:053      1880      dc4      PT      WARNING: Cached cookie has expired or new PID is available
2008-04-02      18:23:36:053      1880      dc4      PT      Initializing simple targeting cookie, clientId = 001eae92-42b7-4e2f-b97a-99a16b3bb344, target group = , DNS name = jarmstrong.bcc.local
2008-04-02      18:23:36:053      1880      dc4      PT        Server URL = http://sus.bcc.local/SimpleAuthWebService/SimpleAuth.asmx
2008-04-02      18:23:36:069      1880      dc4      PT      WARNING: GetAuthorizationCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
2008-04-02      18:23:36:069      1880      dc4      PT      WARNING: Failed to initialize Simple Targeting Cookie: 0x80244019
2008-04-02      18:23:36:069      1880      dc4      PT      WARNING: PopulateAuthCookies failed: 0x80244019
2008-04-02      18:23:36:069      1880      dc4      PT      WARNING: RefreshCookie failed: 0x80244019
2008-04-02      18:23:36:069      1880      dc4      PT      WARNING: RefreshPTState failed: 0x80244019
2008-04-02      18:23:36:069      1880      dc4      PT      WARNING: PTError: 0x80244019
2008-04-02      18:23:36:069      1880      dc4      Report      WARNING: Reporter failed to upload events with hr = 80244019.
------------------------------------------------------------------------------------------------------------------------------

PLEASE NOTE:
This issue is not related to Group Policy problems as our WSUS server was fully functioning prior to this.  

Any help would be greatly appreciated.  
Start Free Trial
Attachments:
 
IIS Error log from WSUS Server
 
[+][-]04.02.2008 at 04:17PM PDT, ID: 21268438

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 7-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]04.02.2008 at 04:59PM PDT, ID: 21268663

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 7-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]04.02.2008 at 05:12PM PDT, ID: 21268726

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 7-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]04.02.2008 at 05:40PM PDT, ID: 21268837

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: Microsoft Server, Windows XP Operating System, Windows Network Security Questions
Tags: Microsoft, WSUS, 3.0 SP1
Sign Up Now!
Solution Provided By: Brainstormer
Participating Experts: 2
Solution Grade: B
 
 
 
Loading Advertisement...
20080716-EE-VQP-32 / EE_QW_2_20070628