Some Clients not reporting to WSUS

I have a large # of clients that are not reporting to a new WSUS server.  This server is a downstream server and is version 3.2  I have had no issues with clients reporting to other WSUS servers and some clients are reporting normally this new WSUS server.

I have cleared the SUSClientID value and ran a "wuauclt.exe /resetauthorization /detectnow" command.  I'm still getting the following error:

2011-03-30      11:21:53:843      1512      534      Service      *************
2011-03-30      11:21:53:875      1512      534      Service      ** START **  Service: Service startup
2011-03-30      11:21:53:875      1512      534      Service      *********
2011-03-30      11:21:55:484      1512      534      Agent        * WU client version 7.4.7600.226
2011-03-30      11:21:55:484      1512      534      Agent        * Base directory: C:\WINDOWS\SoftwareDistribution
2011-03-30      11:21:55:500      1512      534      Agent        * Access type: No proxy
2011-03-30      11:21:55:500      1512      534      Agent        * Network state: Connected
2011-03-30      11:22:44:394      1512      534      Agent      ***********  Agent: Initializing Windows Update Agent  ***********
2011-03-30      11:22:44:394      1512      534      Agent      ***********  Agent: Initializing global settings cache  ***********
2011-03-30      11:22:44:394      1512      534      Agent        * WSUS server: http://wsus.domain.local
2011-03-30      11:22:44:394      1512      534      Agent        * WSUS status server: http://wsus.domain.local
2011-03-30      11:22:44:394      1512      534      Agent        * Target group: (Unassigned Computers)
2011-03-30      11:22:44:394      1512      534      Agent        * Windows Update access disabled: No
2011-03-30      11:22:44:455      1512      534      DnldMgr      Download manager restoring 0 downloads
2011-03-30      11:22:44:563      1512      534      AU      ###########  AU: Initializing Automatic Updates  ###########
2011-03-30      11:22:44:563      1512      534      AU      AU setting next sqm report timeout to 2011-03-30 15:22:44
2011-03-30      11:22:44:563      1512      534      AU        # WSUS server: http://wsus.domain.local
2011-03-30      11:22:44:563      1512      534      AU        # Detection frequency: 22
2011-03-30      11:22:44:563      1512      534      AU        # Approval type: Scheduled (Policy)
2011-03-30      11:22:44:563      1512      534      AU        # Scheduled install day/time: Every day at 3:00
2011-03-30      11:22:44:563      1512      534      AU        # Auto-install minor updates: Yes (Policy)
2011-03-30      11:22:44:609      1512      534      AU      Setting AU scheduled install time to 2011-03-31 07:00:00
2011-03-30      11:22:44:609      1512      534      AU      Initializing featured updates
2011-03-30      11:22:44:655      1512      534      AU      Found 0 cached featured updates
2011-03-30      11:22:44:655      1512      534      AU      AU finished delayed initialization
2011-03-30      11:22:48:361      1512      534      Report      ***********  Report: Initializing static reporting data  ***********
2011-03-30      11:22:48:361      1512      534      Report        * OS Version = 5.1.2600.3.0.65792
2011-03-30      11:22:48:592      1512      534      Report        * Computer Brand = Equus Computer Systems
2011-03-30      11:22:48:592      1512      534      Report        * Computer Model = Nobilis
2011-03-30      11:22:48:607      1512      534      Report        * Bios Revision = PRG3110H.86A.0066.2009.0518.1206
2011-03-30      11:22:48:607      1512      534      Report        * Bios Name = BIOS Date: 10/22/08 19:07:50 Ver: 08.00.10
2011-03-30      11:22:48:607      1512      534      Report        * Bios Release Date = 2009-05-18T00:00:00
2011-03-30      11:22:48:607      1512      534      Report        * Locale ID = 1033
2011-03-30      11:22:53:651      1512      c44      PT      WARNING: Cached cookie has expired or new PID is available
2011-03-30      11:22:53:651      1512      c44      PT      Initializing simple targeting cookie, clientId = , target group = , DNS name = pc.domain.local
2011-03-30      11:22:53:651      1512      c44      PT        Server URL = http://wsus.domain.local/SimpleAuthWebService/SimpleAuth.asmx
2011-03-30      11:22:57:419      1512      c44      PT      WARNING: GetAuthorizationCookie failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200
2011-03-30      11:22:57:419      1512      c44      PT      WARNING: SOAP Fault: 0x000190
2011-03-30      11:22:57:419      1512      c44      PT      WARNING:     faultstring:Fault occurred
2011-03-30      11:22:57:419      1512      c44      PT      WARNING:     ErrorCode:InternalServerError(5)
2011-03-30      11:22:57:419      1512      c44      PT      WARNING:     Message:(null)
2011-03-30      11:22:57:419      1512      c44      PT      WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/SimpleAuthWebService/GetAuthorizationCookie"
2011-03-30      11:22:57:434      1512      c44      PT      WARNING:     ID:c1fd7980-317a-4a58-a8dd-ce3f6f4ed5fd
2011-03-30      11:22:57:434      1512      c44      PT      WARNING: Failed to initialize Simple Targeting Cookie: 0x8024400e
2011-03-30      11:22:57:434      1512      c44      PT      WARNING: PopulateAuthCookies failed: 0x8024400e
2011-03-30      11:22:57:434      1512      c44      PT      WARNING: RefreshCookie failed: 0x8024400e
2011-03-30      11:22:57:434      1512      c44      PT      WARNING: RefreshPTState failed: 0x8024400e
2011-03-30      11:22:57:434      1512      c44      PT      WARNING: PTError: 0x8024400e
2011-03-30      11:22:57:434      1512      c44      Report      WARNING: Reporter failed to upload events with hr = 8024400e.
2011-03-30      11:22:57:480      1512      c44      PT      WARNING: Cached cookie has expired or new PID is available
2011-03-30      11:22:57:480      1512      c44      PT      Initializing simple targeting cookie, clientId = , target group = , DNS name = pc.domain.local
2011-03-30      11:22:57:480      1512      c44      PT        Server URL = http://wsus.domain.local/SimpleAuthWebService/SimpleAuth.asmx
2011-03-30      11:22:57:480      1512      c44      PT      WARNING: GetAuthorizationCookie failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200
2011-03-30      11:22:57:480      1512      c44      PT      WARNING: SOAP Fault: 0x000190
2011-03-30      11:22:57:480      1512      c44      PT      WARNING:     faultstring:Fault occurred
2011-03-30      11:22:57:480      1512      c44      PT      WARNING:     ErrorCode:InternalServerError(5)
2011-03-30      11:22:57:480      1512      c44      PT      WARNING:     Message:(null)
2011-03-30      11:22:57:480      1512      c44      PT      WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/SimpleAuthWebService/GetAuthorizationCookie"
2011-03-30      11:22:57:480      1512      c44      PT      WARNING:     ID:84a502b4-37fc-4035-a682-ee61ef52f937
2011-03-30      11:22:57:480      1512      c44      PT      WARNING: Failed to initialize Simple Targeting Cookie: 0x8024400e
2011-03-30      11:22:57:496      1512      c44      PT      WARNING: PopulateAuthCookies failed: 0x8024400e
2011-03-30      11:22:57:496      1512      c44      PT      WARNING: RefreshCookie failed: 0x8024400e
2011-03-30      11:22:57:496      1512      c44      PT      WARNING: RefreshPTState failed: 0x8024400e
2011-03-30      11:22:57:496      1512      c44      PT      WARNING: PTError: 0x8024400e
2011-03-30      11:22:57:496      1512      c44      Report      WARNING: Reporter failed to upload events with hr = 8024400e.
2011-03-30      11:22:57:542      1512      c44      PT      WARNING: Cached cookie has expired or new PID is available
2011-03-30      11:22:57:542      1512      c44      PT      Initializing simple targeting cookie, clientId = , target group = , DNS name = pc.domain.local
2011-03-30      11:22:57:542      1512      c44      PT        Server URL = http://wsus.domain.local/SimpleAuthWebService/SimpleAuth.asmx
2011-03-30      11:22:57:542      1512      c44      PT      WARNING: GetAuthorizationCookie failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200
2011-03-30      11:22:57:542      1512      c44      PT      WARNING: SOAP Fault: 0x000190
2011-03-30      11:22:57:542      1512      c44      PT      WARNING:     faultstring:Fault occurred
2011-03-30      11:22:57:542      1512      c44      PT      WARNING:     ErrorCode:InternalServerError(5)
2011-03-30      11:22:57:557      1512      c44      PT      WARNING:     Message:(null)
2011-03-30      11:22:57:557      1512      c44      PT      WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/SimpleAuthWebService/GetAuthorizationCookie"
2011-03-30      11:22:57:557      1512      c44      PT      WARNING:     ID:e31c52b3-f1ca-4164-95d1-a32c1f20ad1a
2011-03-30      11:22:57:557      1512      c44      PT      WARNING: Failed to initialize Simple Targeting Cookie: 0x8024400e
2011-03-30      11:22:57:557      1512      c44      PT      WARNING: PopulateAuthCookies failed: 0x8024400e
2011-03-30      11:22:57:557      1512      c44      PT      WARNING: RefreshCookie failed: 0x8024400e
2011-03-30      11:22:57:557      1512      c44      PT      WARNING: RefreshPTState failed: 0x8024400e
2011-03-30      11:22:57:557      1512      c44      PT      WARNING: PTError: 0x8024400e
2011-03-30      11:22:57:557      1512      c44      Report      WARNING: Reporter failed to upload events with hr = 8024400e.
Kram80Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DonNetwork AdministratorCommented:
0
Kram80Author Commented:
I don't think this pertains since I'm not using a load balancer.  The clients contact the downstream server, which has it's own updates database.  

