SCCM & WSUS Crash

[KibosJ]

Hey Guys,

 

Hoping someone can help me out here, this is getting me rather annoyed.

 

We are using SCCM for software updates and have been using it for about a year now without any issues, until a couple of weeks ago.

 

The WSUS component keeps dying and I get these messages in Event Viewer

 

The WSUS administration console was unable to connect to the WSUS Server via the remote API. 
Verify that the Update Services service, IIS and SQL are running on the server. 
If the problem persists, try restarting IIS, SQL, and the Update Services Service.System.Net.WebException -- 

The request failed with HTTP status 503: Service Unavailable.SourceSystem.Web.ServicesStack Trace:   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse
response, Stream responseStream, Boolean asyncCall)   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)   at 
Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetConfiguration()   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPGetConfiguration()   at 
Microsoft.UpdateServices.Internal.BaseApi.UpdateServerConfiguration.Load()   at Microsoft.UpdateServices.Internal.ClassFactory.CreateWellKnownType(Type type, Object[] args)   at 
Microsoft.UpdateServices.Internal.ClassFactory.CreateInstance(Type type, Object[] args)   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetConfiguration()   at 
Microsoft.UpdateServices.UI.AdminApiAccess.CachedObject.RefreshCache()   at Microsoft.UpdateServices.UI.AdminApiAccess.CachedObject.GetFromCache()   at 
Microsoft.UpdateServices.UI.AdminApiAccess.PermissionsManager.IsPermitted(UserOperation operation)   at Microsoft.UpdateServices.UI.SnapIn.Scope.UpdatesSummaryScopeNode.RefreshPermissions()   at 
Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.AddChildNodes()   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServerAndPopulateNode(Boolean connectingServerToConsole)   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ResetScopeNode()

 

I have restarted the WSUS service.

I have restarted the SCCM server.

I have run the wsusutil.exe postinstall /servicing command

 

None of this has worked to get WSUS back up and working, so I decided to remove the WSUS role from the server, delete the SQL database and re-install the role and it worked..... for about 3 hours

 

After about 3 hours, these messages appear in event viewer again and WSUS stops working. I really hope someone can help, I'm at a loss

[Linfit]

There are a number of causes of this. You will get more useful info from the SCCM logs-in the logs folder look for WSUSCtrl.log

This will give you more detailed information about exactly why the connection is failling.

 

A common cause is that the IIS application pool related to the WSUS Service has stopped because it is full and not recycling the memory.

If you open up the IIS console on the SCCM server and look at the application pools, check the one called WSUSPool and check that it has not stopped. If it has, manually re-start it and see if that temporarily fixes the problem. If it does, try allocating more ram to that pool - its in Advanced Settings on the right hand IIS menu, and the setting is called Private Memory Limit. I had to give ours 8GB before these connection errors stopped occuring, and that is with a single site, approx 800 devices.

[KibosJ]

Hi Linfit, thanks for replying.

 

I've removed the roll again now and I'm separating the servers and putting WSUS on its own VM but I'll look into this too, it's likely to happen again!

 

Thanks so much

[_queeg500]

We don't use SCCM, but our WSUS had the same issue. It would crash as soon as my back was turned.This solved it for us:https://blogs.technet.microsoft.com/sus/2015/03/23/support-tip-wsus-sync-in-configmgr-2012-fails-with-http-503-errors/On the WSUS box:

1. IIS Manager > Application Pools > WsusPool > Advanced Settings... > Private Memory Limit (KB) = 40000002. Restart application pool

 

If WSUS has been down or intermittent for a while, expect a deluge of server reboot requests.

 

As Linfit suggests, the memory limit will depend on your particular case.

[KibosJ]

Hey guys,

 

Thanks for this! Gonna try this out this morning and hopefully it will solve it once and for all. I find it strange that it has worked perfectly for the last year or so :/

[KibosJ]

Well it appears that this has solved the issue

 

I've had SCCM downloading and deploying updates through the automatic rules and WSUS is still alive

 

Thank you very much for this guys, saved me a lot of headaches.