We help IT Professionals succeed at work.

WSUS 3.0 Client Connectivity Issues

5,273 Views
Last Modified: 2013-12-05
We've started using WSUS 3.0, and none of my clients are showing up as expected.  All have different SID's and I have performed a series of troubleshooting steps.  Please see below for more detailed info.  Any and all help is always appreciated.  

Here's what I've done and tested:
1.) GPO works
a. set to correct server, with correct port.
2.) Going to http://wsusserver/iuident.cab works.
3.) Ran the wsus client diagnostic tool.  (Pass all the way around)
4.) Ran the gpupdate /force and wuauclt /detectnow
a. See errors below from windowsupdate.log from local workstation (cleaned of company info)

2007-10-01 11:26:07:042 1800 768 Agent *********** Agent: Refreshing global settings cache ***********
2007-10-01 11:26:07:042 1800 768 Agent * WSUS server: http://wsusserver/ (Changed)
2007-10-01 11:26:07:042 1800 768 Agent * WSUS status server: http://wsusserver/ (Changed)
2007-10-01 11:26:07:042 1800 768 Agent * Target group: http://wsusserver/ (Unchanged)
2007-10-01 11:26:07:042 1800 768 Agent * Windows Update access disabled: No (Unchanged)
2007-10-01 11:26:07:042 1800 768 AU AU received policy change subscription event
2007-10-01 11:26:07:058 1800 768 AU Sus server changed through policy.
2007-10-01 11:26:07:073 1800 768 AU AU Refresh required....
2007-10-01 11:26:07:089 1800 768 AU AU setting next detection timeout to 2007-10-01 16:26:07
2007-10-01 11:26:07:104 1800 768 AU Triggering Online detection (non-interactive)
2007-10-01 11:26:07:104 1800 768 AU #############
2007-10-01 11:26:07:104 1800 768 AU ## START ## AU: Search for updates
2007-10-01 11:26:07:104 1800 768 AU #########
2007-10-01 11:26:07:104 1800 768 AU <<## SUBMITTED ## AU: Search for updates [CallId = {1A9001A9-9F23-4793-BC6B-D8FB65A5237A}]
2007-10-01 11:26:07:104 1800 4858 Agent *************
2007-10-01 11:26:07:104 1800 4858 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2007-10-01 11:26:07:104 1800 4858 Agent *********
2007-10-01 11:26:07:104 1800 4858 Agent * Online = Yes; Ignore download priority = No
2007-10-01 11:26:07:104 1800 4858 Agent * Criteria = "IsHidden=0 and IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and IsAssigned=1 or IsHidden=0 and IsInstalled=1 and DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and IsAssigned=1 and RebootRequired=1"
2007-10-01 11:26:07:104 1800 4858 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2007-10-01 11:26:07:104 1800 4858 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2007-10-01 11:26:07:136 1800 4858 Misc Microsoft signed: Yes
2007-10-01 11:26:18:370 1800 4858 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2007-10-01 11:26:18:370 1800 4858 Misc Microsoft signed: Yes
2007-10-01 11:26:18:386 1800 4858 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
2007-10-01 11:26:18:401 1800 4858 Misc Microsoft signed: Yes
2007-10-01 11:26:18:401 1800 4858 Setup *********** Setup: Checking whether self-update is required ***********
2007-10-01 11:26:18:401 1800 4858 Setup * Inf file: C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
2007-10-01 11:26:18:433 1800 4858 Setup Update NOT required for C:\WINDOWS\system32\cdm.dll: target version = 7.0.6000.374, required version = 7.0.6000.374
2007-10-01 11:26:18:448 1800 4858 Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll: target version = 7.0.6000.374, required version = 7.0.6000.374
2007-10-01 11:26:18:479 1800 4858 Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.0.6000.374, required version = 7.0.6000.374
2007-10-01 11:26:18:479 1800 4858 Setup Update NOT required for C:\WINDOWS\system32\wuauclt.exe: target version = 7.0.6000.374, required version = 7.0.6000.374
2007-10-01 11:26:18:495 1800 4858 Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.0.6000.374, required version = 7.0.6000.374
2007-10-01 11:26:18:526 1800 4858 Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.0.6000.374, required version = 7.0.6000.374
2007-10-01 11:26:18:542 1800 4858 Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll: target version = 7.0.6000.374, required version = 7.0.6000.374
2007-10-01 11:26:18:573 1800 4858 Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.0.6000.374, required version = 7.0.6000.374
2007-10-01 11:26:18:589 1800 4858 Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll: target version = 7.0.6000.374, required version = 7.0.6000.374
2007-10-01 11:26:18:651 1800 4858 Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.0.6000.374, required version = 7.0.6000.374
2007-10-01 11:26:18:683 1800 4858 Setup Update NOT required for C:\WINDOWS\system32\wups.dll: target version = 7.0.6000.374, required version = 7.0.6000.374
2007-10-01 11:26:18:698 1800 4858 Setup Update NOT required for C:\WINDOWS\system32\wups2.dll: target version = 7.0.6000.374, required version = 7.0.6000.374
2007-10-01 11:26:18:714 1800 4858 Setup Update NOT required for C:\WINDOWS\system32\wuweb.dll: target version = 7.0.6000.374, required version = 7.0.6000.374
2007-10-01 11:26:18:714 1800 4858 Setup * IsUpdateRequired = No
2007-10-01 11:26:20:120 1800 4858 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2007-10-01 11:26:20:120 1800 4858 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsusserver/ClientWebService/client.asmx
2007-10-01 11:26:21:167 1800 4858 PT WARNING: Cached cookie has expired or new PID is available
2007-10-01 11:26:21:167 1800 4858 PT Initializing simple targeting cookie, clientId = 539e5fd5-e628-487a-b199-159e66cb7f47, target group = http://wsusserver/, DNS name = machine.domain.com
2007-10-01 11:26:21:167 1800 4858 PT Server URL = http://wsusserver/SimpleAuthWebService/SimpleAuth.asmx
2007-10-01 11:26:21:229 1800 4858 PT WARNING: GetAuthorizationCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
2007-10-01 11:26:21:229 1800 4858 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80244019
2007-10-01 11:26:21:229 1800 4858 PT WARNING: PopulateAuthCookies failed: 0x80244019
2007-10-01 11:26:21:229 1800 4858 PT WARNING: RefreshCookie failed: 0x80244019
2007-10-01 11:26:21:229 1800 4858 PT WARNING: RefreshPTState failed: 0x80244019
2007-10-01 11:26:21:229 1800 4858 PT WARNING: Sync of Updates: 0x80244019
2007-10-01 11:26:21:229 1800 4858 PT WARNING: SyncServerUpdatesInternal failed: 0x80244019
2007-10-01 11:26:21:229 1800 4858 Agent * WARNING: Failed to synchronize, error = 0x80244019
2007-10-01 11:26:21:339 1800 4858 Agent * WARNING: Exit code = 0x80244019
2007-10-01 11:26:21:339 1800 4858 Agent *********
2007-10-01 11:26:21:339 1800 4858 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2007-10-01 11:26:21:339 1800 4858 Agent *************
2007-10-01 11:26:21:339 1800 4858 Agent WARNING: WU client failed Searching for update with error 0x80244019
Comment
Watch Question

