Server 2016 WSUS keeps failing

[talksr]

Hi there, getting really fed up with this issue. Every time I log in to our 2016 server and check WSUS, I am getting the following error:

 

Error: Connection Error.

An error occurred trying to connect the WSUS server. This error can happen for a number of reasons. Check connectivity with the server. Please contact your network administrator if the problem persists.

I am only able to get it to work by bouncing the server, but within hours, it is doing it again.

 

Copy of error below, any ideas?

 

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.

 

Source

System.Web.Services

 

Stack 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()

 

The partition WSUS folder is on has 400gb of free space, IIS has not been messed about with and the server is only running WSUS and Sophos EC for AV purposes. This is not a DC, just joined to domain as member.

Edited April 9, 2017 by talksr

[KibosJ]

Could be the same as the issue I had, where WSUS is running out of memory in IIS

 

http://www.edugeek.net/forums/enterprise-software/182174-sccm-wsus-crash.html#post1564085

[Michael]

I've had it where the IIS Service just stops, however starting it manually it appears OK.

 

Have you applied the latest March 2017 patch? It's quite a big update and has lots of fixes. It brings IE11 to 11.0.40.

[talksr]

I have not applied any patches but it is fully updated. Is this a manual patch?

Do you think it could be a RAM related issue?

Thought the minimum ram requirement for WSUS was 2gb, this system has 4.

[Michael]

Is it physical or virtual?

[talksr]

Is it physical or virtual?

 

Physical. I have just upped the ram to 12gb. Left it for 6 hours and it has flipping done it again! Grrr.

[KibosJ]

Have you tried increasing the memory available to the WSUS pool in IIS?

[talksr]

Have you tried increasing the memory available to the WSUS pool in IIS?

 

I changed this earlier:

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

 

Changed from 1843200kb to 40000002.

Not sure if that is what you are referring to? So far, so good.

[KibosJ]

Yeah that was it It worked for myself, thought I was going crazy!

[talksr]

Yeah that was it It worked for myself, thought I was going crazy!

 

Great, yes I think that has done the job! Thanks for your help!

[kdj]

Terrific! I had been going around in circles for two days before I stumbled upon this solution. Thanks so much.

[ModeratelyGruntled]

I'm having this exact issue on a Server Core installation. I can't access the site via IIS Remote Manager - I go to add the remote server and it's unable to connect. Can I increase the memory limit using powershell/command line?

 

...or does anyone have any idea why I can't connect using remote IIS to a machine with default WSUS configuration!?

 

Thanks