I'm leaning towards the issue on the client end, since some clients seem to be reporting without any issue.
0
Defend Against the Q2 Top Security Threats

Were you aware that overall malware worldwide was down a surprising 42% from Q1'18? Every quarter, the WatchGuard Threat Lab releases an Internet Security Report that analyzes the top threat trends impacting companies worldwide. Learn more by viewing our on-demand webinar today!

Kram80Author Commented:
Interesting second comment, you may be on to something....let me read a little further.
0
Kram80Author Commented:
Ok, I think I found the solution.  I thought the Office 2003 comment was going to be the magic bullet, but it wasn't.  What worked was the following, and I grabbed it from this posting:  http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_23999510.html  

. At the client, shutdown Automatic Updates service.
. At the client, use bitsadmin to check the BITS queue, and flush it if there's anything there.
. At the client, make a backup of the %windir%\SoftwareDistribution folder and all subfolders and the %windir%\WindowsUpdate.log file.
. At the client, purge the following folders of all content:
       %windir%\SoftwareDistribution\Datastore\Logs\edb*.*
        %windir%\SoftwareDistribution\Datastore\DataStore.edb
        %windir%\SoftwareDistribution\Download
        %windir%\SoftwareDistribution\EventCache
and delete the following files:
        %windir%\SoftwareDistribution\ReportingEvents.log
        %windir%\WindowsUpdate.log

. At the client, delete the three values in the registry key at:
    HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate

Tried it on 4 PCs and it has worked on all of them.  Just need to script it out....

Thank you for your input, I do appreciate it.
0
DonNetwork AdministratorCommented:
note:

". At the client, make a backup of the %windir%\SoftwareDistribution folder and all subfolders and the %windir%\WindowsUpdate.log file."

this is unnecessary

"rd /s /q %windir%\softwareDistribution" would take care in one swoop

the directory gets recreated on the next detection cycle
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Kram80Author Commented:
could you explain the rd /s /q?
0
DonNetwork AdministratorCommented:
Oh, and the script that I posted in that thread (Long ago) does that as well.
0
Kram80Author Commented:
Didn't even notice you were part of that thread.  Let me take a look at that script.  I may have questions about it, mind if I ask?
0
DonNetwork AdministratorCommented:
/s  <<include subfolders

/q  <<quiet mode
0
DonNetwork AdministratorCommented:
It was a all inclusive script that reset the susclient ID(in case imaging of pc's was used) then re-registered appropriate DLL's and then reinstalled the latest windows update agent.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.