WSUS 0x80244022

[Gongalong]

Hi folks,

 

We have an issue with our WSUS server where it seems to become unresponsive. This happens every few hours, and a reboot fixes it.

 

In the WSUS console we just get "Error: Connection Error. An error occurred trying to connect to the WSUS server. This error can happen for a number of reasons etc.". There's an option to "Reset Server Node", but this does nothing. It's also evident on the clients because they give the error "There were some problems installing updates etc. 0x80244022."

 

I've run the cleanup routine, but no resolution. Server Manager doesn't show any error.

 

Any ideas?

 

Thanks

[sultan966]

1. Increase IIS Private memory limit.

2. Run WSUS Server CleanUp Wizard. It may take long time to do this. Run one item at a time. Be patient on this. It sometimes takes days to cleanup.

 

See what happens.

Edited October 4, 2017 by sultan966

[Gongalong]

1. OK, doubled that. Thanks!

(2. Done already, as mentioned above.)

[sultan966]

I think increasing IIS private memory limit will solve the problem. Restart the server after that.

[sted]

open up an admin command prompt and type in"C:\Program Files\Update Services\Tools\wsusutil.exe" postinstall /servicing

wait

then load server manager and go to add roles/features, go to the features page and tab out .net framework 4.5 features then tab out wcf services and tick http activationrestart the wsus servicehopefully that should fix ita temporary fix if that dosent work is to run iisreset from an admin command prompt it will get it working again but will probably fail again after some time

[Tesla]

1. Increase IIS Private memory limit.

 

See what happens.

 

Didn't know increasing the limit was a thing, this seems to have solved an error i've been getting for ages (that doesnt actually effect WSUS operating, just takes up more space..) whereby it crashes on running the cleanup. Googling the error code that always came up never suggested this as a thing, so thanks!

[sultan966]

Glad to see your problem is solved.

[lafleur1977]

I have been having this error recency on my WS2012R2 WSUS server, after its been working fine for the last 2-3 years when it was setup. I have seen the recommendations about wsus cleanup (I run this a few times a year anyway and have done recently) and also about the IIS private memory limit. I have increased the private memory from the default 1843200KB to 2843200KB, which improved it for a day, but then the reset server node error returned. I have just increased it again to 3843200KB hoping this will be enough.

 

My question is what have you all increased it to? The server is a VM doing only WSUS and I had 4GB ram assignedbut have just increased it to 6GB. How much memory do you guys have for WSUS?

 

Thanks

[computer_expert]

Make sure you only have the categories/products you need (Get rid of old OS/office updates etc) - this helps with disk space too Edited December 2, 2018 by elsiegee40

[leeshellard]

I found this and a clean up worked