Commented:
Try typing (regsvr32 msxml3.dll   ) on one of the clients then (wuauclt.exe /detectnow ) and see if it registers correctly in WSUS.

Author

Commented:
Doesn't look like anything changed...

2007-10-01      13:45:22:215      1800      45dc      PT      WARNING: Cached cookie has expired or new PID is available
2007-10-01      13:45:22:215      1800      45dc      PT      Initializing simple targeting cookie, clientId = 539e5fd5-e628-487a-b199-159e66cb7f47, target group = http://wsusserver/, DNS name = machine.domain.com
2007-10-01      13:45:22:215      1800      45dc      PT        Server URL = http://wsus/SimpleAuthWebService/SimpleAuth.asmx
2007-10-01      13:45:22:215      1800      45dc      PT      WARNING: GetAuthorizationCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
2007-10-01      13:45:22:215      1800      45dc      PT      WARNING: Failed to initialize Simple Targeting Cookie: 0x80244019
2007-10-01      13:45:22:215      1800      45dc      PT      WARNING: PopulateAuthCookies failed: 0x80244019
2007-10-01      13:45:22:215      1800      45dc      PT      WARNING: RefreshCookie failed: 0x80244019
2007-10-01      13:45:22:215      1800      45dc      PT      WARNING: RefreshPTState failed: 0x80244019
2007-10-01      13:45:22:215      1800      45dc      PT      WARNING: Sync of Updates: 0x80244019
2007-10-01      13:45:22:215      1800      45dc      PT      WARNING: SyncServerUpdatesInternal failed: 0x80244019
2007-10-01      13:45:22:215      1800      45dc      Agent        * WARNING: Failed to synchronize, error = 0x80244019
2007-10-01      13:45:22:247      1800      45dc      Agent        * WARNING: Exit code = 0x80244019
2007-10-01      13:45:22:247      1800      45dc      Agent      *********
2007-10-01      13:45:22:247      1800      45dc      Agent      **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2007-10-01      13:45:22:247      1800      45dc      Agent      *************
2007-10-01      13:45:22:247      1800      45dc      Agent      WARNING: WU client failed Searching for update with error 0x80244019
2007-10-01      13:45:22:247      1800      45d0      AU      >>##  RESUMED  ## AU: Search for updates [CallId = {E3A910A9-349C-4B79-8016-EC97D65F12CD}]
2007-10-01      13:45:22:247      1800      45d0      AU        # WARNING: Search callback failed, result = 0x80244019
2007-10-01      13:45:22:247      1800      45d0      AU        # WARNING: Failed to find updates with error code 80244019
2007-10-01      13:45:22:247      1800      45d0      AU      #########
2007-10-01      13:45:22:247      1800      45d0      AU      ##  END  ##  AU: Search for updates [CallId = {E3A910A9-349C-4B79-8016-EC97D65F12CD}]
2007-10-01      13:45:22:247      1800      45d0      AU      #############
2007-10-01      13:45:22:247      1800      45d0      AU      AU setting next detection timeout to 2007-10-01 23:45:22
2007-10-01      13:45:22:247      1800      45d0      AU      Setting AU scheduled install time to 2007-10-04 03:00:00

