SCCM Patch Update Error 0x80244022

For background i use SCCM Current Branch on windows server 2012 R2 and encounter this error. I didn’t remember any changes on my server but it hit me from nowhere. Some article say it might due to patches on windows server 2012 R2 but for mine, last server patches for security update has been quite a while. I believe there are others software update deployment that has been successfully deployed after the server patches.

Symptom

First i noticed from client PC whereby all my update is failed. I noticed it doesn’t go to even downloading.

Second, i triggered my application deployment and it is a success. I also did another try on another machine. So it’s only affected software update deployment. Therefore in this case i put aside any possibility of client issue, connection, distribution point and boundary issue or firewall blocking.

Troubleshooting

So now, lets check the error.

We noticed the error is 0x80244022 whereby this error is described as :

Same as HTTP status 503 – the service is temporarily overloaded. Check WSUS service is running. Open Internet explorer and type; http://[SCCM Server name]:8530 should display a page. If HTTP error 503. The service is unavailable. Then WSUS is currently down. Try rebooting the WSUS server first and if the issue continues, further investigation will be required.

Let’s check from browser on port 8530

Now it’s confirmed something is not right with WSUS on our server.

Solution

Remote to sccm server and check the IIS Manager. Here we can see the WsusPool has been stopped.

So there’s 2 way to do this. One is we restart our server. Second is we start Wsus pool. If possible, i would recommend to restart server. Because the moment i start wsuspool, it actually spike up my server memory to 100% even though we have set Private Memory Limit. End up we still have to reboot the server and it actually did stuck at restarting. But luckily we use VM so then we can use VM to restart guest OS to force it a bit. It will take awhile but eventually it did the job.

Private Memory Limit

On the advanced settings of Application Pool, scroll down to ‘Private Memory Limit’. Here you can increase it accordingly if you have enough server memory. Do check your deployment and take a look if there’s any you can end.

Above is just my method in solving the issue. If you do have better solution, do leave a comment and share with us.