AboutPricingCommunityTeamsStart Free TrialLog in
Avatar of jkemp761
jkemp761
 asked on

WSUS Error 8024400D

Good Afternoon,

I have 20 Servers so far that wont register with their WSUS Server (WSUS Standalone Config)

I have read several MS Technet articles and have tried various recommendations including:
----------------------------------------
1. Rename the Windows Update related temporary folder:
net stop wuauserv
ren %windir%\SoftwareDistribution %windir%\SoftwareDistribution.old
net start wuauserv

2. Download and install the latest WUAgent
3. Rename the catroot2 folder:
net stop cryptsvc
ren %systemroot%\system32\catroot2 oldcatroot2
net start cryptsvc
-------------------------------------------

Removed The Client ID Reg Entries from the registry and Reset Authorization and Tried to Detect.  No Go...

I can download the CAB Files if I copy and paste the URL's into the Browser on the servers that have the issue.  

Genuinely Stumped here..

Here is the last Entry from the log:
2016-01-26      14:12:25:413      5780      171c      PT        Server URL = http://<servernamehere>:8530/SimpleAuthWebService/SimpleAuth.asmx
2016-01-26      14:12:25:959      5780      171c      PT      WARNING: RegisterComputer failure, error = 0x80244016, soap client error = 10, soap error code = 0, HTTP status code = 400
2016-01-26      14:12:25:959      5780      171c      PT      WARNING: PTError: 0x80244016
2016-01-26      14:12:25:959      5780      171c      PT      WARNING: ClientWebService->RegisterComputer failed, hr=0x80244016, Not Fatal
2016-01-26      14:12:25:975      5780      171c      PT      WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
2016-01-26      14:12:25:975      5780      171c      PT      WARNING: SOAP Fault: 0x00012c
2016-01-26      14:12:25:975      5780      171c      PT      WARNING:     faultstring:Fault occurred
2016-01-26      14:12:25:975      5780      171c      PT      WARNING:     ErrorCode:RegistrationRequired(3)
2016-01-26      14:12:25:975      5780      171c      PT      WARNING:     Message:need to call RegisterComputer.
2016-01-26      14:12:25:975      5780      171c      PT      WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2016-01-26      14:12:25:975      5780      171c      PT      WARNING:     ID:1ecf01f0-3363-4295-b771-0443dcba9945
2016-01-26      14:12:26:006      5780      171c      PT      Initializing simple targeting cookie, clientId = d01c3b44-a284-44eb-9d57-d35c0dd312cc, target group = , DNS name = vlt586nus.svc.livevault.com
2016-01-26      14:12:26:006      5780      171c      PT        Server URL = http://<servernamehere>:8530/SimpleAuthWebService/SimpleAuth.asmx
2016-01-26      14:12:26:256      5780      171c      PT      WARNING: RegisterComputer failure, error = 0x80244016, soap client error = 10, soap error code = 0, HTTP status code = 400
2016-01-26      14:12:26:256      5780      171c      PT      WARNING: PTError: 0x80244016
2016-01-26      14:12:26:256      5780      171c      PT      WARNING: ClientWebService->RegisterComputer failed, hr=0x80244016, Not Fatal
2016-01-26      14:12:26:271      5780      171c      PT      WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
2016-01-26      14:12:26:271      5780      171c      PT      WARNING: SOAP Fault: 0x00012c
2016-01-26      14:12:26:271      5780      171c      PT      WARNING:     faultstring:Fault occurred
2016-01-26      14:12:26:271      5780      171c      PT      WARNING:     ErrorCode:RegistrationRequired(3)
2016-01-26      14:12:26:271      5780      171c      PT      WARNING:     Message:need to call RegisterComputer.
2016-01-26      14:12:26:271      5780      171c      PT      WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2016-01-26      14:12:26:271      5780      171c      PT      WARNING:     ID:fc176fb1-0fa5-493d-ad90-6043e646ac26
2016-01-26      14:12:26:302      5780      171c      PT      Initializing simple targeting cookie, clientId = d01c3b44-a284-44eb-9d57-d35c0dd312cc, target group = , DNS name = vlt586nus.svc.livevault.com
2016-01-26      14:12:26:302      5780      171c      PT        Server URL = http://<servernamehere>:8530/SimpleAuthWebService/SimpleAuth.asmx
2016-01-26      14:12:26:552      5780      171c      PT      WARNING: RegisterComputer failure, error = 0x80244016, soap client error = 10, soap error code = 0, HTTP status code = 400
2016-01-26      14:12:26:552      5780      171c      PT      WARNING: PTError: 0x80244016
2016-01-26      14:12:26:552      5780      171c      PT      WARNING: ClientWebService->RegisterComputer failed, hr=0x80244016, Not Fatal
2016-01-26      14:12:26:568      5780      171c      PT      WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
2016-01-26      14:12:26:568      5780      171c      PT      WARNING: SOAP Fault: 0x00012c
2016-01-26      14:12:26:568      5780      171c      PT      WARNING:     faultstring:Fault occurred
2016-01-26      14:12:26:568      5780      171c      PT      WARNING:     ErrorCode:RegistrationRequired(3)
2016-01-26      14:12:26:568      5780      171c      PT      WARNING:     Message:need to call RegisterComputer.
2016-01-26      14:12:26:568      5780      171c      PT      WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2016-01-26      14:12:26:568      5780      171c      PT      WARNING:     ID:34022b3a-5f0f-48d8-a050-54836ae2eaeb
2016-01-26      14:12:26:599      5780      171c      PT      Initializing simple targeting cookie, clientId = d01c3b44-a284-44eb-9d57-d35c0dd312cc, target group = , DNS name = vlt586nus.svc.livevault.com
2016-01-26      14:12:26:599      5780      171c      PT        Server URL = http://<servernamehere>:8530/SimpleAuthWebService/SimpleAuth.asmx
2016-01-26      14:12:26:849      5780      171c      PT      WARNING: RegisterComputer failure, error = 0x80244016, soap client error = 10, soap error code = 0, HTTP status code = 400
2016-01-26      14:12:26:849      5780      171c      PT      WARNING: PTError: 0x80244016
2016-01-26      14:12:26:849      5780      171c      PT      WARNING: ClientWebService->RegisterComputer failed, hr=0x80244016, Not Fatal
2016-01-26      14:12:26:864      5780      171c      PT      WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
2016-01-26      14:12:26:864      5780      171c      PT      WARNING: SOAP Fault: 0x00012c
2016-01-26      14:12:26:864      5780      171c      PT      WARNING:     faultstring:Fault occurred
2016-01-26      14:12:26:864      5780      171c      PT      WARNING:     ErrorCode:RegistrationRequired(3)
2016-01-26      14:12:26:864      5780      171c      PT      WARNING:     Message:need to call RegisterComputer.
2016-01-26      14:12:26:864      5780      171c      PT      WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2016-01-26      14:12:26:864      5780      171c      PT      WARNING:     ID:8257477b-f036-4988-b24f-9336f019e5c4
2016-01-26      14:12:26:864      5780      171c      PT      WARNING: PTError: 0x8024400d
2016-01-26      14:12:26:864      5780      171c      PT      WARNING: SyncUpdates_WithRecovery failed.: 0x8024400d
2016-01-26      14:12:26:864      5780      171c      PT      WARNING: Sync of Updates: 0x8024400d
2016-01-26      14:12:26:864      5780      171c      PT      WARNING: SyncServerUpdatesInternal failed: 0x8024400d
2016-01-26      14:12:26:864      5780      171c      Agent        * WARNING: Failed to synchronize, error = 0x8024400D
2016-01-26      14:12:26:864      5780      171c      Agent        * WARNING: Exit code = 0x8024400D
2016-01-26      14:12:26:864      5780      171c      Agent      *********
2016-01-26      14:12:26:864      5780      171c      Agent      **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2016-01-26      14:12:26:864      5780      171c      Agent      *************
2016-01-26      14:12:26:864      5780      171c      Agent      WARNING: WU client failed Searching for update with error 0x8024400d
2016-01-26      14:12:26:864      5780      de0      AU      >>##  RESUMED  ## AU: Search for updates [CallId = {6A65E0BC-4D8F-40CA-A410-14BB2E6FFF11}]
2016-01-26      14:12:26:864      5780      de0      AU        # WARNING: Search callback failed, result = 0x8024400D
2016-01-26      14:12:26:864      5780      de0      AU        # WARNING: Failed to find updates with error code 8024400D
2016-01-26      14:12:26:864      5780      de0      AU      #########
2016-01-26      14:12:26:864      5780      de0      AU      ##  END  ##  AU: Search for updates [CallId = {6A65E0BC-4D8F-40CA-A410-14BB2E6FFF11}]
2016-01-26      14:12:26:864      5780      de0      AU      #############
2016-01-26      14:12:26:864      5780      de0      AU      Successfully wrote event for AU health state:0
2016-01-26      14:12:26:864      5780      de0      AU      AU setting next detection timeout to 2016-01-27 00:12:26
2016-01-26      14:12:26:864      5780      de0      AU      Successfully wrote event for AU health state:0
2016-01-26      14:12:26:864      5780      de0      AU      Successfully wrote event for AU health state:0
2016-01-26      14:12:31:873      5780      171c      Report      REPORT EVENT: {8AF03217-EA79-4260-9B79-3945D393E99A}      2016-01-26 14:12:26:864-0500      1      148      101      {00000000-0000-0000-0000-000000000000}      0      8024400d      AutomaticUpdates      Failure      Software Synchronization      Windows Update Client failed to detect with error 0x8024400d.
2016-01-26      14:12:31:889      5780      171c      Report      CWERReporter::HandleEvents - WER report upload completed with status 0x8
2016-01-26      14:12:31:889      5780      171c      Report      WER Report sent: 7.6.7601.18847 0x8024400d(0) 0000000-0000-0000-0000-000000000000 Scan 0 1 AutomaticUpdates {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0
2016-01-26      14:15:24:523      5780      171c      PT      WARNING: RegisterComputer failure, error = 0x80244016, soap client error = 10, soap error code = 0, HTTP status code = 400
2016-01-26      14:15:24:523      5780      171c      PT      WARNING: PTError: 0x80244016
2016-01-26      14:15:24:523      5780      171c      PT      WARNING: ClientWebService->RegisterComputer failed, hr=0x80244016, Not Fatal
2016-01-26      14:15:24:523      5780      171c      Report      Uploading 2 events using cached cookie, reporting URL = http://<servernamehere>:8530/ReportingWebService/ReportingWebService.asmx
2016-01-26      14:15:24:741      5780      171c      Report      WARNING: Failed to upload events to the server with hr = c00ce556.
2016-01-26      14:15:24:741      5780      171c      PT      WARNING: ReportEventBatch failure, error = 0x80244016, soap client error = 10, soap error code = 0, HTTP status code = 400
2016-01-26      14:15:24:741      5780      171c      Report      WARNING: Reporter failed to upload events with hr = 80244016.
Windows Server 2008Microsoft Server OSMicrosoft ApplicationsMicrosoft Server AppsWSUS
Avatar of undefined
Last Comment
jkemp761
8/22/2022 - Mon
arnold
See if the following helps, deals with wiping everything from softwaredownloads....
https://groups.google.com/forum/#!topic/microsoft.public.windowsupdate/BnbzCQv2cxA

The issue is access to a URL is reflecting a permanent failure:
WARNING: RegisterComputer failure, error = 0x80244016, soap client error = 10, soap error code = 0, HTTP status code = 400


see if the following helps..
https://support.microsoft.com/en-us/kb/836941
*** Hopeleonie ***
Did you see this?

Error code 0x80244016 = HTTP 400  -- in short, the URL provided is invalid.

Check the url with the correct FQDN name and port 80 or 8530.(For example:http://wsus.contoso.com:8530). I would also suggest you walk thru the WSUS Deployment Guide and the WSUS Operations Guide.

Source:
https://social.technet.microsoft.com/Forums/office/en-US/d686c720-6c38-47a7-a15a-6b52b2f1987d/warning-registercomputer-failure-error-0x80244016-soap-client-error-10?forum=winserverwsus
*** Hopeleonie ***
Sorry arnold saw your post now. Didn't refresh :-)
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
jkemp761
ASKER
I understand what you are saying with the URL provided is invalid.  However I have other Servers with the same config that can patch just fine.  The other odd thing here is that I can actually get to the URL's from the problem servers.
R. Andrew Koffron
knee-jerk response, is a failed routing or new firewall issue on a network segment, you said 20 servers, so I'm assuming they're not all on one switch.

sounds like infrastructure problem, not a server problem can you but being able to download in the browser seems to rule that out.

Maybe firewall issues, due to how the WSUS downloads compared to a browser. something like packet inspection, or compressed traffic.
jkemp761
ASKER
I suppose it could be a network issue (Firewall has been disabled locally on the server for troub;leshooting purposes).. The odd thing is that it does initially report in (Shows in the WSUS Console under Unassigned Computers) but never updates.
âš¡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
jkemp761
ASKER
Addendum:  When it reports into the console it does not show the OS Version and Last Status Report all say "Not Yet Reported"
jkemp761
ASKER
I am now also able to confirm that the servers that do get patched and the ones that dont are both on the same subnet.
*** Hopeleonie ***
One one problem Server open CMD as an Administrator and run this coomand:
wuauclt.exe /resetauthorization /detectnow
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
jkemp761
ASKER
Executed with no result.  Still get the same error.
*** Hopeleonie ***
That command will not work immediately. Wait a little and let us know.

Can you please answer my first post:
When you open the url with the correct FQDN name and port 80 or 8530 on the same Server .(For example: http://wsus.contoso.com:8530). What will you see?
arnold
the issue deals with SOAP and access, checking the IIS logs to see which page/resource was being accessed when 400 error is returned, the other deals with SOAP as being the .....
âš¡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
jkemp761
ASKER
Hi,
I have executed that command several times over the last couple days..  No Effect.

When I execute that particular URL via the Browser I get: <See attached ScreenShot>
2016-01-27-16_45_15.png
arnold
this is on the IIS server where wsus is installed.
check the security settings on that location and allow anonymous access if currently denied.
Enable browsing if needed...
jkemp761
ASKER
Anonymous Access allowed on WSUS Admin site already (Only Option enabled).  I enabled browsing and no luck thier either.
Your help has saved me hundreds of hours of internet surfing.
fblack61
*** Hopeleonie ***
And ping to the WSUS Server works?
jkemp761
ASKER
Yes, Ping works..  

Thanks
*** Hopeleonie ***
Good, what will you see when you do a Telnet to the WSUS Server?

telnet IPWSUSServer Port (80 or 8530)
âš¡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
arnold
Check the security settings, you have something there that is prevents access which is why you are getting a 403 error.
the settings might be such that what is being accessed is a asmx and the settings deny execution.

the peculiar thing is that you say some servers/systems have no issues and some do? what is common to those that work versus the ones that do not?
jkemp761
ASKER
The only thing i can figure currently is that they are HP DL180 G6's...  The rest that work are DL380 G6's..  Could be a firmware issue i suppose.  

Though I get the 403 Error on the ones that work as well..  Very strange, pulling whats left of my hair out.
jkemp761
ASKER
Hope,  I believe i tried telnet and it works..  I will verify when I get back to work in the AM.
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
*** Hopeleonie ***
Let us know. We are here :-)
jkemp761
ASKER
Hi Hope,

Telnet connects and gives me a blank screen.  Acts as I would suspect..
jkemp761
ASKER
Arnold,

Im looking through the IIS Logs and here is an entry that relates to the 400 Error.  

2016-01-28 14:30:55 192.168.129.157 POST /ReportingWebService/ReportingWebService.asmx - 8530 - 192.168.133.130 Windows-Update-Agent 400 0 0 434
âš¡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
jkemp761
ASKER
When I try to access that url from the Server that is having the issue I get:


Server Error in '/ReportingWebService' Application.

Runtime Error
  Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".



<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>
 

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.



<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>
jkemp761
ASKER
I have just checked again that Everything under the WSUS Administration site in IIS is set for "Anonymous Authentication"
arnold
Did you try adjusting the web.config as recommended to see what the error is when accessing from the remote system?

The issue seems to be with SOAP that deals with the interaction rather than the WSUS server itself.
For one reason or another the WU version on the ones that are not functioning, have an issue with datat exchange which SOAP is handling.

did you try the stop windows update and BITS. delete the contents of c:\windows\softwaredownloads\* as suggested before as well as in the google link?
and see whether it will get the updated versions from the WSUS server and start working.
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy
jkemp761
ASKER
Hi Arnold,

Yes I have done as suggested in the google link and (again about an hour ago) No luck..  

Regarding Soap, do you think it could be an issue on the Client Server side?
arnold
It is possible that this is an issue on the client side where the SOAP interaction between it and the Server leads to an error either by the client side is attempting to access a reference that does not exist on the server or is using an older call that is not supported by the wsus server.

When you browse from the working systems to http://<servernamehere>:8530/SimpleAuthWebService/SimpleAuth.asmx
do you get a display of the various commands available or do you get an error as you do on the system where these issues fail?
I think the two are GetAuthorizationCookie and Ping

If the issue follows your web browser, I think you may have something mismatched.
Checking what is common to the systems that work (security group membership, OU, etc.) versus the ones that do not work including which OS they are running.
jkemp761
ASKER
Good Morning Arnold,

Yes, if I navigate to that page on an affected server, I do get that page you are referring to.  Basically all servers can get to that page.
âš¡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
arnold
The issue is then with the SOAP functionality on the client that deals with first getting the authorization....

The reset as was posted earlier.......
But it is not clear

How the systems that do not work differ from those that do? Recent acquisition?
Have the non-working systems scanned for virus etc. that is ........ Interfering with updates?

Does the wsus server reflect that an update at some point failed to install on these failing systems?
jkemp761
ASKER
As far as the server role..  they are all identical.  The only difference is the hardware of the server itself...  HP DL160 g6 (Doesnt work) vs DL380 G6 (Works).  

A little history: Previously all had opsware pushing patches down, but we have a new parent company and opsware went away.  I chose WSUS to take its place.

WSUS Has no info on the servers as they cant fully communicate with them.
arnold
Check whether the opsware remnants on the dl160 is the issue....
Were the opsware agents removed/uninstalled or using the opsware server were they severed?
Were the 380's ever under opsware management?
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck
jkemp761
ASKER
No luck...  Removed the HP SA Agent (Opsware), Tested, same error.
jkemp761
ASKER
Yes the 380's still have the agent installed.
arnold
where they managed in a different way?
I.e. belonging to ..

os on 160 and 360's the same?

check agent settings?
âš¡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
jkemp761
ASKER
Hi Arnold,

Yes they where all managed the Same way..  And They all have 2K8 R2 STD on all servers...
ASKER CERTIFIED SOLUTION
jkemp761
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
Plans and Pricing
Resources
Product
Podcasts
Careers
Contact Us
Teams
Certified Expert Program
Credly Partnership
Udemy Partnership
Privacy Policy
Terms of Use

© 1996-2023 Experts Exchange, LLC. All rights reserved. Covered by US Patent