Commented:
WSUS is usually installed at a specific port (8530 by default I think).  Make sure the WSUS configuration includes the port along with the url (http://WSUS:8350)

Author

Commented:
I have tried specifying 8530, 80, and just server name, and still come up with the same errors.  I can change my GP, run the force, and another detectnow if you would like to see the logs after that?  Let me know.  Otherwise, note that I have tried that.  :-)

Commented:
have you tried manually configuring a client to see if WSUS is working at all?

Author

Commented:
I definitively say no, since I'm not aware of how to manually configure a client.  Do you have a link I could follow?  
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
That did the trick.  What I don't understand is why, since I was sure to run newsid.exe on all of our workstations after imaging them.  Do you have any insight?  Is this a WSUS only SID that needs to be regenerated on all of our machines?  Oh, and thanks for you help!!!

Commented:
I believe that it is a Windows Update specific SID.

Author

Commented:
I may have spoken slightly too soon...  I did the same on a different machine, and still the same errors come up.  Any further suggestions?

Commented:
Did you register the msxml3.dll as well?

Author

Commented:
Sure did.  I just went back and checked the logs on the original machine (mine), and SOAP errors came back when I did another detectnow.  I'm really beginning to dislike WSUS 3.0.  We never had these problems with 2.x.  

Author

Commented:
I found it!!!  Score one for the home team!  See the below link.

http://support.microsoft.com/kb/923507/

Apparently, SP1 on 2K3 didn't play well with WSUS.  Or at least was tossing out the wrong SOAP packet.  I really hope that this helps someone else in the future!!  Thanks for your help smilerz!  Without your fixes it still didn't work, so I am glad I awarded you the points!!

Commented:
glad to help
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.