Win 2016 cant connect to WSUS error 8024401f

baysysadmin
baysysadmin used Ask the Experts™
on
I have a few Win 2016 server vms that are having issues connecting to WSUS 6.3 which runs on Win 2012R2
The errors I get are
8024401f
8024401c

Logs show this

2018/06/05 07:45:14.5767492 680   4164  WebServices     WS error: There was an error communicating with the endpoint at 'http://WSUS.domain.com:8530/ClientWebService/client.asmx'.
2018/06/05 07:45:14.5767518 680   4164  WebServices     WS error: The server returned HTTP status code '500 (0x1F4)' with text 'System.ServiceModel.ServiceActivationException'.
2018/06/05 07:45:14.5767533 680   4164  WebServices     WS error: The server was unable to process the request.
2018/06/05 07:45:14.5767656 680   4164  WebServices     Web service call failed with hr = 8024401f.

Open in new window


I am able to load this page http://WSUS.domain.com:8530/ClientWebService/client.asmx
with this result.

Client Service


You have created a service.

To test this service, you will need to create a client and use it to call the service. You can do this using the svcutil.exe tool from the command line with the following syntax:

svcutil.exe http://wsus.domain.com:8530/ClientWebService/Client.asmx?wsdl

You can also access the service description as a single file:

http://wsus.domain.com:8530/ClientWebService/Client.asmx?singleWsdl

Open in new window


Ive read so many articles about fixes in IIS< but none have worked, nor have there been and changes on WSUS server.
I have another WSUS on another domain and I'm having the same issue there.

On client side ive done the usual but no luck.

net stop wuauserv 
net stop cryptSvc 
net stop bits 
net stop msiserver 
Ren C:\Windows\SoftwareDistribution SoftwareDistribution.old 
Ren C:\Windows\System32\catroot2 Catroot2.old 

Open in new window


The client gets added to WSUS but shows not yet reported.

Ive deployed the new 2016 VM from few different templates with same result.

I have some other 2016 vms, from same templates from a while ago, and those are not showing this error. So I'm not sure why these new ones are.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Shreedhar EtteTechnical Manager
Top Expert 2010

Commented:

Author

Commented:
Like i mentioned I already tried those steps, they didnt work.

I also tried installing the required update.
https://support.microsoft.com/en-us/help/3095113/update-to-enable-wsus-support-for-windows-10-feature-upgrades
but it said its not applicable to my server.
Shreedhar EtteTechnical Manager
Top Expert 2010

Commented:
Where you able to browse: http://WSUS.domain.com:8530/content

If not then refer the article further:

http://kaustubhghanekar.blogspot.com/2011/05/advanced-wsus-troubleshooting-for-error.html

Author

Commented:
http://WSUS.domain.com:8530/content
Gives me error 403 declined to show this page.

Occasionally IIS on WSUS will crash I and have to start the pool again.

I looked at the mine types, but didnt find any duplicates. Its basically all default setup.

And only some servers are affected, others are still getting updates

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial